Developer Relations Roadmap
You are the bridge between a product and the developers who use it - part engineer, part teacher, part community builder. Pay runs $85-115k US; the entry requirement is credibility, which is why DevRel is usually a second role built on real engineering plus a public teaching habit.
By Carl Mills • Last updated • tap any step for guidance and free resources • progress saves in your browser • free printable PDF roadmap poster.
Take this roadmap with you
Save your progress as a free personalized PDF study plan, plus one practical break-into-tech email each week. Unsubscribe anytime.
Developer Relations roadmap FAQ
How do I get into DevRel?
Build the job before you have it: pick technologies you genuinely use, publish consistently (posts, videos, talks), engage the community, contribute to OSS. DevRel hiring is portfolio hiring - your public work IS the interview. Most advocates come from engineering + a visible teaching habit.
Is DevRel engineering or marketing?
It reports into either, but the credible version is engineering-led: advocates who build real demos, file real issues and give honest feedback. If you cannot code the demos yourself, developers detect it instantly - which is why engineer-first entry is the reliable route.
How is DevRel measured?
Imperfectly - a known joke in the field. Common frames: content reach and engagement, developer signups/activation attributable to programs, community health, product feedback loops closed. Being fluent about measurement trade-offs is itself an interview differentiator.
What next once the list is green?
Prove it under pressure: take the free Mock Interview, then check your application signals.
Not sure this is your direction?
Compare every tech role - what you'd build, what it pays, and who it suits - on the roadmaps hub.
Compare all roadmaps