The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
Mid-Level Developer Advocate
2-3 yearsSkills to master
- As a Mid-Level Advocate, you'd have mastered independent content creation, owned a specific content stream (like our blog or YouTube channel), and delivered talks at regional meetups. You'd be comfortable with our core tech stack and actively engaging in our community.
You're ready to move on when
- Consistently delivering high-quality, impactful content independently.
- Successfully owning and growing a specific content or community initiative.
- Receiving positive feedback on your public speaking and community engagement.
- Proactively identifying and proposing solutions to developer pain points.
- 2
Senior Software Engineer (with external focus)
5-7 yearsSkills to master
- You'd be an experienced engineer with a deep technical background, but crucially, you'd have a proven passion for teaching, writing, and engaging with external technical audiences. Maybe you've written extensively, contributed to open source, or mentored junior developers outside your immediate team.
You're ready to move on when
- A strong portfolio of personal technical projects or open-source contributions.
- Experience explaining complex technical concepts to non-technical audiences.
- Demonstrated interest in community building or technical education (e.g., running workshops, speaking at internal events).
- Excellent communication skills, both written and verbal, beyond just coding.
- 3
Technical Writer / Content Strategist
4-6 yearsSkills to master
- You'd come with a strong background in creating highly technical documentation and content, but with a desire to be more hands-on with code and public-facing. You'd understand content strategy and how to make complex topics accessible, but you'd be ready to step onto the stage.
You're ready to move on when
- A portfolio of clear, accurate, and engaging technical documentation or long-form content.
- Experience collaborating closely with engineering teams on product features.
- Demonstrated ability to translate technical specifications into user-friendly guides.
- A desire to move into public speaking and live coding, perhaps with some initial experience.