roadmap.sh: Technical Writer

What it is

The Technical Writer roadmap is one of the community roadmaps on roadmap.sh, the open source project that publishes visual learning paths for developer roles. It lays out the role as a map of nodes: what technical writing is and who does it, the required skills (language, written communication, technology expertise), the forms of technical writing, and the main content types such as tutorials, how-to guides, references, troubleshooting pages, release notes and FAQs. It then covers docs structure, API definitions and references, writing style guides, Markdown, Git and version control, docs generation and publishing tools, and growth as a technical writer.

The roadmap also includes a section on technical content marketing: blog posts, case studies, SEO keywords and content funnels. That part matters if you are looking at developer-facing content roles at startups, where one writer often does docs and marketing content together.

Who it is for

It suits students and early-career people who like writing and technology and want to know what the job actually involves before committing. Engineers who keep getting asked to write the docs will also find it a quick way to see the whole field.

It is not a course. Each node opens a short explanation with a few links; the teaching comes from the resources you follow from there.

How to use it well

• Skim the whole map once to see the shape of the role, then mark what you already know.
• Pair the documentation nodes with a real course, such as Google's free technical writing courses, and a framework such as Diataxis.
• Treat the content marketing section as optional unless the jobs you are targeting mention SEO or blog content.
• Use it again later as a gap check: before applying, you should be able to explain every node in the docs and tooling sections with an example from your own portfolio.

Free vs paid

The roadmap itself is free. roadmap.sh offers an optional account for progress tracking and some AI tutor features; you do not need them to use the map.

Common questions

Does it tell me which tools to learn? It names categories and common examples rather than prescribing one stack. In practice, Markdown, Git and one static site generator cover most docs-as-code teams.

Is the marketing section required? No. Many documentation teams, especially at larger companies, do not write marketing content at all.

How long does it take? There is no fixed time. Most people can work through the documentation core in a few months of part-time study while building a small docs portfolio.