Free Learning Roadmap

How to Become a Technical Writer

API docs, tutorials, developer guides, and content operations. Sits at the intersection of engineering, product, and writing craft.

Topics
10
Resources
29
Cost
Free
Most resources are free or freemium
Format
Self-paced

1. Writing Foundations

core
Clear Technical Writing

Short sentences, active voice, one idea per paragraph. Google's Tech Writing Course is the industry-default primer.

Style Guides

Microsoft, Google, and IBM style guides are the industry standards. Pick one, follow it religiously.

2. The Diátaxis Framework

core
Tutorials, How-Tos, Reference, Explanation

Diátaxis is the modern documentation framework. Each type of content has different rules, different audiences, different structures.

3. API Documentation

core
OpenAPI / Swagger

The industry standard for describing REST APIs. Learn to read a spec, contribute to one, and generate docs from it.

API Doc Patterns

Getting Started, Authentication, Endpoints, Error Codes, Rate Limits, Changelog. Study Stripe, Twilio, and Plaid — the reference bar.

4. Developer Content

core
Tutorial Writing

Task-focused, step-by-step, working code. If the reader can't finish the tutorial in one sitting, it's too long.

Conceptual / Explanation Docs

The 'why' docs. Diagrams, background, tradeoffs. Often the highest-leverage docs but the least written.

5. Docs Toolchain

core
Docs Site Generators

Docusaurus, MkDocs, Sphinx, VitePress, Nextra. Docs-as-code is the norm — pick your stack based on the engineering team's language.

Markdown, MDX, reStructuredText

The three docs authoring formats. MDX (Markdown + JSX) is dominant for interactive docs.

Git for Writers

Branches, PRs, code review. Docs-as-code means writers use engineering workflows.

6. Docs Ops & Content Strategy

recommended
Docs IA

Structure, navigation, findability. Card sorting for docs. Category vs product vs task grouping.

Docs Analytics

What pages get traffic, where users bail, what searches return zero results. Measure to improve.

7. Working with Engineering

core
Reading Code

You can't document what you don't understand. Enough programming literacy to read the source you're writing about.

Docs Reviews in PRs

Docs live in the same repo as code. Review-driven docs quality is now the norm.

8. Specialisations

recommended
DevRel-Adjacent Writing

Blog posts, launch announcements, conference talks. Tech writers often bridge into DevRel.

UX Writing / Microcopy

In-product strings, error messages, empty states. A distinct craft from long-form docs.

9. AI in Docs

recommended
LLM-Assisted Drafting

First-draft acceleration, style-guide enforcement, translation. AI raises the floor; craft is the ceiling.

10. Career & Voices

optional
Voices to Follow

Where working tech writers hang out.

Want a personalised version?

This roadmap is the same one our platform uses internally, but the logged-in version lets you tick off topics as you complete them, track a personalised First 90 Days plan, and see your AI-durability score against this role. All free.

Open the interactive roadmap →
Curated by WhatTNext Ai · methodology · all roadmaps · last updated 2026-07-29