- Career Roadmaps
- Technical Writer
Technical Writer Roadmap
You turn complexity into words developers and users can act on. A genuinely open door for strong writers -
$60-85k US entry - with API documentation and docs-as-code as the highest-paying specialisation. AI made bad docs cheaper; it made trustworthy docs more valuable.
By Carl Mills
- Last updated 10 July 2026
- progress saves in your browser
- free personalized PDF study plan.
0%
0/16 items completed 13 critical left
0/100
Critical only
Import File
Stage 1 - The Craft 4 item(s)
- Audience analysis: what the reader knows, needs, fears Critical
- Diátaxis: tutorials vs how-tos vs reference vs explanation - never mixed Critical The framework that instantly upgrades doc thinking.
- Plain-language craft: short sentences, active voice, reader-first ordering Critical
- Work to a style guide (Google or Microsoft) consistently
Stage 2 - The Toolchain 4 item(s)
- Command-line comfort: following and testing your own instructions Critical
- Markdown + Git: writing in repos, PR reviews, resolving conflicts Critical
- One docs site generator (Docusaurus/MkDocs) deployed Critical
- Visuals: annotated screenshots, simple diagrams (Mermaid)
Stage 3 - Developer Docs 4 item(s)
- AI-assisted drafting with verification discipline - your accuracy is the product Critical
- API literacy: make real REST calls, read JSON, explain auth Critical
- Write API documentation: endpoints, parameters, errors, examples that run Critical
- OpenAPI specs and generated reference tooling
Stage 4 - Job-Ready Proof 4 item(s)
- 3+ merged documentation PRs to real open-source projects Critical
- A docs portfolio site: tutorial, how-to, API reference sample Critical
- CV/LinkedIn target "Technical Writer" naming docs-as-code + API docs Critical
- Writing test + interview practised (editing a bad doc aloud) Critical
Your selections are saved in your browser. Export a personalized PDF print-out any time.
Technical Writer roadmap FAQ
How technical do I need to be?
Enough to use what you document: run the API calls, follow your own tutorial, read basic code. Developer-docs roles (the best paid) expect working Git, command-line comfort and API literacy - all learnable, all on this roadmap.
Is technical writing safe from AI?
Drafting is automated; judgement is not. The 2026 role is editor-architect: deciding what needs documenting, verifying accuracy against the real product, structuring information, and using AI for drafts. Writers who refuse the tools are at risk; writers who wield them are more productive and more valued.
How do I build a portfolio with no job?
Document real open-source projects - many have terrible docs and welcome PRs. Three pieces: a quickstart tutorial, an API reference section, and a how-to guide. Merged documentation PRs are proof employers trust.
What next once the list is green?
Prove it under pressure: take the free Mock Interview, then check your application signals.
Not sure this is your direction?
Compare every tech role - what you'd build, what it pays, and who it suits - on the roadmaps hub.
Compare all roadmaps