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
Senior Developer Advocate
3-5 years as a Senior AdvocateSkills to master
- As a Senior Advocate, you'd have mastered leading major content or community initiatives, mentoring junior advocates, and being a trusted voice at regional conferences. You'd be comfortable owning entire workstreams and making technical decisions within your scope.
You're ready to move on when
- Consistently delivering high-impact content that generates significant engagement.
- Successfully leading and executing complex DevRel projects from start to finish.
- Demonstrating strong mentorship capabilities with junior team members.
- Regularly presenting at national or international conferences with positive feedback.
- 2
Staff Software Engineer with Advocacy Focus
Transition typically takes 1-2 years of focused advocacy workSkills to master
- You'd be coming from a deep technical background, perhaps having already contributed to open-source projects or written extensively about complex technical topics. You'd need to develop your public speaking, content strategy, and community engagement skills, but your technical credibility would be undeniable.
You're ready to move on when
- A strong portfolio of technical writing or open-source contributions.
- Demonstrated ability to explain complex technical concepts clearly to diverse audiences.
- Initiative in presenting technical topics internally or at local meetups.
- A genuine passion for community building and developer education.
- 3
Technical Product Manager with Community Experience
2-4 years in a TPM role, with active community involvementSkills to master
- You'd bring a strong understanding of the product lifecycle and user needs. You'd need to hone your content creation, public speaking, and hands-on coding skills for advocacy, but your ability to translate user feedback into product requirements would be a huge asset.
You're ready to move on when
- Proven track record of launching successful technical products.
- Experience gathering and synthesising user feedback effectively.
- Strong communication skills, particularly in presenting technical roadmaps.
- Active participation in developer communities or user groups.