20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You’ll spend mornings gathering and checking facts: reading model docs, running short tests, or interviewing a subject-matter expert (SME) about a math algorithm. That often leads into writing or editing a doc page in Atlassian Confluence or an XML-based help file.
Afternoons are for visuals and reviews — making a diagram in Adobe Illustrator or laying out a PDF in Adobe InDesign, then tracking issues in Atlassian JIRA. You’ll also save versions and notes in your content system so you can show revisions later.
According to the U.S. Bureau of Labor Statistics (BLS) for 2025, there were about 45,500 people employed in this occupation. The median annual wage was $90,390; the lowest tenth earned $57,440 and the top tenth earned $145,270.
Use those numbers as a range guide — actual offers depend on location, industry, and your math/AI depth. The BLS is the source for these figures.
Technical writers document, clarify, and teach. You don’t produce production code like a developer, and you don’t design models or run large-scale experiments like a data scientist. Your deliverables are docs, SOPs, diagrams, and usability improvements.
You collaborate closely with developers and data scientists, translate their jargon into user-facing guides, and maintain docs in systems like Confluence, XML repositories, and Adobe tools. You need enough technical literacy to verify content and reproduce simple examples.
Show you can produce a clear Confluence page: write a short how-to for running a tiny math example, include one diagram from Illustrator or an image edited in Photoshop, and attach a PDF exported from InDesign or Acrobat.
That package proves you can gather info, organize it, use the content tools named above, and follow a publishable workflow — exactly the daily work this role requires.