Career roadmap
Developer Advocate
Help developers succeed with a product in public, and bring what they tell you back to the people building it.
Before you start DevRel
- Real software engineering experience
- Willingness to write and speak publicly
- Genuine interest in helping other developers
Building in public
This role is hired on evidence. The evidence is public work.
The highest-volume output of the role and the main hiring signal.
- Tutorials that actually work end to end
- Explaining concepts without condescension
- Structure: problem, solution, why it matters
- Editing ruthlessly
Working code that people can run is worth more than any slide.
- Sample applications that are actually useful
- Repository hygiene and documentation
- Keeping demos working over time
- Open-source maintenance
Increasingly the primary channel for developer education.
- Screencast production basics
- Live coding without disaster
- Editing and pacing
- Distribution and thumbnails
Reach is part of the job description, and is measured.
- Choosing platforms deliberately
- Consistency over virality
- Engaging rather than broadcasting
- Avoiding hype and overselling
Advocates who cannot build lose their audience quickly.
- Maintaining engineering depth
- Learning new technologies fast
- Contributing to the product codebase
- Reading and reviewing code
BuildPublish six technical articles and one open-source project over the stage.
Speaking and community
Public speaking is a learnable skill and a hard requirement here.
Nerve-wracking, learnable, and the fastest way to build credibility.
- Talk structure and narrative
- Slide design for technical talks
- Live demo risk management
- Handling questions well
Writing proposals is a distinct skill from giving the talk.
- Writing a compelling abstract
- Matching a talk to a conference
- Building a speaking track record
- Handling rejection
Being genuinely useful in forums is where trust is built.
- Discord, forum and issue tracker presence
- Answering questions helpfully
- Handling hostility and criticism
- Recognising and elevating community members
Hands-on formats convert far better than talks.
- Workshop design and pacing
- Environment setup that works for everyone
- Supporting a room at different speeds
- Feedback collection
Running events is a common part of the role.
- Event planning and logistics
- Hackathon design
- Sponsorship and booth work
- Measuring event value
BuildDeliver three talks, from a local meetup to a recorded conference-style session.
Developer experience
The advocacy that matters most happens inside the company, on behalf of users.
The most-used part of any developer product, and usually the weakest.
- Tutorial, how-to, reference and explanation
- Getting started in under ten minutes
- Code samples that compile
- Keeping docs current with releases
Time to first successful call is the metric that predicts adoption.
- Measuring time to first success
- Removing signup and setup friction
- Error messages that teach
- Sandbox and trial environments
Advocates are usually the loudest internal voice on developer ergonomics.
- API design critique
- SDK ergonomics across languages
- Versioning and deprecation communication
- Consistency across surfaces
The 'advocate' half: representing developers to product and engineering.
- Structured feedback collection
- Turning anecdotes into evidence
- Influencing the roadmap
- Closing the loop with the community
Answering hard questions in public builds more trust than any campaign.
- Debugging someone else's integration
- Escalating bugs internally
- Managing expectations on fixes
- Turning support patterns into content
BuildRun a documentation and onboarding audit of a real product and ship three improvements.
Strategy and measurement
DevRel gets cut first when it cannot show impact. Measurement is survival.
The perennial problem of the field, and a guaranteed interview question.
- Awareness, activation and retention metrics
- Attribution difficulties, stated honestly
- Qualitative evidence that counts
- Reporting to leadership
Choosing which audiences and channels to invest in, and which to drop.
- Audience segmentation
- Channel selection and effort allocation
- Content strategy and calendars
- Aligning with company goals
DevRel sits between functions and must resist becoming pure marketing.
- Boundaries with marketing
- Working with product management
- Supporting sales without selling
- Maintaining community trust
One person does not scale. Programmes and community champions do.
- Champion and ambassador programmes
- Enabling community content
- Reusable content and templates
- Building a team
Your credibility is the asset. Spending it on a weak product destroys it.
- Honesty about product limitations
- Declining to promote something
- Handling competitive comparisons fairly
- Disclosure and transparency
BuildDefine a measurement framework for a DevRel programme and report on it for a month.
Interview preparation
Hiring is portfolio-driven, usually with a live talk or demo as the main round.
Give a technical talk to the hiring panel. The central interview.
- Choosing a topic that shows depth
- Handling a live demo
- Reading and adapting to the room
- Q&A under pressure
Usually a take-home tutorial or blog post on their product.
- Learning a product quickly
- Writing accurately from documentation
- Finding an angle that is genuinely useful
- Editing to a word count
You are still an engineer, and they will check.
- Building a small integration live
- Debugging an API problem
- Discussing architecture
- Reading unfamiliar code
How would you grow adoption of this product, and how would you measure it.
- Assessing a developer product's weaknesses
- Proposing a programme with priorities
- Defining success metrics
- Explaining DevRel value to a sceptic
The single largest factor in DevRel hiring.
- A body of published writing
- Recorded talks
- Open-source projects with users
- Evidence of community engagement
BuildA public portfolio: articles, talks, projects, and a rehearsed twenty-minute technical talk.
DevRel tools on your CV
- Git / GitHub
- Static site generators
- Screen recording tools
- Discord / Slack
- Analytics platforms
- Presentation tooling
What DevRel employers ask to see
- A body of published technical writing
- Recorded conference or meetup talks
- An open-source project with real users
- A documented developer experience improvement
Any company selling to developers needs it: APIs, infrastructure, tooling and AI platforms. Small field, highly visible, and hiring is driven almost entirely by public work.
Content last reviewed 2026-08-31. Guidance only — no institute or paid placement is endorsed anywhere in this book.