Technical Writer Career Roadmap

1. 1

   Nail Writing Fundamentals & Style Guides

   3–4 weeks

   The core skill is clear, concise, unambiguous writing — and it's more teachable than people expect. Work through Google's free Technical Writing courses, then internalise a major style guide (Google's or Microsoft's) so your prose follows conventions professional teams actually use. Clarity, not vocabulary, is the whole game here.

   Skills to learn

   • Plain language & concision
   • Active voice
   • Google & Microsoft style guides
   • Audience analysis
   • Structuring instructions
   • Editing & self-review

   Start with

   • Google – Technical Writing Courses (free)
   • Google Developer Documentation Style Guide
   • Microsoft Writing Style Guide

   Next: Learn the Docs-as-Code Toolchain

2. 2

   Learn the Docs-as-Code Toolchain

   3–5 weeks

   Modern documentation is written like software: in Markdown, versioned in Git, and published through static site generators. Getting comfortable with this workflow is often what separates a hireable technical writer from a Word-document one. You don't need to be an engineer, but you do need to live in the same tools they do.

   Skills to learn

   • Markdown
   • Git & GitHub workflow
   • Static site generators (Docusaurus, MkDocs)
   • Command line basics
   • Pull requests & reviews
   • Version control for docs

   Start with

   • Write the Docs – Docs as Code
   • Docusaurus – Documentation
   • GitHub – Git Handbook

   Next: Learn API Documentation

3. 3

   Learn API Documentation

   6–8 weeks

   API documentation is where the money is — it commands a clear premium because it demands both writing skill and enough technical literacy to read a spec and test an endpoint. Learn the OpenAPI specification, how reference docs and tutorials differ, and how developer audiences actually read. Tom Johnson's free course is the field's standard text.

   Skills to learn

   • REST API concepts
   • OpenAPI / Swagger
   • Reference vs conceptual docs
   • Documenting endpoints & parameters
   • Code samples & curl
   • Developer-audience empathy
   • Postman basics

   Start with

   • Documenting APIs (Tom Johnson, free)
   • OpenAPI Specification
   • Stripe API Docs (gold-standard example)

   Next: Build a Portfolio on Real Projects

4. 4

   Build a Portfolio on Real Projects

   6–10 weeks

   Nobody hires a technical writer on a resume alone — they hire on writing samples. Pick an open-source project with weak documentation and improve it: write a getting-started guide, document an API, or restructure a messy README. Real, published, reviewed contributions are worth more than any coursework and give you something concrete to point to.

   Skills to learn

   • Open-source contribution
   • Getting-started guides
   • README & tutorial writing
   • Diátaxis framework
   • Publishing a portfolio site
   • Working with maintainers

   Start with

   • The Diátaxis Framework
   • Write the Docs – Community
   • Good First Issue – Find Projects

   Next: Land Your First Role

5. 5

   Land Your First Role

   1–3 months

   With a portfolio in hand, target junior and associate technical writer roles, and don't overlook contract-to-hire postings, which are a common way in. Lean on the Write the Docs community for job leads and mentorship — it's an unusually welcoming professional network. Emphasise your portfolio and toolchain fluency over years of experience you don't yet have.

   Skills to learn

   • Resume & portfolio presentation
   • Documentation writing tests
   • Interviewing for writing roles
   • Working with SMEs & engineers
   • Networking (Write the Docs)

   Start with

   • Write the Docs – Jobs
   • LinkedIn – Technical Writer Jobs
   • Levels.fyi – Technical Writer Salaries

   Next: Specialise for the Salary Premium

6. 6

   Specialise for the Salary Premium

   Ongoing

   Seniority in technical writing comes from depth and ownership. Specialise where the pay is — API and developer documentation, or information architecture and docs-site ownership at scale — and grow into a documentation lead who sets standards, tooling, and strategy for a whole product. Deep API-docs specialists routinely out-earn generalist writers.

   Skills to learn

   • Advanced API & SDK documentation
   • Information architecture
   • Docs tooling & automation
   • Content strategy
   • Docs team leadership
   • Localisation & scale

   Start with

   • Write the Docs – Guide
   • The Good Docs Project
   • Docs for Developers (book)

jobroadmaps.com/roadmaps/technical-writer · Pay, demand and employer data for this role are further down the page.