If you’re a technical writer who likes to understand why something is changing—not simply document it after the fact—this role offers the opportunity to get involved much earlier in the process.
We’re looking for someone who can work alongside Business Analysts, technology teams, and business stakeholders to understand requirements, analyze workflows and system changes, identify impacts, and translate that information into clear, useful documentation.
You’ll support a significant application modernization initiative, participate in requirements and discovery conversations, develop process flows and functional documentation, and help improve how monthly software releases and system changes are communicated across the organization. A key part of the role will be determining what is changing, who is affected, and what information different teams need to successfully adopt those changes.
This isn’t a traditional technical writing position focused on producing manuals or architectural documentation. It sits at the intersection of technical documentation, business analysis, process improvement, and change communication. You’ll have the opportunity to understand projects while they’re being developed rather than receiving a finished product to document afterward.
You may also create user resources and provide training or presentations when needed, but the primary focus is understanding applications and business processes, analyzing changes, and turning complex information into documentation that people can actually use.
This is an excellent opportunity for someone who enjoys technical writing but wants greater involvement in the analysis and requirements side of technology projects, with the potential to grow further into a Business Analyst role.
This is a 6-month contract-to-hire opportunity, with the expectation of transitioning to a full-time position following successful completion of the contract period.
What You’ll Do
