9-step roadmap
Technical Writer
You turn complicated technical things into clear docs, guides, and tutorials that people can actually follow. It's a real, in-demand job, and one of the most common ways strong writers get into tech without a heavy coding background.
Technical Writer roadmap
Follow the line, from first step to goal.
Strong, plain writing
StartEverything here rests on clear writing: short sentences, plain words, and a logical order. If you can explain a hard idea simply, you already have the core skill this job is built on.
Learn enough tech to explain it
You don't need to build the software, but you need to understand it well enough to be trusted. Learn the basics of how apps, code, and the web work, so your explanations are actually right.
The types of docs
Good docs come in a few distinct shapes: tutorials (learning by doing), how-to guides (steps for one task), reference (the dry facts), and explanation (the why). Learn what each is for, and don't mix them up.
Write a great how-to guide
Practise the most common doc: a clear guide that walks someone through one task, start to finish. Test it by actually following your own steps and watching where a reader would get stuck.
API documentation basics
An API is how one piece of software talks to another, and its docs are prized and well-paid work. Learn to document what each part does, what it expects, and what it gives back, with examples that run.
Docs tools: Markdown & docs-as-code
Learn Markdown (a simple way to format text) and the 'docs-as-code' approach, where docs live alongside the code in Git and ship the same way. This is how modern teams write and publish docs.
Work with engineers
You'll get much of your material from busy developers. Learn to ask good questions, draft something, and check it with them — the back-and-forth is how docs become accurate.
Structure a whole docs site
One page is easy; a whole site is a craft. Learn to organise many docs so readers can find what they need and follow a sensible path, instead of drowning in a pile of pages.
Edit & keep docs accurate
GoalSoftware changes, and stale docs are worse than none. Learn to edit ruthlessly and to keep docs up to date over time — the unglamorous work that separates good docs from abandoned ones.