DevRel

SR18 — Developer Advocate / Developer Relations (DevRel)

Version: 1.0
Date: April 2026
Audience: Software engineers considering a public-facing role; community builders; technical writers entering product teams; career changers from engineering to developer engagement.

Overview

Developer Relations (DevRel) bridges the product team and developer community. Unlike pure engineering roles (focused on building the product) or pure marketing (focused on closing deals), Developer Advocates are paid to:

• Understand what developers need and translate that back to product teams
• Educate developers through blogs, tutorials, sample code, and conference talks
• Advocate for developer concerns in product roadmap discussions
• Build and nurture thriving communities around the platform

This is a high-visibility, high-impact, high-burnout career path. Success requires deep technical credibility (you must have shipped real code or contributed to open-source), public communication skill (blogs, talks, social media), and genuine passion for helping others. DevRel is fundamentally not a fast track to promotion or six-figure compensation—it's a career for people who love both engineering and mentorship.

Why This Role Exists

DevRel emerged in the late 2000s as venture-backed infrastructure and SaaS companies (MongoDB, SendGrid, Auth0, Twilio) realized that developer adoption depends on three things:

1. Great documentation and examples — developers won't adopt your API if they don't understand it
2. Community and trust — developers adopt products used by peers they respect
3. Feedback loop — product teams need to hear what developers actually want, not what sales thinks they want

DevRel is the glue. A strong DevRel program:

• Reduces time-to-first-API-call (lowers friction)
• Generates word-of-mouth adoption (cheaper than paid sales for developer products)
• Prevents product team blind spots (captures real developer pain points)
• Builds defensibility (switching cost increases when community is strong and engaged)

Citation: The DevRel Collective community (https://devrelcollective.fun/) survey data shows that companies with mature DevRel programs report 2-3x higher developer adoption and 40% lower customer churn compared to product-only strategies. This is the foundation of modern PLG (product-led growth) in developer tools.

Career Stages & Compensation

DevRel compensation varies widely based on company stage, product type, and geography. Below are industry benchmarks from multiple sources.

1. Junior Developer Advocate

Scope: Create tutorials and sample code; co-author blog posts; participate in community moderation; attend local meetups and small conferences.

Typical background: Recent bootcamp graduate with strong OSS contributions, or 2-3 years as junior engineer with some writing/speaking experience.

Salary range: USD $90,000–$125,000
Median (US, 2025-2026): ~$108,000

Sources:

• Glassdoor: "Developer Advocate" (US), mid-tier tech companies, 0-3 years experience
• levels.fyi DevRel salary data (self-reported, 2025-2026)
• DevRel Collective community survey (community-contributed, varies by region)

Benefits & equity: Early-stage startups offer 0.05–0.20% equity; established companies offer stock options vesting over 4 years.

2. Developer Advocate / DevRel Engineer

Scope: Independently own blog publication; deliver 4-8 conference talks per year; manage community Discord/Slack channels; maintain tutorial repositories; coordinate with product on developer feedback; measure engagement metrics (NPS, MQL attribution, adoption rates).

Typical background: 4-6 years as engineer (with public speaking/writing history), or senior bootcamp grad who shipped open-source.

Salary range: USD $125,000–$175,000
Median (US, 2025-2026): ~$150,000

Sources:

• Glassdoor: "Developer Advocate" (US), mid-to-large companies, 3-6 years experience
• levels.fyi DevRel: mid-level tier (shows $125K–$175K range across Google, Amazon, smaller SaaS)
• DevRel Collective member testimonials (community Slack)

Benefits & equity: Established companies offer full health coverage, 401(k), and modest equity; startups offer higher equity (0.15–0.50%) with lower base.

3. Senior Developer Advocate

Scope: Lead DevRel strategy for a product line or region; mentor junior advocates; own demand-generation metrics; author technical books or popular courses; keynote at major conferences; shape product roadmap feedback.

Typical background: 6-10 years as engineer + 2-4 years active DevRel, or transferring from Tech Lead → DevRel with strong community presence.

Salary range: USD $160,000–$220,000
Median (US, 2025-2026): ~$190,000

Sources:

• levels.fyi DevRel: senior level
• Glassdoor senior DevRel roles (major tech companies)
• PayScale (reports $160K–$210K for "Senior Developer Advocate")

Equity: Vested stock from previous years + additional grants; can represent significant total comp (30-40% of base).

4. Principal / Staff Developer Advocate

Scope: Define DevRel strategy across multiple products or the entire company; lead a team of 5-15 advocates; represent the company at the highest levels of industry conferences; own product-to-community feedback loop; own ROI metrics for the entire DevRel program.

Typical background: 10+ years engineering + 4-6 years senior DevRel, or hired from competing company as thought leader.

Salary range: USD $190,000–$260,000
Median (US, 2025-2026): ~$225,000

Sources:

• levels.fyi: Principal/Staff level
• Blind community salary sharing (anonymous, 2025)
• Major tech companies' published leveling data

Equity: Significant annual grants; total comp often $280K–$350K when stock is included.

5. Head of DevRel / VP DevRel

Scope: Own entire DevRel function; budget and hiring; strategy and OKRs; cross-functional alignment (product, marketing, sales, engineering); report to Chief Product Officer or CTO.

Typical background: 8+ years as engineer/architect + 6+ years DevRel leadership.

Salary range: USD $220,000–$350,000+
Median (US, 2025-2026): ~$280,000

Sources:

• levels.fyi executive level
• Compensation.com (VP roles at 100+ employee companies)
• Heidrick & Struggles executive compensation (major tech companies show range of $220K–$400K base + bonus + equity)

Equity + bonus: VP roles typically include 10-40% annual bonus and equity packages worth $50K–$150K annually.

Skills Required

DevRel success demands a unique intersection of technical depth and communication breadth. Below are the core skills.

Technical

• Software architecture and system design — you need to understand the "why" behind products you advocate for, not just the "how"
• Multiple programming languages — at minimum, fluency in the primary language of your product ecosystem (Python for ML/data tools, Node.js for JavaScript ecosystems, Java for enterprise tools, Go for infrastructure)
• Open-source contribution — you must have shipped code in public repositories. This is non-negotiable for credibility.
• SDK / library design — understanding how to use your own APIs from first-principles perspective
• API testing and debugging — rapid prototyping with your company's APIs and competitors'

Writing

• Technical blog posts — 1,500–5,000 word tutorials explaining concepts to developers unfamiliar with your product
• Documentation clarity — contributing to and reviewing API docs, guides, and getting-started tutorials
• Email and community communication — Discord/Slack community management, thoughtful responses to questions
• Long-form analysis — whitepapers, case studies, architecture breakdowns

Speaking

• Conference talks — 30-45 minute talks at 10-20 conferences per year; ability to tell stories, not recite slides
• Webinars and workshops — live coding demonstrations
• Impromptu live coding — debugging code in front of an audience without a net
• Podcast interviews — articulate technical concepts for non-specialist audiences

Community & Metrics

• Community moderation — Discord, Slack, Discourse, Reddit, Hacker News; ability to de-escalate conflict, recognize spam, amplify helpful voices
• Social media presence — maintaining Twitter/X, LinkedIn, and Medium; ability to recognize and engage with conversations early
• Feedback synthesis — collecting qualitative feedback from hundreds of developers and distilling into 3-5 actionable product insights
• Metrics literacy — understanding NPS, MQL (marketing-qualified lead) attribution, API adoption curves, developer retention rates, conference ROI

Product Feedback

• Data-driven advocacy — translating community feedback into prioritized product requests with supporting evidence
• Product roadmap alignment — understanding why you can't always get what developers want (technical debt, competing priorities) and communicating that tradeoff clearly

Sub-Specializations

DevRel is not a single track. Depending on company size, product, and your background, you may specialize.

1. Developer Education (DevEdu)

Focus: Curriculum design, structured learning paths, video tutorials, certification programs, online courses.

Typical company: Stripe, Auth0, MongoDB, Twilio (products with high learning curves)

Skills emphasized: Curriculum design, pedagogy, video production, asynchronous teaching, assessment design

Compensation: Same as general DevRel; sometimes slightly lower (education roles are commoditized) or higher (video production expertise is scarce)

Career trajectory: DevEdu → Content Leader → Learning Org leadership

Notable practitioners:

• Wes Bos (JavaScript courses, personal brand-driven)
• Jessica Rose (formerly Slack, now independent)

2. Developer Marketing (DevMktg)

Focus: Demand generation, content marketing, SEO for developer tools, API documentation as marketing, webinar strategy.

Typical company: SaaS startups (SendGrid, Segment, Mixpanel); heavy emphasis on lead generation

Skills emphasized: Content strategy, analytics, funnel optimization, ABM (account-based marketing), copywriting

Compensation: Typically higher than pure DevRel (often $140K–$190K range); marketing budgets are larger than community budgets

Career trajectory: DevMktg → Product Marketing Manager → Marketing Director

Challenge: Risk of "becoming a marketing puppet" — developers can sense when content is inauthentic or purely commercial. Requires careful balance.

3. Developer Experience / DX Engineering

Focus: SDK design and quality, internal tooling for developers, API ergonomics, language-specific libraries, documentation automation.

Typical company: Infrastructure companies (Vercel, Stripe, Firebase, Supabase); building developer productivity tools

Skills emphasized: Software engineering (still building code), UX research, API design, polyglot programming

Compensation: Same as senior engineer ($160K–$220K range); sometimes commands premium because it's engineer-heavy

Career trajectory: DX Engineer → Developer Platform Lead → VP Product

Notable practitioners:

• Nicole Forsgren (Stripe, then GitHub, now independent researcher)
• Charity Majors (Honeycomb; DX + observability)

Distinction from DevRel: DX engineers build tooling; DevRel advocates for it. Many roles blend the two.

4. Developer Community / Community Management

Focus: Discord, Slack, Discourse, Reddit community moderation; event organization; grassroots community building; "keeping the vibes right"

Typical company: Any company with an active community (Kubernetes, React, Next.js; or company-owned communities like Stripe's ecosystem)

Skills emphasized: Conflict resolution, recognition systems, event logistics, sociological awareness (what drives community health?)

Compensation: Often slightly lower ($110K–$160K range); fewer growth opportunities within a single company

Career trajectory: Community Manager → Community Lead → Community Director → small-company VP

Challenge: Emotional labor and burnout from unpaid problem-solving; community members often feel entitled to 24/7 support

5. General Developer Relations

Hybrid role balancing all of the above: writing, speaking, community, product feedback, education. This is the most common path.

Compensation: Mid-range, $125K–$175K, depending on level.

Career progression: Junior → Mid → Senior → Principal → Director/VP

How to Enter DevRel

There is no certification path for DevRel. The field is entirely portfolio-driven.

Paths into DevRel

Path 1: Senior Engineer → DevRel (Most Common)

Prerequisites:

• 4-6+ years as software engineer (full-stack, backend, or infrastructure preferred)
• Shipped at least one non-trivial open-source project or contributed significantly to an existing major project
• Published 5-10 blog posts on technical topics
• Given at least 2-3 conference talks or meetup presentations
• Active on Twitter/X or another developer social platform

How to break in:

1. Deepen OSS contributions — contribute to projects related to your target company's ecosystem
2. Start a blog or podcast — regular writing or audio content; consistency matters more than virality
3. Speak at meetups and smaller conferences — PyCon regional, DevOps Days, smaller cons (lower barrier than KubeCon)
4. Build a network — connect with other DevRel practitioners, attend DevRel Collective events
5. Target early-stage startups or established companies with open positions — startups are more willing to hire "devrel-curious" engineers; larger companies look for the full portfolio

Timeline: 2-3 years of deliberate effort as engineer + 1-2 years of OSS/public activity before you're hireable

Example trajectory:

• Years 1-4: Backend engineer at startup (Python/Go)
• Years 4-5: Increased OSS contributions (3+ projects on GitHub), 2 conference talks, 8 blog posts
• Year 6: Hired as Junior DevRel at infrastructure startup
• Year 8: Senior DevRel at mid-sized SaaS company

Path 2: Tech Writer → DevRel

Prerequisites:

• 3-5 years as technical writer (API documentation, tutorials, developer guides)
• Strong coding skills (can read and write code samples, understand architecture)
• Portfolio of well-written, well-structured documentation

How to break in:

1. Expand beyond writing — contribute to or create an example repository; make code runnable, not just "prose about code"
2. Publish independent writing — start a technical blog beyond company-owned docs
3. Give talks — present your doc writing expertise or technical topic at meetups
4. Connect with DevRel hiring managers — DevRel values the discipline that good technical writing teaches

Timeline: 2-3 years as tech writer + 1-2 years of outside portfolio

Path 3: Developer Relations Coordinator → Advocate

Prerequisites:

• 1-2 years managing events, sponsorships, or community programs for a tech company (no coding required)
• Learning to code (Python, JavaScript, or Go) through bootcamp or self-study

How to break in:

1. Learn to ship code — bootcamp or self-study project-based; commit to it for 6-12 months
2. Contribute to the company's OSS — show capability through internal projects first
3. Shadow a DevRel engineer — learn the blog-and-speak side of the role
4. Apply for Junior Developer Advocate role — coordinator experience + new coding skill is a viable entry point

Timeline: 2-3 years (bootcamp + coordinator work can overlap)

Path 4: Career Changer with OSS Passion

Prerequisites:

• 2-3 years as software engineer in any other field (fintech, healthcare, e-commerce)
• Strong GitHub profile (repos with stars, consistent contributions)
• Personal blog or published technical writing

How to break in:

1. Target specific company in field you know — bring domain expertise (e.g., fintech engineer → DevRel at fintech API company)
2. Build sample project using target company's APIs — demonstrate expertise through a working example
3. Write case study or technical blog post — show how the APIs solved a real problem
4. Apply for DevRel role — leverage both domain expertise and public contributions

Timeline: 3-5 years total

Books & Learning Resources

DevRel has a growing canon of books and free resources. Below are the essential reads.

Paid Books

1. "Developer Relations: How to Build and Grow a Successful Developer Program" (Lewko & Parton, Apress, 2017)

   • The foundational text for DevRel strategy
   • Covers program design, metrics, career progression
   • Focus on enterprise/large-company DevRel
   • Citation: Apress official book page; widely cited in DevRel Collective community

2. "The Business Value of Developer Relations: How to Advocate for Developers" (Mary Thengvall, Apress, 2021)

   • Business case for DevRel; metrics and ROI
   • How to hire and scale DevRel teams
   • Emphasis on cross-functional collaboration
   • Citation: Apress; widely recommended in DevRel communities

3. "Talking to Humans: Success Starts With Understanding Your Customers" (Constable & Rimalovski, self-published, 2014)

   • Not DevRel-specific, but essential for customer research
   • How to conduct user interviews, synthesize feedback
   • Directly applicable to DevRel feedback loop
   • Citation: self-published; widely cited by product and DevRel teams

4. "Made to Stick: Why Some Ideas Survive and Others Die" (Chip & Dan Heath, Random House, 2007)

   • Communication and messaging frameworks
   • Why some explanations resonate; others don't
   • Essential for conference talks and content strategy
   • Citation: Random House; bestseller in communication field

5. "Documenting Software Architectures: Views and Beyond" (Bass, Clements, Kazman, Addison-Wesley, 2012)

   • How to think about and document system design
   • Essential for DevRel who explain architectures
   • Dry but precise
   • Citation: SEI / Carnegie Mellon; standard reference

Free Resources

DevRel Collective Community (https://devrelcollective.fun/)

• Type: Community platform + conference
• Content: Job board, Slack community (~2,000+ members), annual conference (DevRelCon)
• Cost: Community is free; DevRelCon tickets are $200–$500
• Use: Best source for real DevRel people, trends, and job openings
• Citation: Community-operated; most important DevRel gathering point as of 2026

Mary Thengvall's Blog (https://www.persea-consulting.com/)

• Type: Independent consulting + thought leadership
• Content: Articles on DevRel strategy, case studies, metrics, team dynamics
• Cost: Free blog; consulting services paid
• Citation: Mary Thengvall is a DevRel pioneer; her blog is a primary source for modern DevRel thinking

Developer Avocados Podcast (https://developeravocados.net/)

• Type: Weekly podcast
• Episodes: Interviews with DevRel practitioners, discussions of tools, trends, and challenges
• Cost: Free
• Citation: Long-running community podcast; hosted by Sam Julien and Melissa Collier

"A Guide to Developer Relations" (Fireside Chats, various)

• Type: Blog series + talks
• Content: Practical guides on building DevRel programs
• Cost: Free
• Citation: Community-contributed; curated by DevRel Collective

"The Business Value of Developer Relations" (short version) (Mary Thengvall, LinkedIn Pulse / Medium)

• Type: Article series
• Content: Condensed version of the book
• Cost: Free
• Citation: Published on major platforms

Communities & Networking

DevRel is hyperlocal and hypernetworked. Below are the key communities.

Online Communities

1. DevRel Collective Slack (https://devrelcollective.fun/)

   • Size: ~2,000+ members worldwide
   • Activity: Job posts, technical discussions, casual chat
   • Culture: Inclusive, mentor-heavy, "no stupid questions"
   • Citation: Official community platform

2. Developer Avocados Discord (https://developeravocados.net/)

   • Size: ~500+ active members
   • Activity: Weekly discussions, resource sharing, events
   • Citation: Community-run

3. r/devrel (https://www.reddit.com/r/devrel/)

   • Size: ~1,500 subscribers (small compared to r/Python or r/golang)
   • Activity: Moderate; more career questions than strategy
   • Citation: Reddit

4. Dev.to (https://dev.to/)

   • Type: Multi-topic platform but strong DevRel presence
   • Activity: Blog posts, discussions, community showcases
   • Citation: Independent platform

In-Person / Annual Conferences

1. DevRelCon (https://devrelcollective.fun/)

   • Schedule: Annual conference (spring/fall); also regional variants (DevRelCon Earth online)
   • Location: Rotating (London, San Francisco, Tokyo)
   • Attendance: 200–600 DevRel professionals
   • Talks: Strategy, case studies, metrics, community
   • Citation: Largest dedicated DevRel conference; official DevRel Collective event

2. KubeCon / Cloud Native Con (CNCF)

   • Schedule: Biannual (spring/autumn)
   • Location: Multiple continents
   • Attendance: 10,000+ engineers and operators
   • DevRel angle: Strong community networking for infrastructure/cloud DevRel
   • Citation: CNCF official conference

3. React Conf / Next.js Conf (Vercel / Meta)

   • Schedule: Biannual
   • Attendance: 1,000–3,000
   • DevRel angle: For JavaScript ecosystem DevRel practitioners
   • Citation: Official conferences

4. PyCon (Python Software Foundation)

   • Schedule: Annual (typically May)
   • Attendance: 3,000–4,000 across US regional conferences
   • DevRel angle: Python tools and infrastructure DevRel
   • Citation: Official Python conference

5. AWS re:Invent / Microsoft Ignite / Google Cloud Summit

   • Schedule: Annual
   • Attendance: 10,000–50,000+
   • DevRel angle: Corporate DevRel networking (Amazon, Microsoft, Google DevRel teams present)
   • Citation: Official vendor conferences

Certifications (None)

DevRel has zero formal certification pathways. The field is entirely portfolio-driven and peer-evaluated.

No organization (Linux Foundation, CompTIA, AWS, Google Cloud, etc.) issues "Developer Advocate Certification." This is by design — the role is so new and specialized that standardization is premature.

What substitutes for certification:

• GitHub contributions + open-source portfolio
• Blog audience and engagement metrics
• Conference speaking history
• Social media following and influence
• Published technical writing (books, longform articles)
• Peer recognition (recommendation from other DevRel practitioners)

Salary Negotiation & Career Ceiling

Negotiation Points

1. Conference budget — DevRel income is heavily tied to speaking; negotiate 4-8 annual conference stipends (flights + hotels + registration)
2. Content creation time — negotiate 20-30% of your week reserved for writing, without interrupt-driven work (very hard to enforce)
3. Flexible location — DevRel often requires travel; negotiate remote-first schedules with periodic in-office weeks
4. Speaking honorariums — many conferences offer speaker travel coverage; negotiate whether you keep it or it goes back to company
5. Equity vesting schedule — in startup equity negotiation, DevRel roles often start lower than engineering; push back if you have strong OSS track record

Career Ceiling

Structural reality: DevRel careers have a lower ceiling than engineering management or product management.

• VP DevRel is a plausible end-state for exceptional practitioners; salaries reach $300K–$400K+ total comp
• Chief Evangelist or VP Developer Platform roles exist at large companies but are rare
• Transition paths: Senior DevRel → Product Manager, Director of Marketing, CTO, or independent consultant/content creator (common)

Why the ceiling:

• DevRel is still considered a cost center by many finance teams (spend money on advocacy, which doesn't directly close deals)
• Few companies have enough product complexity to justify 10+ person DevRel teams
• Engineering and Product Management roles scale deeper and have clearer advancement

Sustainable path: Most senior DevRel practitioners eventually move to:

1. Independent consulting — helping startups build DevRel programs ($150K–$300K/year)
2. Content creation / personal brand — Patreon, courses, affiliate revenue
3. Product management — leverage deep community knowledge
4. Founder — building tools for developers (SaaS, open-source)

Failure Modes & Burnout Drivers

1. "Becoming a Marketing Puppet"

The trap: Your DevRel program is measured purely on lead generation (MQLs, webinar attendance, email list growth) rather than developer satisfaction or product feedback quality.

Symptoms:

• You're pressured to "write more posts" but company ignores what developers actually ask for
• Conference talks are 50% sales pitch, 50% technical content
• Blog metrics are vanity (clicks) not impact (code written, feedback acted upon)

Prevention:

• Establish metrics that balance acquisition (leads) with retention (NPS, adoption, churn reduction)
• Write contracts with marketing stakeholders that protect DevRel independence
• Keep a "no BS" policy: if data doesn't support a claim, don't publish it

2. Burnout from Travel

The trap: "8 conferences a year" becomes 14 conferences per year; you're living out of a suitcase, missing family events, battling jet lag.

Symptoms:

• Fatigue, health problems, relationship strain
• Quality of talks and writing drops (exhaustion)
• Resentment toward the job itself

Prevention:

• Negotiate a hard cap on annual conference days (60–80 days/year max)
• Cluster conferences geographically when possible
• Require 1 week off after every 3 conferences
• Invest in travel comfort (good hotels, airlines, noise-canceling headphones)

3. Losing Technical Credibility

The trap: After 2-3 years of mostly speaking and writing, your technical skills atrophy. You can no longer ship code or debug live. Developers sense the decline; your credibility evaporates.

Symptoms:

• Can't answer detailed technical questions
• Your code examples are outdated or wrong
• You miss industry shifts (e.g., Kubernetes adoption change)

Prevention:

• Allocate 20–30% of your time to shipping code — maintain at least one OSS repo or example project
• Keep a "technical debt tracker" — if you can't complete a 2-week coding project, refocus
• Stay on top of industry trends (conferences, blogs, RFCs, GitHub Trending)

4. Underestimating Community Moderation Effort

The trap: You launch a Discord or Slack for your community; it grows to 1,000+ people; you're now answering questions 24/7 or hiring a full-time moderator.

Symptoms:

• Unmoderated spam/toxicity
• Bad actors or discriminatory behavior
• Your own sanity/work-life balance suffers

Prevention:

• Build community guidelines before launch
• Recruit volunteer moderators (offer stickers, swag, or stipends)
• Use moderation bots (Discord / Slack plugins) aggressively
• Set expectations: "Response times are business hours, not 24/7"

5. Friction with Product Teams

The trap: You collect tons of developer feedback; product team ignores it or dismisses it as "not representative" or "niche requests."

Symptoms:

• Developers feel unheard
• Your credibility with community declines
• Your job feels pointless

Prevention:

• Frame feedback quantitatively: "50% of surveyed developers asked for X" (not "I heard about X once")
• Build relationships with product managers early; understand their constraints
• Escalate roadmap decisions that conflict with community feedback to leadership
• Be transparent: "Here's why we're not building X (competing priority, technical debt, etc.)"

2026 Landscape & Trends

AI-Augmented Content Generation

Trend: Generative AI (ChatGPT, Claude, GitHub Copilot) is accelerating content production but also increasing quality expectations.

Impact on DevRel:

• You can generate first drafts of blog posts faster; mandatory human editing and fact-checking
• Tutorial code examples are faster to prototype; still need rigorous testing
• Webinar slides auto-generate from outlines; narration still requires authentic voice

Reality check: Companies are beginning to hire "AI-skeptical" DevRel leads specifically to ensure community trust. Shipping low-quality ChatGPT posts erodes credibility.

Citation: Developer Avocados podcast episodes (2025-2026) on "AI and DevRel"; Mary Thengvall's Slack community discussions

Economic Compression of DevRel Teams

Trend: 2023-2024 saw startup layoffs in DevRel functions; some companies cutting from 8-person teams to 3-person teams.

Impact:

• Individual DevRel load increases (more writing, more speaking, more community)
• Role becomes more hybrid (less specialization, more "do everything")
• Job security is lower; individual contributor DevRel roles at startups are at risk

Who's hiring:

• Profitable SaaS companies (Stripe, Vercel, LaunchDarkly, etc.)
• Large tech companies (Google Cloud, AWS, Microsoft, GitHub)
• Bootstrapped startups with strong community roots

Citation: Blind community salary discussions (2024-2025); DevRel Collective Slack job board trends

Focus on Metrics Maturity

Trend: DevRel programs are moving from "vanity metrics" (blog views, Twitter followers) to business metrics (product adoption, MQL attribution, NPS impact, churn reduction).

Impact:

• DevRel roles now require SQL/analytics literacy
• DevRel budgets are justified with financial models
• Programs measuring "developer happiness" compete with programs measuring "revenue impact"

Citation: "The Business Value of Developer Relations" (Thengvall) frameworks; levels.fyi DevRel salary data shows premium for analytics-savvy roles

Notable DevRel Practitioners

These individuals are recognized for pioneering DevRel practices or building notable communities.

Current / Recent

1. Jessica West (https://www.jessicawest.dev/)

   • Background: Engineer → API evangelist (Auth0, Vonage)
   • Known for: DX frameworks, API design advocacy
   • Platform: Personal brand + conference speaking

2. Mary Thengvall (https://www.persea-consulting.com/)

   • Background: Community manager → DevRel at Traction Guest, Linux Academy, SendGrid
   • Known for: DevRel strategic thinking, metrics frameworks
   • Current: Independent consultant + author

3. Adam Wiggins (https://adamwiggins.com/)

   • Background: Co-founder of Heroku
   • Known for: Developer experience thinking (12-factor app)
   • Current: Coinbase + independent thought leadership

4. Kelsey Hightower (https://kelseyhightower.com/)

   • Background: Systems engineer at Google
   • Known for: Kubernetes ecosystem advocacy, technical authority
   • Current: Google Cloud + independent
   • Note: Blurs line between engineer and advocate; rare combination of credibility

5. Bret Comnes

   • Background: Node.js and web standards communities
   • Known for: Open web platform advocacy
   • Platform: GitHub + community leadership

South African Context

DevRel is rare in South Africa but growing.

Current Market (2026)

• Positions: Handful of roles at multinational tech companies with ZA offices (Microsoft ZA, Amazon ZA, Google ZA)
• Startups: Limited; most SA startups are B2B SaaS (e.g., Superbalist, Takealot tech teams) without dedicated DevRel
• Remote possibilities: Many US and UK DevRel roles are fully remote; SA-based DevRel practitioners often work for foreign companies

Salary Context

• Junior DevRel: ZAR 1,400,000–1,800,000/year (approximately)
• Mid-level DevRel: ZAR 1,900,000–2,500,000/year (approximately)
• Senior DevRel: ZAR 2,500,000–3,300,000/year (approximately)

Conversion note: Based on ~ZAR 18 = 1 USD (April 2026 rate); DevRel salaries in SA are lower than US equivalents due to market size and cost of living.

Sources:

• PayScale ZA; Glassdoor ZA (limited data)
• Salary surveys from recruitment agencies (Michael Page, Pnet)
• Remote DevRel roles at US companies (often paid in USD with ZA-adjusted contracts)

Path Forward for SA Professionals

1. Build OSS reputation — ZA has strong engineering talent; open-source contributions are globally visible
2. Remote-first approach — target DevRel roles at US/UK companies that hire remote
3. Specialize in underserved ecosystems — e.g., Afro-tech communities, emerging market mobile Dev (Flutter, React Native)
4. Consulting path — help African startups build community programs (bootstrapped approach, lower barriers)

Key Takeaways

1. DevRel is a high-impact, high-visibility, moderately-well-paid career for engineers and writers who love both technical depth and community.

2. Entry barriers are real but surmountable: you need OSS contributions, public speaking experience, and a blog. 2-3 years of deliberate portfolio-building, then hiring is feasible.

3. Compensation ranges from $90K (junior) to $300K+ (VP), with median around $150K–$190K for mid-level roles.

4. No certifications exist. Credibility is entirely portfolio-driven (GitHub, blog, conference talks, social presence).

5. Burnout is structural: travel, moderation load, friction with product teams, and pressure to become "marketing" are real risks. Mitigate with clear boundaries and metrics.

6. Career ceiling is lower than engineering management or product management. Most senior practitioners transition to consulting, personal brand, product, or founding.

7. 2026 landscape: AI-augmented content, economic compression of teams, focus on metrics maturity, and continued growth in infrastructure/cloud ecosystems.

8. South African context: Market is small; remote work is the primary path. Building global reputation through OSS is essential.

Sources

Books

• Lewko & Parton (2017). Developer Relations: How to Build and Grow a Successful Developer Program. Apress.
• Thengvall, Mary (2021). The Business Value of Developer Relations: How to Advocate for Developers. Apress.
• Constable & Rimalovski (2014). Talking to Humans: Success Starts With Understanding Your Customers. Self-published.
• Heath, Chip & Dan (2007). Made to Stick: Why Some Ideas Survive and Others Die. Random House.
• Bass, Clements, Kazman (2012). Documenting Software Architectures: Views and Beyond. Addison-Wesley / SEI.

Communities & Organizations

• DevRel Collective (https://devrelcollective.fun/) — official community platform, conferences, Slack
• Developer Avocados Podcast (https://developeravocados.net/) — weekly interviews and discussions
• Mary Thengvall / Persea Consulting (https://www.persea-consulting.com/) — independent strategy and consulting

Salary Data & Surveys

• Glassdoor (US, 2025-2026): "Developer Advocate" salary range by years of experience
• levels.fyi DevRel: crowd-sourced compensation data from technology companies
• DevRel Collective community survey: self-reported compensation data from DevRel practitioners
• PayScale (US & ZA, 2025-2026): "Senior Developer Advocate," "VP Developer Relations"
• Blind community: anonymous salary sharing (2024-2025)
• Heidrick & Struggles (2025): Executive compensation benchmarking for VP roles at 100+ employee tech companies
• Michael Page ZA & Pnet (2025-2026): SA recruitment salary benchmarks

Practitioner Platforms

• Jessica West (https://www.jessicawest.dev/)
• Mary Thengvall (https://www.persea-consulting.com/)
• Adam Wiggins (https://adamwiggins.com/)
• Kelsey Hightower (https://kelseyhightower.com/)
• Bret Comnes (GitHub: bcomes)

Conference Data

• DevRelCon (annual conference): attendance and speaker lists (https://devrelcollective.fun/)
• KubeCon / Cloud Native Con (CNCF): annual conference schedule and attendance
• PyCon (Python Software Foundation): annual conference
• AWS re:Invent, Microsoft Ignite, Google Cloud Summit: annual vendor conferences

Industry Discussions

• r/devrel (Reddit): career questions and discussions
• Developer Avocados Slack & Discord: community discussions on trends and burnout
• DevRel Collective Slack: job postings and strategy discussions

Regional Data

• Glassdoor ZA, PayScale ZA: South African salary benchmarks
• Michael Page ZA, Pnet recruitment: SA market salary data
• Remote job platforms (Remote.co, We Work Remotely): remote DevRel positions and rates

Certifications — Quick Reference Table

DevRel does not have a single dominant certification pathway. Unlike AWS or Google Cloud roles, there is no universally-recognized "Developer Advocate Certification." However, DevRel practitioners often pursue foundational and vendor credentials to strengthen their platform knowledge:

Relevant Certifications & Training

Key Insight

Portfolio matters more than credentials. Hiring managers evaluate DevRel candidates primarily on:

• GitHub contributions and open-source portfolio
• Blog audience and engagement metrics
• Conference speaking history (verified via speaker databases like Papercall, Sessionize)
• Social media presence (Twitter/X, LinkedIn, YouTube followings)
• Published technical writing (Medium, Dev.to, company blogs)

Certifications are supplementary and can signal platform knowledge (AWS, Azure, GCP), but they do not substitute for demonstrated community work.

Free Training Resources

Communities & Event Platforms

• DevRel Collective (https://devrelcollective.fun/)

  • Free Slack community (~2,000+ members)
  • Annual DevRelCon conference (USD $200–$500 tickets)
  • Job board for DevRel openings
  • Curated "Awesome DevRel" resources: https://github.com/devrelcollective/awesome-devrel

• Developer Avocados (https://developeravocados.net/)

  • Free weekly podcast with interviews from active DevRel practitioners
  • Community Discord for discussions
  • Guest speakers include Emmy Buttner, Sam Julien, Melissa Collier

• DevRel Foundation (https://dev-rel.org/)

  • Mission: elevate professional practice through open-source resources
  • Community collaboration on DevRel standards and training
  • Free and paid educational content

• Common Room DevRel Resources (https://www.commonroom.io/resources/community/developer-relations/)

  • Campaign strategy templates and playbooks
  • DevRel scaling guides
  • Case studies and customer stories
  • DevRel job titles & career progression reports

YouTube Channels & Influencers

• Wesley Faulkner (https://wesleyfaulkner.com/)

  • DevRel expert & Chairperson of DevRel Foundation
  • YouTube: talks on community building, diversity in tech, neurodiversity advocacy
  • LinkedIn: https://www.linkedin.com/in/wesley83/

• Mary Thengvall (https://www.marythengvall.com/)

  • DevRel pioneer & author
  • Articles on strategy, metrics, team dynamics
  • Personal consulting: https://www.persea-consulting.com/

• Jeremy Meiss (https://jmeiss.me/)

  • DevEx & DevRel leader; formerly CircleCI, Auth0, Solace
  • Podcast appearances & community discussions
  • LinkedIn: https://www.linkedin.com/in/jeremymeiss/

• Aja Hammerly (https://www.linkedin.com/in/ajahammerly)

  • Developer Relations Manager at Google Cloud
  • Technical writing & speaking on DevRel practices

• Emma Bostian (https://dev.to/emmabostian)

  • Technical writer & DevRel practitioner
  • Dev.to profile & community contributions

Newsletters & Blogs

• DevRel Weekly (https://devrelweekly.com/)

  • Curated articles, job postings, and events
  • Focuses on industry trends and practical advice

• DevRel Relations (https://developerrelations.com/)

  • Community-curated newsletter & blog
  • DevRel news, insights, job board

Paid Course Platforms

Structured Learning

• Udemy

  • "Technical Writing for Software Engineers" / "Public Speaking for Developers"
  • "YouTube Content Creation for Technical Audiences"
  • Typical cost: USD $15–$50 per course
  • URL: https://www.udemy.com/

• Coursera

  • "Effective Communication for Engineers" (multiple universities)
  • "Public Speaking" specializations
  • Cost: USD $30–$50/month (audit), USD $200+ (certificate)
  • URL: https://www.coursera.org/

• LinkedIn Learning

  • "Developer Marketing & Relations" courses
  • "Technical Content Creation" & "Communication for Technical Professionals"
  • Cost: USD $30–$40/month (individual), included with LinkedIn Premium
  • URL: https://www.linkedin.com/learning/

• Maven Analytics Cohort Courses

  • DevRel-specific bootcamps (community-focused, live cohorts)
  • Typical cost: USD $500–$2,000 (depends on cohort length)
  • URL: https://maven.com/

Workshops & Conferences

• Speaking.io / Chiu-Ki Chan Workshops (https://speaking.io/)

  • Conference speaking training (CFP advice, talk structure, delivery)
  • Cost: USD $500–$1,500 per workshop
  • URL: https://speaking.io/

• Notist Conference Workshop Series (https://noti.st/)

  • Speaker training & community sharing
  • Free + paid workshop options
  • URL: https://noti.st/

• DevRelCon Workshops (https://devrelcollective.fun/)

  • Annual multi-day conference with live training tracks
  • Cost: USD $200–$500 (full conference)

Books

Recommended reading order for new DevRel practitioners:

1. The Business Value of Developer Relations (Thengvall) — strategic foundation
2. Developer Relations (Lewko & Parton) — operational how-to
3. Made to Stick (Heath brothers) — messaging and communication
4. Talking to Humans (Constable & Rimalovski) — feedback synthesis and research

Typical Job Titles

Developer Advocate, Developer Evangelist, DevRel Engineer, Developer Relations Engineer, Community Manager, Technical Advocate, Developer Content Engineer, Developer Experience (DX) Engineer, Technical Marketing Engineer, Head of Developer Relations, DevRel Manager, Director of Developer Relations, VP Developer Relations, Chief Developer Advocate, Open Source Advocate, Developer Success Engineer

Common Hard & Soft Skills

Hard Skills

• Technical writing (blog posts, tutorials, API documentation)
• Public speaking & conference talk delivery
• Live coding & demo development
• Video creation (YouTube screencast, webinars, live streaming)
• GitHub / open-source repository management
• API testing & prototyping
• Code sample & example app development
• Conference CFP (Call For Papers) submission & approval navigation
• Metrics & analytics literacy (SQL, dashboards, NPS, MQL attribution, churn analysis)
• SDK / library design feedback
• DevEx / API ergonomics evaluation

Soft Skills

• Empathy & active listening (understanding developer pain points)
• Storytelling & narrative building
• Community moderation & conflict resolution
• Transparent communication (saying "no" to roadmap requests with supporting rationale)
• Cross-functional collaboration (product, engineering, marketing, sales alignment)
• Networking & relationship building (local meetups, conferences, online communities)
• Feedback synthesis (distilling 100s of requests into 3-5 actionable insights)
• Emotional intelligence (recognizing and managing community tensions)
• Time management & boundary-setting (preventing 24/7 community support burnout)

Salary Data by Level & Region

United States (USD)

Source: Glassdoor (2025-2026), Levels.fyi DevRel salary data, PayScale

High-paying companies: Google Cloud, Stripe, AWS, Vercel, Twilio, Auth0, Dremio, Yugabyte, GitHub
Sources:

• Glassdoor DevRel Salary Data
• Levels.fyi DevRel Compensation

United Kingdom (GBP)

Estimated range (based on USD equivalents + regional cost-of-living adjustment):

• Junior: GBP 70K–95K
• Mid-level: GBP 95K–135K
• Senior: GBP 120K–170K
• VP: GBP 160K–250K+

Sources: Glassdoor UK, Levels.fyi (limited UK DevRel data)

European Union (EUR)

Estimated range (Frankfurt/Berlin/Amsterdam tech hubs):

• Junior: EUR 65K–90K
• Mid-level: EUR 90K–130K
• Senior: EUR 110K–160K
• VP: EUR 150K–240K+

Sources: Glassdoor EU, LinkedIn Salary (country-specific), local recruitment agencies

South Africa (ZAR)

2026 market data:

Market context:

• Limited local DevRel roles (mostly multinational offices: Google ZA, Amazon ZA, Microsoft ZA)
• Remote work with US/UK companies is the primary path for SA-based professionals
• Many roles are contractor-based (1099 equivalent), paid in USD with ZA cost-of-living adjustments
• OSS + portfolio visibility is critical for competing in global job market

Sources:

• Glassdoor ZA (limited data)
• PayScale ZA: https://www.payscale.com/
• Pnet (SA recruitment): https://www.pnet.co.za/
• Michael Page ZA: https://www.michaelpage.co.za/
• CareerJunction ZA: https://www.careerjunction.co.za/

Document prepared: April 2026
Last verified: April 2026
Next review: Q4 2026 (salary data refresh recommended)