Developer advocate is one of the fastest-growing roles in tech — and one of the most misunderstood. At good companies, DAs are a growth multiplier. At bad companies, they're a marketing team with good PR skills.
This guide covers what developer advocacy actually is, how to build a DevRel program that drives measurable product growth, and how to become a developer advocate if you want the career path.
TL;DR
- A developer advocate's job is to make developers successful — with your product, and in their work generally
- The best DevRel programs are product-led, not marketing-led: DAs surface real developer pain, influence the roadmap, and build tools that developers actually use
- DevRel ROI is real but slow: expect 6-12 months before you see clear attribution to signups and retention
- The most effective DA skill: the ability to build something real and explain it clearly — technical credibility + communication
- AFFiNE scaled to 60k GitHub stars with 2 people doing DevRel — the leverage comes from creating content and communities that work without you
What Is a Developer Advocate?
A developer advocate is the bridge between a company and its developer community. The role has three core responsibilities:
1. External-facing: Educating developers about the product, creating technical content, speaking at events, participating in communities.
2. Internal-facing: Representing developer needs and feedback to the product team. A DA who only talks to developers externally is a marketer. A DA who also changes the roadmap is a growth lever.
3. Community building: Growing and nurturing the developer community around the product — whether that's a GitHub contributors community, a Discord server, a forum, or a conference program.
The balance of these three varies by company and stage. At Series A, DevRel is mostly external (get developers using the product). At Series C+, it shifts toward community infrastructure and internal influence.
Developer Advocate vs. Developer Evangelist vs. DevRel
These terms are often used interchangeably but have meaningful distinctions:
| Role | Focus | Direction | Typical Stage |
|---|---|---|---|
| Developer Advocate | Community + education | Bidirectional (inside-out and outside-in) | Series A+ |
| Developer Evangelist | Awareness + promotion | Mostly outbound | Enterprise/established companies |
| DevRel Engineer | Technical content + tools | Mostly technical | Later stage |
| Community Manager | Community health + engagement | Community-facing | Any stage |
| Head of DevRel | Program strategy + team | Strategic | Series B+ |
Modern job titles trend toward "Developer Advocate" because it implies the bidirectional nature of the role — advocating for developers to the company, not just advocating the company's products to developers.
What Developer Advocates Actually Do (Day-to-Day)
Content Creation (30-40% of time)
- Technical blog posts, tutorials, and guides
- Demo videos and live coding streams
- Conference talks and workshop materials
- Sample projects, starter templates, and code examples
- Documentation contributions (especially "getting started" guides)
Community Work (25-30% of time)
- Responding to questions on GitHub, Stack Overflow, Discord, Reddit
- Facilitating community events (AMAs, hackathons, office hours)
- Identifying and nurturing community contributors
- Monitoring community health metrics
Internal Feedback Loop (15-20% of time)
- Synthesizing developer feedback for the product team
- Writing internal reports on common pain points
- Participating in roadmap planning sessions
- Advocating for DX (Developer Experience) improvements
Events and Conferences (10-15% of time)
- Speaking at industry conferences
- Representing the company at meetups and hackathons
- Running a company conference or developer summit (larger teams)
Measurement and Strategy (10-15% of time)
- Tracking community health metrics
- Reporting on DevRel attribution
- Planning quarterly programs
The Developer Advocate Skill Stack
Technical Foundation (Non-Negotiable)
- Can write working code in at least one language your community uses
- Has built and deployed at least one project with your tech stack
- Can read and understand technical documentation
- Contributes to or maintains an open source project (ideally)
Communication Skills
- Technical writing: can explain complex concepts clearly to different audiences
- Public speaking: comfortable presenting to 10 people or 1,000
- Video production: can create useful screencasts/demos (basic video editing is fine)
- Community listening: reads developer conversations without projecting assumptions
Developer Empathy
- Has been a developer. Understands the pain of bad documentation, breaking API changes, and unclear error messages.
- Remembers what it was like to be a beginner in this ecosystem.
- Gets genuinely excited about good developer tools.
Business Acumen (Often Underrated)
- Understands how DevRel connects to product growth
- Can measure and communicate DevRel ROI
- Knows when a community interaction is a sales opportunity vs. a support issue
How to Become a Developer Advocate
Path 1: From Software Engineering
The most common path. You've been building things for 3-5 years, you like explaining technical concepts, and you want more of the community and communication side of the job.
How to transition:
- Start creating technical content publicly — blog posts, YouTube videos, conference talks
- Contribute actively to open source projects in your ecosystem
- Answer questions on Stack Overflow, GitHub Issues, Discord
- Apply for junior DA roles or developer experience engineering roles
- The portfolio of public technical content is your resume
Path 2: From Technical Writing or Documentation
You have the communication skills but want more technical depth. Focus on:
- Learning to build real projects (not just document them)
- Contributing code to open source projects
- Creating tutorials that involve actual code, not just explanations
Path 3: From Community Management
You have the community skills but need technical credibility. Focus on:
- Taking your company's developer courses and getting certified
- Building a project using the product you work with
- Starting to answer technical questions alongside the engineers
What to Include in Your Developer Advocate Portfolio
- Links to public technical writing (blog, Dev.to, Medium)
- GitHub profile showing contributions and projects
- Conference talk recordings or slides
- Community contributions (Stack Overflow reputation, Discord activity)
- A project you built that demonstrates your technical skills
Building a DevRel Program from Scratch: 90-Day Playbook
Days 1-30: Listen and Map
Don't create anything yet. Your first 30 days are about understanding the community.
Actions:
- [ ] Map every place developers talk about your product (GitHub Issues, Reddit, Discord, Stack Overflow, Twitter/X)
- [ ] Read every community question from the past 6 months. Categorize: What are the top 5 pain points?
- [ ] Identify your 10-20 most active community members (GitHub contributors, forum power users)
- [ ] Have 15 conversations with developers using the product — actual Zoom calls or DMs, not surveys
- [ ] Map the developer journey: how do developers discover, evaluate, and adopt the product?
Output: A community health snapshot and developer journey map. Share this with the product team.
Days 31-60: Create Foundation Content
Based on what you learned, create the 3-5 pieces of content that would have saved developers the most time.
Priority content types:
- Getting Started guide (if the current one is lacking)
- Top 5 use case tutorials (for the use cases developers actually have)
- "How to migrate from [most common alternative]" (biggest question at evaluation stage)
- Troubleshooting guide for the top 5 pain points
Distribute where developers are: Dev.to, the company blog, Reddit, Hacker News.
Days 61-90: Build Community Infrastructure
- [ ] Set up a Discord or Slack community (if one doesn't exist)
- [ ] Create a contributor recognition program
- [ ] Launch a weekly office hours or Q&A session
- [ ] Start a monthly developer newsletter
- [ ] Plan your first community event (virtual or in-person)
Output at day 90: Community baseline metrics established. Content attribution tracked. First community event completed. Report to leadership with data.
DevRel Metrics: What to Track
Community Health
- GitHub Stars: Total and velocity (stars per month)
- GitHub Contributors: Active contributors (past 90 days)
- Issue Response Time: Median time to first response on GitHub Issues
- Forum Activity: Posts, replies, and active members per month
- Discord/Slack MAU: Monthly active users
Content Performance
- Organic traffic from developer content: Sessions from blog posts, tutorials
- Content-to-signup conversion: % of content readers who sign up
- Video views and watch time: For YouTube/Loom content
- Conference talk reach: Attendees + recording views
Business Impact (Hardest to Measure, Most Important)
- DevRel-influenced pipeline: Deals where a DA touchpoint was in the journey
- Community-sourced signups: Signups attributed to community channels
- NPS from community members: Are community members more likely to recommend?
- Feature requests from DevRel feedback: How many roadmap items came from DA community insights?
The DevRel ROI Debate (And How to Win It)
DevRel is frequently questioned by finance teams because attribution is genuinely hard. Here's how to make the case:
The direct attribution play: Set up UTM tracking for all DevRel content. Track signups from blog posts, YouTube, conference links. Report monthly.
The indirect attribution play: Survey new signups — "How did you first hear about us?" Community mentions, developer content, and event exposure are DevRel attribution.
The retention play: Compare NPS and retention of community members vs. non-community users. Community members typically retain at higher rates (because they're invested). This is DevRel's most defensible business case.
The pipeline sourcing play: Ask the sales team to flag deals where developer content, a conference talk, or a community interaction was part of the buyer's journey. DevRel-influenced deals often close faster and at higher ACV.
Case Study: DevRel at AFFiNE (0 to 60k GitHub Stars)
AFFiNE is an open-source knowledge management tool. With a small team, they built one of the fastest-growing GitHub repositories in the productivity tools category.
DevRel structure: 2 people (the COO doing community and content, 1 developer doing technical tutorials). No dedicated DA title — DevRel was part of everyone's job.
What drove the 60k stars:
GitHub README as the product page: The README was written like a developer advocate wrote it — clear problem statement, compelling screenshots, instant setup instructions. First impressions in the developer community happen at the README level.
Authentic community seeding: Early participation in r/selfhosted, developer Discord servers, and Hacker News — providing value before promoting.
Product Hunt as a repeated event: 30+ launches over 18 months. Each launch created a newsletter spike that reached developer communities.
Contributors as advocates: AFFiNE invested in contributor onboarding — clear contribution guide, fast PR reviews, public recognition. Contributors became the most active community advocates because they had ownership.
Open source as the distribution mechanism: Being open source meant developers could evaluate the product before committing. The GitHub repo was the top-of-funnel.
Key lesson: At early stage, DevRel is mostly about building community trust — not about polished marketing. The team answered every GitHub issue, responded to every Reddit mention, and shipped fast enough to maintain community excitement.
DevRel Tools Stack
Community Platforms
- Discord — Best for real-time developer communities
- Discourse — Better for async Q&A and searchable knowledge base
- GitHub Discussions — Native to open source projects
- Slack — Better for B2B/enterprise developer communities
Content and Documentation
- Mintlify / Gitbook / Docusaurus — Developer documentation
- Dev.to / Hashnode — Developer-focused blogging
- YouTube / Loom — Video tutorials and demos
Analytics
- Orbit — Community analytics and member insights
- GitHub Insights — Repository analytics
- PostHog — Product analytics with open source option
- Common Room — Community engagement analytics
Event Management
- Hopin / StreamYard — Virtual events
- Meetup.com — In-person community events
- Eventbrite — Conference and workshop tickets
Developer Advocate Salary Data (2026)
US market data:
| Level | Base Salary | Total Comp |
|---|---|---|
| Entry-level DA | $90k-$120k | $100k-$140k |
| Mid-level DA | $130k-$160k | $150k-$200k |
| Senior DA | $170k-$220k | $200k-$280k |
| Head of DevRel | $200k-$260k | $240k-$350k |
| VP/Director of DevRel | $240k-$300k | $300k-$450k |
Factors that increase compensation:
- Deep expertise in a high-demand ecosystem (Rust, Go, AI/ML, Web3)
- Strong technical credibility (active open source contributions)
- Proven community growth track record
- FAANG or high-growth startup experience
- Strong conference speaking record
Remote-friendly: 70%+ of DevRel roles are fully remote or hybrid.
FAQ
What does a developer advocate do?
A developer advocate bridges the gap between a company and its developer community. Key responsibilities: creating technical content (tutorials, demos, blog posts), representing developer needs to the product team, speaking at conferences, building and nurturing communities, and measuring community health. The best DAs function as bidirectional translators — explaining the product to developers AND explaining developer needs to the company.
How much does a developer advocate earn?
In the US (2026): Entry-level: $90k-$120k base. Mid-level: $130k-$160k. Senior/Head of DevRel: $170k-$260k. Director/VP: $240k-$300k base. Total comp including equity can be significantly higher at growth-stage startups. DevRel roles at high-growth developer tool companies are among the best-compensated non-engineering tech roles.
Do you need to be a developer to be a developer advocate?
Not necessarily, but you need technical credibility. The most effective developer advocates have done meaningful technical work — built projects, contributed to open source, written code in production. You don't need to be a senior engineer, but you need to be able to build something real with the technology you're advocating for. Developers have a highly accurate BS detector for people who don't actually use the tools they promote.
What is the difference between DevRel and developer marketing?
Developer marketing focuses on campaigns, messaging, and channels to reach developers — it's mostly outbound. DevRel focuses on relationships, community, and technical credibility — it's bidirectional. At larger companies, these are separate functions. At startups, the same person often does both. Good DevRel makes developer marketing significantly more effective because the trust is already established.
Top comments (0)