How to become a Technical Writer / Developer Advocate
A complete, honest roadmap for two related roles: technical writing, centred on clear documentation, and developer advocacy, centred on community and reach. It covers where they overlap and where they diverge, from technical literacy and writing through docs, code samples, community, talks, and AI. It runs top to bottom, foundational to advanced, so you always know what comes next. Free to read, no signup required.
How to use this: tap a step on the map to open its details, skill pills, and guidance in a side panel. These are two related roles, so each step notes which it leans toward. Work down the spine in order; the early steps are shared ground, and the later ones separate the docs-focused path from the community-focused one.
Publish real developer content
Both roles are proven by public work. The most convincing thing you can do is create something that genuinely helps developers and put it out where people can find it.
Write a getting-started guide for a tool you like, with working, tested code samples.
Improve the documentation of an open-source project and get the change merged.
Record a short demo or write a clear tutorial that takes a developer from zero to a working result.
Give a short talk at a local meetup, or turn one of the above into a conference-style session.
Make it public and keep the samples working. A single piece that clearly helped developers is exactly the evidence these roles hire on.
Frequently asked questions
They overlap but have different centres of gravity. A technical writer focuses on documentation: accurate, clear, well-structured writing that helps people use a product, and is judged mostly on the quality of the docs. A developer advocate focuses on community and advocacy: talks, demos, code samples, and carrying feedback between developers and the product team, and is judged mostly on developer trust and adoption. Both need writing skill and technical understanding, and many people move between them.
It depends on what you enjoy. If you love writing, structure, and precision, and prefer working head-down, technical writing fits well. If you love teaching in public, speaking, building demos, and engaging a community, developer advocacy is a better match. You can start in one and move toward the other, since the foundation is shared.
Some technical ability is essential for both, but the depth differs. Technical writers need enough to understand and accurately document a product. Developer advocates generally need more hands-on coding, since writing working samples, building demos, and earning developer trust often depend on it.
No. Both fields value demonstrated ability over credentials, and people come in from writing, support, engineering, and teaching backgrounds. A portfolio of clear docs, useful posts, or good talks matters far more than a specific degree.
Make public work. Write documentation for an open-source project, publish a clear tutorial, record a short demo, or give a talk at a local meetup. This work is naturally visible, so a few strong pieces you can point to are the most convincing thing you can show.
It depends far more on building real skill and a public body of work than any fixed timeline. Many people transition from adjacent roles like support, engineering, or writing by producing developer content where they are. Consistently publishing useful work is what accelerates it.
Ready to prepare for real interviews with a personalized plan?
This roadmap is the map. When you’re ready to actually get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (writing craft, technical depth, docs tooling and workflow, DevRel and content strategy), a guided Build-a-Project track alongside it, and progress tracking the whole way. Start free.
