Sign Up
Blog

Developer Advocacy: The Technical Evangelist Path

Developer Advocacy: The Technical Evangelist Path

You love technology and you love teaching. You get energy from helping other developers succeed. You can explain complex concepts clearly and enjoy being part of developer communities. Developer advocacy might be your calling.

Developer advocates (also called developer evangelists, developer relations engineers, or DevRel professionals) represent technology products to developer communities. They teach, create content, build community, and bring developer feedback back to product teams.

What Developer Advocates Do

Core Activities

Content creation:

  • Writing blog posts, tutorials, and documentation
  • Creating video content and courses
  • Building sample applications and demos
  • Developing talks and workshops

Community engagement:

  • Speaking at conferences and meetups
  • Participating in online communities (Discord, forums, social media)
  • Answering developer questions
  • Building relationships with developers

Product feedback:

  • Representing developer perspective internally
  • Reporting issues and feature requests
  • Testing products from developer perspective
  • Advising on developer experience

Developer enablement:

  • Helping developers succeed with products
  • Creating quickstarts and getting-started guides
  • Running hackathons and workshops
  • Supporting developer programs

Day-to-Day Variation

The role varies significantly:

  • Travel-heavy: Conference speakers, field advocacy
  • Content-focused: Primarily creating written/video content
  • Community-focused: Managing communities and programs
  • Technical-focused: Building samples, SDKs, tools

Why Developer Advocacy Appeals

The Positives

  • Helping developers: Direct impact on others’ success
  • Variety: Mix of creating, presenting, coding, and connecting
  • Visibility: Build personal brand and reputation
  • Community: Connect with developers worldwide
  • Learning: Constantly explore new technologies
  • Creativity: Express yourself through content and talks

The Trade-offs

  • Travel demands: Can be extensive (though remote advocacy exists)
  • Burnout risk: Always “on,” public visibility, content treadmill
  • Impact measurement: Value can be hard to quantify
  • Less coding: May write less production code
  • Job stability: DevRel sometimes cut during downturns

Skills for Developer Advocacy

Technical Skills

  • Broad technical knowledge: Ability to learn quickly
  • Coding ability: Write clear, educational code
  • Product expertise: Deep knowledge of your product
  • Developer empathy: Understanding developer workflows

Communication Skills

  • Writing: Clear, engaging technical content
  • Public speaking: Presenting to groups of all sizes
  • Teaching: Explaining concepts at appropriate levels
  • Listening: Understanding developer needs

Community Skills

  • Relationship building: Connecting with developers authentically
  • Social media: Engaging effectively online
  • Empathy: Understanding diverse perspectives
  • Patience: Answering the same questions repeatedly

Paths Into Developer Advocacy

From Software Engineering

Most common path:

  • Build public presence (blog, talks, open source)
  • Demonstrate communication skills
  • Volunteer to help with documentation, community
  • Transition to DevRel role

From Technical Writing

  • Writing skills already strong
  • Deepen coding abilities
  • Build speaking skills
  • Develop community presence

From Community/Support

  • Community skills established
  • Build technical depth
  • Develop content creation skills
  • Learn public speaking

Building Your Profile

Before applying to DevRel roles:

  • Start a technical blog
  • Give talks at local meetups
  • Create video content
  • Contribute to open source
  • Be active in relevant communities
  • Build Twitter/social media presence

Developer Advocacy Compensation

Compensation comparable to engineering:

  • Entry-level: $100,000-$140,000
  • Mid-level: $140,000-$180,000
  • Senior: $170,000-$230,000
  • Principal/Staff: $200,000-$280,000
  • Director+: $220,000-$350,000

Big tech typically pays more. Note that extensive travel can add unpaid time costs.

The Developer Advocacy Career Path

Individual Contributor Track

  1. Junior Advocate: Learning the role, creating content, speaking locally
  2. Developer Advocate: Full ownership of areas, speaking widely
  3. Senior Advocate: Thought leadership, strategic content, mentoring
  4. Staff/Principal: Industry recognition, program creation

Management Track

  1. DevRel Lead: Small team, player-coach
  2. Manager: Full team management
  3. Director: Multiple teams, strategy
  4. VP/Head of DevRel: Executive leadership

Adjacent Moves

  • Product Management: Developer-facing products
  • Engineering Management: Return to engineering with new skills
  • Marketing: Technical marketing roles
  • Founding/Consulting: Independent developer education

Women in Developer Advocacy

The Opportunity

  • Communication skills valued (often undervalued in pure engineering)
  • More visible women in DevRel than some technical roles
  • Community-focused culture often more welcoming
  • Growing field with opportunities

Considerations

  • Public visibility means public scrutiny (sometimes negative)
  • Conference culture varies in inclusivity
  • Travel demands can conflict with life responsibilities
  • Need to self-promote, which can feel uncomfortable

Building Visibility Safely

  • Start with smaller, welcoming communities
  • Build support network of allies
  • Know that criticism often isn’t personal
  • Set boundaries on public availability

Avoiding DevRel Burnout

Developer advocacy has high burnout risk:

Warning Signs

  • Dreading content creation or speaking
  • Exhaustion from constant travel
  • Feeling like you’re always “performing”
  • Resentment of community demands

Prevention

  • Set boundaries on travel and availability
  • Build sustainable content cadence
  • Take real vacations (offline)
  • Develop non-public technical work
  • Find community within DevRel

Is Developer Advocacy Right for You?

Good Fit If

  • You love teaching and helping others learn
  • You enjoy public speaking and writing
  • You’re energized by community interaction
  • You like variety in your work
  • You want visibility and personal brand

Think Carefully If

  • You want to focus deeply on building systems
  • Public visibility makes you uncomfortable
  • Travel would be unsustainable for your life
  • You need very stable roles (DevRel can be cut)
  • You prefer heads-down work

Getting Started

If developer advocacy interests you:

  1. Start creating: Write a blog post or record a video this month
  2. Speak locally: Give a talk at a meetup
  3. Build community: Engage actively in developer communities
  4. Learn from DevRel: Follow advocates, understand the role
  5. Apply: Look for junior or associate DevRel roles

Developer advocacy combines technical skills with teaching and community—if that mix excites you, it’s a rewarding career path.

Meet developer relations teams at WomenHack events.