Developer Advocate (DevRel) Career Roadmap

1. 1

   Learn What Developer Relations Is For

   1–2 weeks

   Start with the purpose, because the title covers different jobs. Developer relations exists to help developers succeed with a product, and to carry what they say back to the company. Read postings from companies you like and note the balance: some stress content and talks, some stress samples and engineering, some stress community programmes. Learn how the work is measured, since adoption and feedback matter more than follower counts.

   Skills to learn

   • Developer relations versus marketing, support and documentation
   • Developer journey from first visit to production use
   • Advocacy, education and community as three strands
   • How DevRel work is measured
   • Reading a posting for the real mix of work

   Start with

   • DevRel Collective – community and definitions
   • Open Source Guides – metrics
   • Write the Docs – documentation guide

   Next: Be a Credible Builder on One Platform

2. 2

   Be a Credible Builder on One Platform

   8–12 weeks

   Developers trust advocates who build. Pick the product category you want to represent (data, infrastructure, AI, identity, developer tools) and get good enough to build real things with it in public: a sample app, an integration, a tool. Be fluent in Git and GitHub, in one or two languages and in how the platform's API and documentation work. You should be able to answer a developer's question from your own experience, not from a script.

   Skills to learn

   • One or two languages, usually Python, JavaScript or TypeScript
   • Git and GitHub workflows
   • Reading and using an API and its docs
   • Building sample apps and integrations
   • One product category in depth
   • Debugging in front of an audience

   Start with

   • GitHub Skills
   • MDN – Learn web development
   • The Missing Semester of Your CS Education

   Next: Learn to Teach in Writing and Code

3. 3

   Learn to Teach in Writing and Code

   6–10 weeks

   Written explanation is the daily output: tutorials, guides, sample code and blog posts. Learn to write for a beginner, to scope a tutorial so the reader finishes it and to keep sample code simple and correct. Study how documentation is organised so that your content fits next to it instead of competing with it. Publish regularly, because a public body of work is how most advocates are hired.

   Skills to learn

   • Clear technical writing
   • Tutorials, how-to guides, reference and explanation as different kinds of content
   • Sample code that demonstrates one idea
   • Markdown and docs tooling
   • Editing your own work
   • Using language models as a drafting aid, with review

   Start with

   • Technical Writing One – Google
   • Technical Writing Two – Google
   • Diátaxis – a systematic approach to documentation

   Next: Speak, Present and Run Workshops

4. 4

   Speak, Present and Run Workshops

   6–10 weeks

   Many postings name conference talks, meetups and workshops. Start small: a meetup talk, a lightning talk, a live-coding stream or a recorded walkthrough. Learn to structure a talk around one idea, to run a live demo that survives failure and to run a workshop where people actually build something. Record your talks and share the links, as employers will watch them.

   Skills to learn

   • Structuring a talk around one idea
   • Live demos and recovering from failures
   • Workshop design and facilitation
   • Video and livestream basics
   • Handling questions and hostile audiences
   • Travel and event planning

   Start with

   • DevRel Collective – community and resources
   • Technical Writing One – Google
   • GitHub Skills

   Next: Build and Grow a Community

5. 5

   Build and Grow a Community

   6–10 weeks

   Community appears in most postings. Learn how open-source communities work: welcoming contributors, setting a code of conduct, answering issues, recognising contributors and avoiding burnout. Take part in a real community before you try to lead one, whether an open-source project, a forum or a Discord server. Learn to turn community feedback into something the product team can act on, with examples and numbers.

   Skills to learn

   • Open-source contribution and maintainership
   • Welcoming contributors and codes of conduct
   • Community channels and moderation
   • Turning feedback into product input
   • Community metrics
   • Working with open-source licences

   Start with

   • Open Source Guides
   • Open Source Guides – building welcoming communities
   • DevRel Collective – community and resources

   Next: Get In and Grow Into a Programme Lead

6. 6

   Get In and Grow Into a Programme Lead

   6–12 months

   Entry seats are rare, so most people arrive from software engineering, technical support, solutions engineering, technical writing or community roles, bringing a public portfolio. Show a handful of posts, a recorded talk, a sample app and an open-source contribution, each with an outcome (people used it, a bug was fixed, a feature changed). Later steps lead to senior and staff advocate, to managing a team, and to head or vice-president of developer relations.

   Skills to learn

   • Entry routes: engineering, support, solutions, technical writing, community
   • A public portfolio with outcomes
   • Choosing between content, community and engineering strands
   • Managing advocates and programmes
   • Developer strategy at company level

   Start with

   • DevRel Collective – community and resources
   • Open Source Guides – metrics
   • Write the Docs – documentation guide

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