Ø

CHABOT.DEV — A FIELD JOURNAL — VOLUME I, NO. 4

11    TRENDS   ✣

Layoffs and Renaissance.

Three durable observations:

ENTRY · 4 MIN · 832 WORDS

A trend file companion to the historical narrative in ../01-history/death-and-rebirth.md. This file focuses on what the contraction-and-recovery means as a current state, not as history — what is changed about the discipline now, what is still settling, and what to watch.

What the contraction confirmed

Three durable observations:

  1. DevRel without business alignment is structurally fragile. Teams that could not articulate a connection to revenue, retention, or product feedback were cut first. This was not unjust; it was structurally predictable.
  2. Marketing-reporting DevRel is more vulnerable than product- or CEO-reporting DevRel. When marketing budgets shrink, marketing-reported functions absorb a disproportionate share of cuts.
  3. The function survives at PLG companies. Where DevRel is part of the activation funnel, cutting it produces immediate revenue degradation, which makes the cut self-correcting.

What the renaissance has produced

By 2026, several structural changes are visible:

Higher quality bar for DevRel programs

  • Clear metrics, mapped to business outcomes.
  • Explicit strategy documents.
  • AAARRRP, Orbit, Four Pillars in mainstream use.
  • DXI-style satisfaction measurement.
  • Quarterly executive-level reporting.

Programs that operated on vibes and intuition through 2021 have not survived. Programs that operate on data and strategy have.

Different organisational structures

  • More C-suite reporting (CEO / CTO).
  • More embedded models — DevRel members embedded in product teams.
  • Less “VP of Marketing’s DevRel team” as default structure.

Renewed professional infrastructure

  • Developer Relations Foundation under the Linux Foundation (announced August 2025).
  • DevRelCon continuing strong in multiple cities.
  • State of Developer Relations surveys continuing.
  • DevRel-focused courses and certifications through the Product Marketing Alliance, the Developer Marketing Alliance, and DevRel Uni.

Compensation reset

The 2020–2022 boom inflated DevRel compensation at some companies; the 2022–2024 contraction reset it; by 2024–2026 compensation is back to engineering-comparable levels at developer-product companies.

AI as a new home for DevRel talent

A substantial fraction of laid-off DevRel professionals from 2022–2024 found new roles at AI companies (OpenAI, Anthropic, Hugging Face, LangChain, the vector-DB cluster, NVIDIA AI, Cohere, Mistral, etc.). The AI category effectively absorbed the supply of laid-off DevRel talent.

Cross-pollination across companies

The contraction shuffled talent. Many senior DevRel figures now in 2026 roles started 2022 at very different companies:

  • Cassidy Williams: Netlify → GitHub (Senior Director, DevRel).
  • Sarah Drasner: Netlify → Google (infrastructure leadership).
  • Brian Douglas (bdougie): GitHub → OpenSauced (founder).
  • Logan Kilpatrick: Apple / OpenAI → Google AI Studio.
  • Omar Sanseviero: Hugging Face → Google DeepMind.
  • Salma Alam-Naylor: Sentry → Nordcraft (Head of Developer Education).

This shuffle re-distributed expertise across the field — the network effect of which is still playing out.

What remains unsettled

Headcount

  • Most large DevRel functions remain smaller than their 2021 peaks.
  • AI-company DevRel functions are growing rapidly.
  • Net-net headcount at the field level is roughly flat compared to 2021, but distributed differently.

Career path

  • The career ladder for senior DevRel ICs (Staff, Principal, Distinguished) is clearer at some companies than others.
  • Lateral moves between DevRel and adjacent functions (PM, engineering management, customer success) are more common than in 2021.

Tooling consolidation

  • Orbit’s SaaS wind-down (2023) and Common Room’s consolidation suggest the community-CRM category is consolidating.
  • Documentation tooling remains competitive (Mintlify vs. Docusaurus vs. ReadMe vs. GitBook).
  • Analytics tooling has stabilised but PostHog’s open-source rise is reshaping the space.

What “DevRel” means

  • At some companies, DevRel and DevEx have merged.
  • At some, DevRel has been absorbed into Product Marketing.
  • At some, DevRel has split into Developer Education, Developer Advocacy, and Community as separate functions.

The function is more clearly real than ever, but its boundaries are still in flux.

What watchers should monitor

Through 2027–2028:

  • AI’s continued effect. How does agent-mediated developer discovery change DevRel work over the next 2 years?
  • DevRel Foundation maturity. Does it produce professional certifications, standards, or codes of practice?
  • PLG-vs-AI-buyer split. Many AI tools are bought by enterprises rather than developers; does this change AI-company DevRel?
  • Compensation trajectory. Is comp keeping pace with engineering?
  • Reporting structures. Does C-suite-reporting DevRel become more common or less?

Lessons for current and aspiring DevRel professionals

A short distillation:

  1. Align your work to measurable business outcomes. Whatever you produce, connect it to AAARRRP goals and to revenue.
  2. Build your own audience. Newsletter, blog, YouTube, conference speaker history. Portable assets travel with you.
  3. Avoid sole reliance on a single platform. Cross-post; own your URL.
  4. Develop the financial literacy to discuss your function in executive language.
  5. Stay current on AI. AI tools, agentic patterns, prompt engineering, and MCP are now baseline competencies.
  6. Develop deep expertise in something. Generalist DevRel professionals are more replaceable than specialists with credibility.
  7. Build relationships across the field. The DevRel Collective, the DevRel Foundation, and your peer network matter more than ever.

See also