Developer Advocate

It looks like the dream job from outside: code a little, write a little, speak at conferences, get paid like an engineer. The reality of developer advocacy is stranger and harder — a job caught permanently between marketing and engineering, loved by developers and perpetually asked to justify its existence to finance. Both the dream and the precarity are real. Here's the honest picture.

Median pay (US)

~$140k / yr

Typical range

$100k–$190k+

Degree required?

No — public technical work is the resume

What the job actually is

Developer advocates help developers succeed with a product — and feed what they learn back into it. The output mix: tutorials and sample apps, docs contributions, conference talks and meetups, video and livestreams, community answering (Discord, Stack Overflow, GitHub issues), launch content for new features, and the inward half everyone forgets — synthesizing developer friction into reports product teams actually act on. The ratio varies enormously by company: some DevRel roles are 70% content creation, some are community management with code, some are near-product roles shaping the roadmap. The constant: you're the product's technical public face, and your credibility with developers is the entire asset — which is why good advocates guard their honesty fiercely, even about their own product's flaws.

Is it actually you?

You'll probably love it if

Teaching is the part of technical work you'd do for free
You already write, speak, stream, or answer questions publicly — unprompted
Breadth over depth suits you: many technologies, shallow-to-medium, constantly refreshed
Public visibility energizes you (or at least doesn't drain you)
You can hold two loyalties honestly — the company's and the community's

Maybe not, if

Deep-focus building is what you love; DevRel fragments your weeks into pieces
Being measured by fuzzy metrics (reach? sentiment? signups?) would stress you
Public criticism — of your talks, your posts, your product — lands hard on you
Travel and event energy costs more than it gives you
You need job security above all: DevRel budgets are cyclical and cut first

The real day-to-day (no hype)

The layoff cycle is this career's defining risk — plan for it structurally. DevRel sits in the budget gray zone between marketing and engineering, and in downturns it gets cut disproportionately — the field has been through brutal waves. The hedge: keep your engineering skills interview-fresh, keep your public work portable (your audience follows YOU), and favor companies where DevRel reports into product or engineering with clear metrics, not into marketing as vibes.
The job is a portfolio career wearing a salary. Everything you produce — talks, tutorials, open-source, audience — compounds personally and travels with you between employers. Advocates with strong public bodies of work interview better than almost anyone in tech, exit into product/engineering/founding roles smoothly, and can absorb a layoff better than peers. Treat the public work as your pension, not just your output.
Measurement is unsolved and you'll live inside that tension. Does DevRel drive signups? Retention? Brand? Every company answers differently and many answer badly — 'we'll know it when we see it' becomes 'we cut what we can't measure.' The advocates who survive learn to attach themselves to one or two metrics leadership already cares about (SDK adoption, time-to-first-success, support deflection) and narrate their impact in those terms relentlessly.
AI changed the content game — authenticity is the remaining moat. Generic 'getting started' tutorials are now instantly generatable, which devalued exactly the content junior DevRel used to cut teeth on. What holds value: opinionated depth, live debugging, honest comparisons, real-time community trust, and being a named human developers actually believe. The role is consolidating toward judgment and authenticity — write the thing only someone who's really used it could write.

How people break in — or switch in

DevRel hires almost exclusively on visible public work — the job IS public technical communication, so the application is your existing trail: blog posts explaining real problems, conference or meetup talks (local counts), open-source contributions, YouTube/streams, answers that helped people. Engineers: start creating around whatever you already build; six months of consistent output is a legitimate DevRel resume. Non-traditional entrants (teachers, bootcamp grads who document loudly): the teaching-plus-code combination is precisely the skill, and several strong advocates came exactly that way. Target products you genuinely use — faked enthusiasm reads instantly in this field. And in interviews, ask THEM the measurement question ('how does DevRel prove value here?'); the answer quality predicts your job security.

Engineers: you don't apply for DevRel, you accumulate into it — the public work has to exist first. The good news: six months of consistent, genuinely useful content about tech you already know is enough trail, and you can build it without quitting anything.

Your application, already half-written

Here's a question every Developer Advocate application asks, answered the way pirch would — in a real voice, grounded in real experience:

“How do you balance advocating for the company with advocating for developers?”

I treat my credibility with developers as the company's asset — which means I'm honest even when it's uncomfortable, because the alternative destroys the only thing that makes DevRel work. Concrete example: our SDK had a genuinely painful auth flow, and community threads were full of people hitting it. Instead of posting workaround content that papered over it, I did three things: published an honest guide that named the pain and gave the cleanest path through it, built the internal case for fixing it — I compiled 40+ community complaints, timed the flow myself on camera, and presented product with a friction report they couldn't unsee — and told the community, publicly, that I'd escalated it. The fix shipped two quarters later and the announcement thread was full of 'they actually listened.' That cycle — honest externally, forceful internally, credit shared — is the whole job to me. Developers can smell a mouthpiece instantly. The advocate who'll say 'this part is rough, here's the workaround, and I'm pushing to fix it' is the one they believe when he says the new feature is great.

pirch's co-pilot writes answers like this for your background and the exact job — try it free →

pirch finds the DevRel roles that are actually you

Developer advocate, DevRel engineer, community engineer, developer educator — the titles blur and the role behind each posting varies wildly. Tell pirch who you are and it hunts down real, still-open roles that match the mix you want, with a tailored cover letter already written. No spray-and-pray. No dead links.

start your free hunt

first hunt free · we never auto-apply · you stay in control

Common questions

What does a developer advocate actually do?

They help developers succeed with a product — tutorials, talks, sample code, community support — and channel developer friction back into the product roadmap. The mix of content, community, and product work varies significantly between companies, so read each posting's actual ratio.

How much do developer advocates make?

Roughly $100k–$190k+ with a median around $140k — engineer-adjacent pay, since most advocates are engineers who moved over. Senior advocates and DevRel leads at major platform companies exceed the range.

How do I get into developer relations?

Build the public trail first: blog posts, talks (local meetups count), open-source contributions, video — six months of consistent, genuinely useful output around technology you already know. DevRel hires on visible work; the portfolio IS the application.

Is developer advocacy a stable career?

The work is durable; the budget line isn't. DevRel gets cut disproportionately in downturns, so the smart structure is: keep engineering skills fresh, build a portable public audience, and favor employers where DevRel has clear metrics and reports into product or engineering rather than marketing.