Developer Advocacy Fundamentals covers the landscape of Developer Relations (DevRel), the discipline API-first and platform companies use to build trust with the external developers who decide whether to adopt their product. It exists because engineers evaluate documentation and code at their own pace, not a sales deck, so companies whose growth depends on developer adoption need people who serve developers first and let goodwill, usage, and feedback follow from that. The catch is that "DevRel" is not one job: a single posting often really means one of three very different disciplines, and picking the wrong one is the most common way newcomers end up disillusioned within a year. Because the field has no standardized job ladder, titles, reporting lines, and even survival through a budget cut vary sharply company to company, so a working mental map of the landscape matters more here than in most careers.
What This Cheat Sheet Covers
This topic spans 10 focused tables and 69 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: The Three Jobs Hiding Inside One "DevRel" Title
A single "Developer Relations" job posting can mean several genuinely different day-to-day jobs, and most of the confusion newcomers feel comes from not knowing which one they are applying for. Match the job to the skillset and expectations before committing to a track.
| Role | Example | Description |
|---|---|---|
Publishes a working sample integration, then runs office hours answering the questions it generates | The externally-facing bridge between the company and developers; writes sample code, runs community office hours, and turns recurring developer pain into product proposals. | |
Ships an OpenAPI spec update and a matching SDK code sample in the same pull request | The engineering-flavored seat on the team (also called a DX Engineer); ships SDKs, CLI tools, and starter kits, and owns the path from "landed on the docs" to a first successful API call. | |
Builds the dashboard that turns a quarter of conference talks and Discord threads into a budget defense for the CFO | Owns strategy, headcount, and budget for the function (also called DevRel Manager or VP of Developer Relations, depending on company size); hires across the specialized roles and reports program value upward. | |
Delivers the same "why this architecture works" talk at five regional conferences in a quarter | The outbound, brand-facing edge of DevRel; mostly conference talks, meetups, and high-reach content rather than inbound support, and does not always require production-level engineering skill. |