Developer Relations (DevRel) as a Career: $120-200K to Talk About Code

A friend of mine quit a $160K senior developer job at a mid-size fintech company to become a Developer Advocate at a startup nobody had heard of. Everyone thought he was crazy. His parents didn't understand the job title. His engineering friends joked that he was "giving up real work to become a tech influencer." His recruiter told him he was taking a career risk. Two years later, he makes more money than he did as a senior dev, works fewer hours, has 50,000 Twitter followers, gets invited to speak at conferences on three continents, and — here's the part that really annoys his old coworkers — genuinely loves his job. He told me recently: "I write code, I write about code, I talk about code, and I help other developers solve problems. It's everything I liked about engineering minus the parts I hated."

Developer Relations — DevRel — is one of those careers that most engineers know exists but fundamentally misunderstand. They think it's "tech marketing" or "being a YouTube personality" or "the person who gives out stickers at conferences." And while those things are sometimes part of the job, the actual role is far more technical, more strategic, and more financially rewarding than most engineers realize. It's also one of the fastest-growing career paths in tech, with companies from early-stage startups to trillion-dollar enterprises building dedicated DevRel teams.

This article is a deep dive into what DevRel actually is, who thrives in it, what it pays, how to break in, and whether the stigma around it ("it's not a real engineering job") has any merit. Spoiler: it doesn't.

The Numbers First

DevRel compensation is surprisingly strong — often matching or exceeding equivalent-level engineering roles, which shocks people who assume it's a "softer" career track.

According to Glassdoor salary data, the average Developer Advocate salary in the US is approximately $124,000 in base compensation. But that average masks a wide range:

• Junior Developer Advocate (0-2 years in DevRel): $85,000 - $120,000
• Mid-level Developer Advocate (2-5 years): $120,000 - $165,000
• Senior Developer Advocate (5+ years): $150,000 - $200,000
• DevRel Manager / Head of DevRel: $149,000 - $215,000 according to ZipRecruiter data
• VP of Developer Relations / Community: $180,000 - $280,000+

When you include total compensation (base + equity + bonuses + conference travel stipends), top DevRel professionals at companies like Stripe, Vercel, and Cloudflare earn $200,000-$350,000 in total comp. According to VelvetJobs salary analysis, the top 10% of Developer Relations professionals in the US earn above $215,000 median in total compensation, placing them firmly in the top tier of tech salaries.

For emerging markets, DevRel salaries follow a different curve. Most DevRel roles are remote-friendly (the job inherently involves engaging with a global developer community), which means developers in Azerbaijan, Eastern Europe, Latin America, and Southeast Asia can access US-based DevRel salaries or near-equivalents:

The remote-friendliness of DevRel is one of its most attractive features. According to Pluralsight's overview of the DevRel field, over 70% of DevRel roles offer remote or hybrid work arrangements, compared to roughly 40-50% for general engineering roles. The nature of the work — creating content, engaging online communities, writing documentation, building sample applications — translates naturally to distributed work.

The job market for DevRel is growing. Glassdoor shows a 35-45% increase in DevRel job postings over the past three years, driven by the explosion of developer-focused products (APIs, SDKs, cloud platforms, AI tools) and the recognition that developer adoption is a critical growth channel for technical products.

What DevRel Actually Is (And What It Isn't)

The biggest misconception about DevRel is that it's "marketing for developers." It's not. Or rather, it's not just marketing. DevRel sits at the intersection of engineering, product, marketing, and community — and the best DevRel professionals are genuinely skilled in all four areas.

Here's what DevRel actually involves:

Developer Advocacy: This is the most visible part. Developer Advocates create technical content — blog posts, tutorials, videos, conference talks, livestreams — that helps developers understand and use the company's products. But unlike marketing content, developer advocacy content must be genuinely useful. Developers have finely tuned BS detectors. If your tutorial is thinly disguised advertising, they'll bounce. The best DevRel content teaches developers something valuable, and the company's product happens to be relevant. This is a fundamentally different approach from traditional marketing.

Documentation: Many DevRel teams own or significantly contribute to product documentation. Good documentation is the single most important factor in developer adoption — Pluralsight research indicates that poor documentation is the #1 reason developers abandon a tool or platform. Writing clear, accurate, comprehensive documentation is a deeply technical skill that requires both engineering knowledge and communication ability.

Community Building: DevRel professionals build and nurture developer communities — Discord servers, forums, user groups, meetups, hackathons. This involves moderation, event planning, feedback collection, and creating spaces where developers can help each other. A strong community reduces support burden, generates user-created content, and creates organic advocacy.

Product Feedback Loop: Perhaps the most underappreciated aspect of DevRel: being the voice of the developer inside the company. DevRel professionals talk to developers every day — through support channels, community forums, conference conversations, and social media. They understand developer pain points, feature requests, and frustrations better than anyone else in the organization. This feedback, channeled to the product and engineering teams, directly influences product roadmaps.

SDK and Sample Code Development: Many DevRel professionals write production-quality code: SDKs, client libraries, sample applications, code examples, and integration guides. This code is often the first thing a developer sees when evaluating a product. A well-written, well-documented SDK can be the difference between a developer adopting your platform or choosing a competitor.

Conference Talks and Events: Speaking at conferences, hosting workshops, running hackathons, and representing the company at developer events. This is the "public face" of DevRel and what most people think the whole job is. In reality, it's typically 10-15% of the work, but it's the most visible 10-15%.

A Day in the Life: How DevRel Actually Breaks Down

The daily work of a Developer Advocate varies by company, but here's a representative breakdown based on conversations with DevRel professionals at various companies and data from Pluralsight's DevRel career guide:

A few things to note about this breakdown:

First, the code-to-communication ratio is roughly 10-40% code, 60-90% communication, depending on the company and role. If you're a developer who hates writing, presenting, and talking to people, DevRel is not for you. If you're a developer who loves explaining things and gets energy from helping others, it might be perfect.

Second, the travel varies enormously. Some DevRel roles involve 30-40% travel (multiple conferences per month). Others are almost entirely remote content creation with 2-3 conferences per year. Know what you're signing up for. The "digital nomad DevRel who speaks at conferences worldwide" lifestyle is real but demanding. The "content-focused DevRel who writes from home" lifestyle is equally valid and increasingly common.

Third, the mix shifts over your career. Junior DevRel professionals spend more time on content creation and community engagement. Senior DevRel professionals spend more time on strategy, product influence, and team leadership. At the Head of DevRel level, you're setting strategy, managing a team, and working with executive leadership — it becomes a leadership role with a technical foundation.

Who Thrives in DevRel (And Who Doesn't)

DevRel is not for every engineer, and that's fine. The people who thrive in it tend to share specific characteristics:

You love explaining things. Not just answering questions — actively enjoying the process of taking a complex concept and making it clear. If you're the person on your team who writes the best documentation, who volunteers to onboard new engineers, who explains architectural decisions in pull request descriptions — you have the DevRel instinct.

You're a generalist at heart. DevRel requires broad technical knowledge rather than deep specialization. You need to understand frontend, backend, databases, APIs, deployment, authentication, and the developer tool landscape well enough to write and speak about them credibly. You don't need to be the world's best React developer — you need to understand React well enough to write a tutorial that helps someone build something real.

You're empathetic toward beginners. A lot of senior engineers have a hard time remembering what it was like to not understand things. DevRel requires the ability to meet developers where they are — whether that's a complete beginner or a senior architect — and communicate at their level. The "curse of knowledge" is the enemy of good DevRel.

You can write well. Technical writing is a core DevRel skill. Not academic writing — clear, conversational, practical writing. If you can explain a complex technical concept in a blog post that a mid-level developer can follow, you have a marketable DevRel skill.

You're comfortable with ambiguity. Unlike engineering roles where success is measurable (the feature works, the test passes, the system stays up), DevRel success is harder to quantify. Did that blog post drive adoption? Did that conference talk generate leads? How do you measure the value of a healthy developer community? DevRel professionals need to be comfortable operating in a space where impact is real but metrics are imperfect.

Who DOESN'T thrive: Engineers who find deep satisfaction in solving hard technical problems for hours in focused solitude. Engineers who dislike writing, presenting, or being a "public figure" in any capacity. Engineers who need clear, quantitative metrics to feel their work is valued. These are all valid preferences — they just point toward individual contributor engineering roles rather than DevRel.

The Introvert Path: You Don't Have to Be a Conference Star

One of the biggest barriers to DevRel is the perception that you need to be an extroverted, charismatic stage presence. This is wrong. DevRel has multiple specialization paths, and several of them are ideal for introverts:

Documentation-focused DevRel. Some DevRel professionals specialize in documentation: API references, getting-started guides, architecture documentation, migration guides. This is deeply technical, largely solitary work that has enormous impact. Companies like Stripe and Twilio have built their reputations partly on exceptional documentation — written by DevRel professionals, not marketing teams.

Written content DevRel. Blog posts, tutorials, technical guides, newsletters. You can build a significant DevRel career entirely through written content, without ever speaking at a conference. Many of the most influential developer educators work primarily through writing — think of the people behind popular technical blogs, newsletters with tens of thousands of subscribers, and detailed tutorial series.

Open-source DevRel. Some DevRel roles are focused on building and maintaining open-source projects, SDKs, and developer tools. This involves writing code, reviewing community contributions, managing GitHub issues, and collaborating with external developers — all of which can be done asynchronously and in writing.

Video content (pre-recorded). If speaking in front of a live audience terrifies you but you're comfortable recording screencasts, there's a massive demand for video tutorials. Pre-recorded content lets you edit, reshoot, and polish — no live performance anxiety required.

The key insight is that DevRel is fundamentally about helping developers succeed with your product. There are many ways to do that, and not all of them require extroversion or public speaking.

Career Paths: Where DevRel Goes

One of the common concerns about DevRel is "where does it lead?" Engineering has a clear ladder: junior → mid → senior → staff → principal. DevRel's career trajectory is less standardized, but there are several well-established paths:

Path 1: DevRel Leadership

Developer Advocate → Senior Advocate → DevRel Lead → Head of Developer Relations → VP of Developer Relations. This is the most direct path. You move from individual contribution to team management to department leadership. At the VP level, you're setting strategy for how the company engages with its entire developer ecosystem, managing budgets in the millions, and reporting to the C-suite. Compensation at the VP level is $200,000-$350,000+ at well-funded tech companies.

Path 2: Community → Marketing Leadership

Developer Advocate → Community Lead → Head of Community → VP Community → CMO. Some DevRel professionals pivot into broader marketing leadership, bringing their developer-community expertise to the marketing organization. The CMO path is less common but not unheard of, especially at developer-focused companies where the marketing strategy is fundamentally community-driven.

Path 3: Back to Engineering (But Better)

Developer Advocate → return to Senior/Staff Engineer role. DevRel experience makes you a dramatically better engineer. You've developed communication skills, product thinking, empathy for users, and cross-functional collaboration experience. Engineers who return from DevRel often move into tech lead or engineering manager roles because they combine technical depth with the communication and leadership skills that DevRel develops.

Path 4: Independent / Creator

Developer Advocate → independent consultant, course creator, author, or content creator. The audience and reputation you build in DevRel can become the foundation for an independent career. DevRel professionals who build large followings sometimes leave to create courses, write books, or consult independently. This path is high-risk, high-reward — you lose the stability of a salary but gain complete autonomy.

Path 5: Product Management

Developer Advocate → Product Manager → Senior PM → Director of Product. The product feedback loop aspect of DevRel is excellent preparation for product management. You've spent years understanding developer needs, prioritizing feature requests, and translating between engineering and business stakeholders. The transition to PM is natural for DevRel professionals who are more interested in product strategy than content creation.

Companies Hiring DevRel (And What They Look For)

The DevRel job market is concentrated in developer-focused companies — those whose customers are developers or whose products require developer adoption. Here's a breakdown by company type:

Developer Tools and Platforms: Stripe, Vercel, Supabase, Cloudflare, MongoDB, Twilio, Postman, Hashicorp, Datadog, PlanetScale. These companies live or die by developer adoption. Their DevRel teams are large, well-funded, and strategic.

Cloud Providers: AWS, Google Cloud, Microsoft Azure, DigitalOcean. Cloud providers have some of the largest DevRel organizations in the industry — AWS alone has hundreds of developer advocates. These roles tend to be specialized (e.g., "Developer Advocate, Machine Learning" or "Developer Advocate, Serverless").

AI/ML Companies: OpenAI, Anthropic, Hugging Face, Cohere, Stability AI. The AI boom has created massive demand for DevRel professionals who can help developers integrate AI capabilities into their applications. This is currently one of the hottest DevRel sub-markets.

Open-Source Companies: GitLab, Elastic, Grafana Labs, Temporal, Airbyte. Open-source companies rely on community adoption as their primary growth channel. DevRel is existentially important to their business model.

What they all look for:

• Demonstrated technical ability: You don't need to be a 10x engineer, but you need to be able to write production-quality code, understand architectural patterns, and discuss technical concepts credibly. Most DevRel job postings require 3-5+ years of engineering experience.
• A public body of work: Blog posts, conference talks, video tutorials, open-source contributions, a technical Twitter/LinkedIn presence. Companies want evidence that you can create technical content and engage a developer audience. VelvetJobs notes that a strong public portfolio is the single most important differentiator in DevRel hiring.
• Communication skills: Clear writing, articulate speaking, ability to explain complex concepts simply. This is evaluated through your existing content, take-home assignments (write a tutorial, give a sample presentation), and interview conversations.
• Empathy and community instincts: Can you meet developers where they are? Can you handle negative feedback gracefully? Can you build genuine relationships in a community, not just transactional interactions?

Breaking Into DevRel: The Practical Playbook

If DevRel interests you, here's how to build credibility and get your first role — even if you have zero DevRel experience today:

Step 1: Start writing. Today. Create a technical blog (dev.to, Hashnode, personal site, Medium) and start publishing. Write about what you're learning, problems you've solved, technologies you've evaluated. Aim for one post per week. Quality matters more than frequency, but consistency matters too. After 3-6 months of regular writing, you'll have a portfolio of technical content that most DevRel applicants can't match.

Step 2: Engage in developer communities. Join Discord servers, forums, and GitHub discussions for tools you use. Answer questions. Help people debug problems. Be genuinely helpful, not self-promotional. Community engagement is a core DevRel skill, and doing it for free in public builds both skill and reputation.

Step 3: Give a talk. Start small. Your company's internal tech talk. A local meetup (virtual or in-person). A Lightning Talk at a conference (5-10 minutes, much less intimidating than a full talk). Record it and share it. Even one recorded talk separates you from 90% of DevRel applicants who have zero speaking experience.

Step 4: Contribute to open source. Pick a developer tool you use and contribute — documentation improvements, sample applications, bug fixes. This demonstrates that you can work in public, collaborate with other developers, and contribute to products you don't own. These are exactly the skills DevRel requires.

Step 5: Apply strategically. When you have 6-12 months of public content and community engagement, start applying to DevRel roles. Target companies whose products you genuinely use and believe in — your authentic enthusiasm will come through in interviews. Tailor your application to show specific examples of your content and community work.

The timeline from "interested in DevRel" to "hired for a DevRel role" is typically 6-18 months if you're building your public presence intentionally. That might seem long, but it's comparable to the time most engineers spend preparing for senior engineering interviews.

"It's Not a Real Engineering Job" — Debunking the Stigma

Let's address the elephant in the room. In many engineering circles, DevRel carries a stigma. "It's marketing, not engineering." "DevRel people couldn't hack it as real developers." "It's a cushy job where you just give conference talks and post on Twitter." I've heard all of these. Let me address them directly.

"DevRel people aren't real engineers." Look at the backgrounds of DevRel professionals at top companies. Kelsey Hightower (Google Cloud) was a systems engineer. Cassidy Williams (various, now Contenda) was a software engineer at Venmo, L4, and CodePen. Swyx (Airbyte, Temporal) was an engineer at AWS and Netlify. These are not people who "couldn't hack it" in engineering. They're people who discovered that their unique combination of technical skill and communication ability was more valuable — and more fulfilling — in DevRel than in pure engineering roles.

"DevRel is just marketing." Marketing creates demand for products. DevRel helps developers succeed with products. There's overlap, but the objectives are different. A marketer asks "how do I get more people to buy?" A DevRel professional asks "how do I help developers build things successfully with our product?" The content is different (technical depth vs. feature highlights), the audience is different (practitioners vs. decision-makers), and the metrics are different (adoption and retention vs. leads and conversions). Calling DevRel "marketing" is like calling a doctor a "salesperson for pharmaceutical companies" because they prescribe medicine.

"It's a cushy job." DevRel professionals regularly work across multiple time zones, travel 20-40% of the year, create content under public scrutiny, manage community conflicts, and balance competing priorities from engineering, product, and marketing leadership — all while maintaining their technical skills and producing high-quality content. The burnout rate in DevRel is notably high. According to Pluralsight's research, DevRel professionals report burnout at rates comparable to or higher than engineering roles, driven by the always-on nature of community management and the difficulty of setting boundaries when your public presence IS your job.

"It's a dead-end career." The career paths section above directly refutes this. DevRel leads to leadership roles, product management, engineering management, independent consulting, and executive positions. The combination of technical skill, communication ability, product thinking, and community understanding that DevRel develops is extraordinarily valuable and transferable.

The real source of the stigma, if I'm being honest, is insecurity. Some engineers define their identity through the difficulty and exclusivity of their work. The idea that someone can earn comparable money by "just" writing blog posts and giving talks feels threatening to that identity. But this reveals more about the person holding the stigma than about DevRel itself.

The Hard Parts Nobody Mentions

In the interest of balance, let me be honest about the parts of DevRel that are genuinely difficult:

Measuring impact is hard. Engineering output is measurable: features shipped, bugs fixed, system uptime. DevRel impact is fuzzy: how many developers did your tutorial help? How much did that conference talk contribute to adoption? How do you measure the value of a healthy community? This ambiguity can be stressful, especially during budget reviews when DevRel teams are asked to justify their existence with numbers that don't capture their full impact.

Staying technically current is a constant effort. Unlike engineers who deepen their expertise in a specific area, DevRel professionals need to maintain broad technical knowledge across a rapidly changing landscape. You need to understand the latest frameworks, tools, and patterns well enough to write and speak about them credibly. This requires deliberate, ongoing investment in learning — and it can be hard to find time for that learning when your calendar is full of content creation and community engagement.

Being a public figure has costs. When your work is public — blog posts, conference talks, social media — you're exposed to public criticism, misinterpretation, and occasionally outright hostility. Not every developer community is healthy. Dealing with toxic community members, handling controversial topics, and maintaining professionalism under public scrutiny is emotionally demanding.

Organizational positioning is often unclear. DevRel teams report to engineering at some companies, marketing at others, product at others, and directly to the CEO at still others. This organizational ambiguity can create confusion about priorities, metrics, and career ladders. Some companies treat DevRel as a cost center to be cut during downturns; others treat it as a strategic investment. Your experience in DevRel can vary dramatically based on organizational positioning.

The travel can be exhausting. If your role involves conference speaking, you might be on the road 30-40% of the time. That sounds glamorous until you've spent your fourth consecutive weekend in a hotel room preparing a talk instead of being home. DevRel travel is work travel — long flights, time zone disruptions, energy-intensive social interactions — not vacation.

What I Actually Think

Here's my honest take on DevRel as a career:

DevRel is the best-kept secret in tech careers. It pays well, offers incredible flexibility, builds a public reputation that compounds over time, and provides a unique combination of technical and interpersonal challenges. For the right person — a developer who loves explaining things, building community, and working at the intersection of technology and communication — it's an ideal career.

It's not a shortcut or an easy path. Good DevRel is genuinely hard. You need to be technically credible (which requires real engineering experience), an excellent communicator (which is a separate skill that takes years to develop), and resilient enough to handle public visibility and ambiguous metrics. The salary is justified by the breadth and difficulty of the skill set required.

The timing is excellent. Developer-focused products are proliferating — every AI startup, cloud tool, API provider, and open-source project needs developer adoption. The supply of people who can both write code and communicate about code is limited. Demand exceeds supply, which drives compensation up and makes it a good time to break into the field.

Start building your public presence now, regardless of whether you pursue DevRel. Writing technical blog posts, giving talks, contributing to open source, and engaging in developer communities makes you a better engineer even if you never take a DevRel job. These skills are increasingly valued in senior engineering roles too — staff engineers and engineering managers need communication and community skills.

Don't let the stigma stop you. If DevRel calls to you — if you find yourself gravitating toward documentation, mentoring, public writing, and community building — pursue it. The engineers who dismiss DevRel as "not real work" are optimizing for a narrow definition of engineering that doesn't match the reality of how software products succeed. Products succeed when developers can use them effectively. DevRel makes that happen. It's real work, it's important work, and it's well-compensated work.

Decision Framework: Is DevRel Right for You?

Score yourself on these dimensions. Be honest.

1. Do you enjoy explaining technical concepts to others?

• Love it — I'd do it for free (and probably already do): +3
• It's fine, part of the job: +1
• I find it draining and prefer to just code: -2

2. How do you feel about writing?

• I write regularly and enjoy it: +3
• I can write when I need to but don't seek it out: +1
• I actively dislike writing: -3

3. How do you feel about public visibility?

• I'm comfortable being a public figure in my field: +2
• I'm nervous about it but willing to grow: +1
• I strongly prefer working behind the scenes: -2

4. How important is deep technical specialization to you?

• I prefer being a generalist who knows many things: +2
• I like both breadth and depth: +1
• I want to be the world's deepest expert in one area: -2

5. How do you handle ambiguous success metrics?

• I'm comfortable with qualitative impact: +2
• I can adapt but prefer clarity: 0
• I need clear, quantitative metrics or I feel lost: -2

6. Do you have 3+ years of engineering experience?

• Yes, and I'm looking for something different: +2
• Yes, but I still love pure engineering: 0
• No — I'm early in my career: -1 (build engineering experience first)

Score interpretation:

• 10-15: DevRel is likely an excellent fit. Start building your public presence immediately.
• 5-9: DevRel could work for you, especially in a docs-focused or content-focused role. Experiment with writing and community engagement to test the waters.
• 0-4: DevRel might not be the best fit right now. Consider whether you'd enjoy a hybrid role (tech lead, engineering manager) that incorporates some DevRel skills.
• Below 0: You probably thrive more in a deep individual contributor engineering role. That's a great career too — DevRel isn't for everyone, and it doesn't need to be.

How to Get Started This Week

If DevRel interests you after reading this, here are five concrete things you can do in the next seven days:

1. Write one technical blog post. Pick a problem you solved recently at work. Write 800-1,200 words about the problem, your approach, and the solution. Publish it on dev.to, Hashnode, or your personal blog. Don't overthink it — your first post doesn't need to be perfect.
2. Answer 5 questions in a developer community. Find a Discord server, Stack Overflow tag, or GitHub Discussions board for a technology you know well. Answer 5 questions thoughtfully and thoroughly. Practice the skill of explaining technical concepts to strangers.
3. Follow 10 DevRel professionals on Twitter/LinkedIn. See what their days look like, what content they create, how they engage with communities. Get a feel for the role through observation.
4. Read 3 DevRel job descriptions. Search for "Developer Advocate" or "Developer Relations" on LinkedIn or Glassdoor. Read the requirements. Note which skills you already have and which you'd need to develop.
5. Record a 5-minute screencast. Pick a tool or technique you know well. Record yourself demonstrating it with screen recording and narration. Don't publish it if you don't want to — just experience the process of explaining something technical out loud. It's a different skill than writing, and you'll immediately know if you enjoy it.

Sources

• Glassdoor — Developer Advocate Salary Data
• ZipRecruiter — Developer Relations Manager Salary
• Pluralsight — What Is Developer Relations?
• VelvetJobs — Developer Relations Salary Analysis
• Stripe Careers — Developer Advocacy Roles
• Vercel Careers
• Supabase Careers
• Cloudflare Careers
• MongoDB Careers

Whether you're building developer tools or building your career in DevRel, BirJob.com aggregates opportunities from 90+ sources across Azerbaijan and the tech world. Find developer, DevRel, and community roles at birjob.com.

You might also like

• AI Engineer vs ML Engineer: What Actually Changed and Why It Matters
• The Analytics Role Confusion: Business Analyst, Data Analyst, BI Analyst — What's the Actual Difference?
• DevOps vs SRE vs Platform Engineer: The Infrastructure Title Mess, Explained
• Product Manager vs Project Manager vs Program Manager: A Guide for People Who Can't Tell Them Apart