What is developer relations and how does DeveloperRelations.com explain it?
Developer relations (DevRel) is the work of connecting a company with the developers who use, build on, or might adopt its products. DeveloperRelations.com is a resource hub for that field: it collects talks, guides, podcasts, reports, case studies, and origin stories aimed at helping people understand and advance a DevRel career. It is most useful if you are new to DevRel, preparing for a DevRel role, or looking for concrete examples of how other teams run their programs.
What DevRel actually covers
The site frames DevRel as a broad practice rather than a single job. Its guide The four pillars of developer relations and its CORE: A situational analysis framework for DevRel suggest the field is usually broken into a few recurring functions:
- Community — building and moderating spaces where developers gather, ask questions, and collaborate.
- Content and education — guides, documentation, talks, and videos that help developers succeed with a product.
- Advocacy and outreach — speaking, writing, and representing developer needs inside the company.
- Enablement and support — feeding real developer questions back into product and content decisions.
A practical example of how these connect: the guide Using support questions to feed your content calendar treats recurring support questions as raw material for future content, so community, support, and content work reinforce each other instead of running as separate silos.
How the site is organized
DeveloperRelations.com presents its material in labeled sections, which makes it easy to pick an entry point based on what you need:
| Section | What it contains | Good for |
|---|---|---|
| DevRelCon talks | Recorded conference sessions | Seeing current practice and debates |
| DevRel guides | Explanatory articles on methods and frameworks | Learning how DevRel is structured |
| DevRel podcasts | Audio conversations | Following the field over time |
| DevRel reports | Research and survey-style write-ups | Understanding trends |
| DevRel case studies | Accounts of specific programs | Learning from real implementations |
| DevRel origin stories | Career paths into DevRel | Seeing how people actually get in |
The case studies are notably concrete. Examples listed on the site include Marketplace monetisation the wrong way, Globalising a champions program, Scaling developer content production at Snyk, and Overcoming spam during Hacktoberfest — each describing a specific problem and how a team responded, rather than general advice.
Starting points if you are new
The site keeps a dedicated New to DevRel? entry with three questions it answers directly:
- What is developer relations?
- How to get a job in DevRel?
- Do you need to be a developer to work in DevRel?
That last question matters because it addresses a common assumption. The origin stories section reinforces the same point: the paths listed include From Engineer to Boot Camp Teacher to Senior Developer Advocate, From Blogger to Senior Developer Advocate at AWS, From Spare Time Content Creator to Internal Developer Advocate, and Internal DevRel for the Games Industry. These show entry routes from engineering, writing, and content creation, not a single required background.
Events and other services
The site also lists events, including DevRelCon New York 2026 on 22–23 July 2026 in New York, alongside DevRelCon training and consulting offerings. A newsletter subscription option is present. The site does not publish pricing on the pages summarized here, so treat training, consulting, and event costs as things to confirm directly rather than assuming they are free.
How to use it
If you want a definition first, start with the What is DevRel? page. If you want to see the work in practice, read a case study or watch a DevRelCon talk. If you are weighing a career move, the origin stories and the "how to get a job" guide give you realistic paths and expectations. The site works best as a starting map: it tells you what the field contains and points you to deeper material, rather than prescribing one correct way to do DevRel.