The habits in this guide are constant; the priorities are not. Most wasted developer-marketing budget is a play from the wrong stage, executed well — a content calendar before product-market fit, a conference sponsorship before the quickstart works, a DevRel hire before there is anything to advocate. This section is the stage lens: what each stage should buy, who should be doing it, and what the numbers look like.

Three stages, three constraints

  • Pre-product-market-fit. Almost all of the return is in positioning and in talking to the twenty developers who might use the thing. The founder does the marketing, the docs are the product, and a content calendar is expensive procrastination. Buy nothing that scales.
  • Early traction. The constraint moves to the path from first visit to working integration: docs, activation, the website that routes people to them, and a pricing page with a number on it. The first hire happens here, and it should scale what is already working rather than start something new.
  • Scale. The work becomes distribution, category and the buyer beside the developer: channels chosen deliberately, launches run as a cadence, the enterprise door, paid as a craft rather than a tax, and a team with named owners for each.

The test for any spend is which constraint it relieves. A play that would be right two stages later is not “early”; it is a different plan’s line item.

The four jobs

A developer marketing function does four things, whatever the org chart calls them, and a small team covers all four with two people wearing hats.

  • Product marketing owns the positioning, the pricing page, the launch tiers and the buyer’s material. It is the spine: the one function that has to know both what the product does and what the buyer asks.
  • Developer relations owns advocacy, education and the feedback loop — community and DevRel — and its leverage is content and relationships that scale, not one-to-one support.
  • Content owns the tutorials, the explainers, the changelog and the newsletter: content that earns trust and the always-on cadence.
  • Growth owns the funnel numbers — activation, conversion, the docs instrumentation, the experiments — and reports on measurement’s terms rather than a lead-gen dashboard’s.

The first hire follows the motion

Which of the four to hire first is decided by the motion, not by which title is fashionable. Product-led: a growth marketer, because the constraint is activation and the job is instrumenting and shortening the path to value. Sales-assisted or enterprise-leaning: a developer advocate, because the constraint is technical credibility in rooms the founders cannot be in. Content-led or docs-led: a technical writer, because the constraint is the volume of accurate, runnable material. daily.dev’s 2026 hiring guide reaches the same three-way split (vendor content, its salary bands sourced to a third-party blog rather than a survey), and its one-line rule — the first DevRel hire “should be a builder, not a speaker” — is the same point from the other side. The guide’s own rule: the first hire should scale what is already working, not start from scratch. Hire a generalist before a specialist, and hire the specialist for the constraint you can name.

DevRel advocates are expensive and hard to hire — they need genuine technical credibility and the ability to teach and perform — and the role dies in two ways. The first is reporting into sales: a lead quota turns advocacy into capture, and the audience feels it immediately. Report DevRel to whoever values developer engagement most (the CMO, the CPO or the CTO, depending on the company), never to a pipeline number. The second is the support queue: an advocate who spends the week answering tickets is a support engineer with a conference budget. Protect the time, or do not make the hire.

What it costs

The numbers here are benchmarks a reader can check, not a budget. On the salary aggregators (Glassdoor and PayScale, mid-2026), US developer-advocate base pay averages about $135K–$140K with the middle half of reports spanning roughly $110K–$170K — a wide band, because the title covers a junior evangelist and a staff engineer alike. The industry survey runs higher and is skewed by senior and US respondents: the State of Developer Relations series (DevRel.Agency) put median total compensation at $180K in 2022, $200K in 2023 (median base $175K), then $193K in the 11th report (2024; median base $150K) — the latest edition, and the only one that has moved down. No 2025 wave has been published as of this review, so the freshest median is two years old. daily.dev’s benchmark for a one-to-three-person DevRel team is $400K–$700K in salaries plus $100K–$200K in tools and travel, and $1M–$2M a year for a four-to-eight-person team with events and sponsorships included (vendor figures, stated without a method). The recurring finding across the same surveys is the one that should shape the budget: proving impact with data and metrics is DevRel’s most-cited challenge — 60.7% of practitioners in the 2024 report, 67.3% the year before — so a programme funded without a measurement plan is a programme that gets cut in the first downturn.

Two rules of thumb hold across stages. Spend on the surfaces before the campaigns — a broken quickstart amplified is a larger sample of people learning that it is broken — and keep the paid line small enough that losing it entirely would not change the plan, because for this audience it usually should not.

What is deliberately not here

Agencies and consultants are out of scope: a vendor directory needs a re-verification desk and this publication has none. Per-platform playbooks date in weeks and live in the swipe file. Swag and booths are line items, not a topic. What this section owes the reader is the stage lens and the hiring order; the rest of the guide is the job description.