Future Directions.

A speculative file, intentionally less data-driven than the rest of this almanac. What follows is the author’s best read of where the field is heading, why, and what to watch.

These are predictions and patterns, not facts. Treat the confidence levels accordingly.

1. Agent experience as a deliberate practice

By 2027 or earlier, “Agent Experience Engineer” will be a real job title at AI-adjacent infrastructure companies. The discipline of designing APIs, docs, and developer-facing surfaces specifically for AI agents is emerging now; within two years it will be a recognised specialty.

What this looks like:

• API design reviews include “how does an agent use this?” as a section.
• Documentation pipelines have an AI-readability lint step.
• MCP servers and equivalents are standard product surfaces.
• Some DevRel teams reorganise into “human DX” and “agent DX” sub-teams.

2. The unbundling of “DevRel”

The term will continue to fragment. By 2028 it will be plausible that:

• “Developer Advocate” remains the canonical IC title for public-facing advocacy.
• “Developer Educator” stabilises as a separate role with its own career path.
• “Community Manager” stays a distinct discipline.
• “Developer Experience Engineer” becomes a peer engineering role.
• “Developer Marketer” is fully a marketing sub-discipline.
• The umbrella term “DevRel” persists but means less in any specific context.

This is consistent with how other disciplines mature — early generalist terms split into specialist sub-fields as the work deepens.

3. AI replaces some tactics, not the function

Tactics likely to be substantially augmented or replaced by AI:

• First-line community support. AI assistants handle the “how do I X” questions; humans handle the harder ones.
• Initial draft content production. Posts, social, video scripts.
• Documentation gap analysis.
• Sentiment analysis and community signal detection.
• Personalised outreach at scale.

Tactics that will remain human-led:

• Authentic public voice. Trust does not transfer to anonymous AI-generated content.
• Strategic relationships. A founder calls another founder; AI can’t.
• Conference speaking. In-room presence matters.
• Community judgement. Hard moderation decisions, conflict resolution.
• Product feedback synthesis at the strategic level.

The DevRel professional of 2028 will use AI as default leverage but operate on the human-led layer of work.

4. Open-source and OSS sustainability moves further to the centre

Three forces compound:

• AI training data ethics. Open-source projects whose code is in training data are demanding more visibility on attribution and sustainability.
• Supply-chain security. Companies need to know who maintains the dependencies they ship.
• Founder-burnout patterns. OSS sustainability has visible failure modes; companies that depend on OSS will increasingly fund it.

For DevRel teams, this means open-source sponsorship moves from “occasional gesture” to “core operational discipline.” Maintaining a budget for OSS support, with clear allocation criteria, becomes a standard DevRel responsibility.

5. Conferences continue to bifurcate

Two parallel trends:

• Mega-flagships (re:Invent, GTC, Google I/O, Build, GitHub Universe) continue to grow.
• Small, curated, community-led events continue to grow.

The middle — generic 2,000-person commercial conferences — continues to thin.

For DevRel programs, this implies:

• High investment in flagship presence remains worth it for category-leader companies.
• High investment in carefully chosen smaller community events compounds.
• Generic conference sponsorship has the worst ROI.

6. The first-touch shifts further toward LLMs

By 2027, more than half of developer initial research will happen through AI assistants rather than search engines, for many product categories. This implies:

• AI-citation optimisation becomes a real discipline.
• Authoritative long-form content rises in relative value.
• SEO content optimised for Google ranking declines in relative value.
• Documentation must be machine-first as well as human-first.

7. Community-CRM tooling consolidates

The community-data category will consolidate into two or three dominant providers by 2027:

• Common Room or a successor as the commercial leader.
• LFX Community Data Platform as the foundation-grade option.
• Best-in-class build-your-own data warehouses for the largest companies.

The current fragmentation of dozens of small tools will not persist.

8. The Developer Relations Foundation becomes consequential

If the Foundation succeeds in its 2025–2027 phase:

• Professional certifications emerge.
• Standardised job ladders become available for reference.
• Industry compensation surveys carry more weight.
• The Foundation becomes a meaningful voice in industry conversations.

If it doesn’t (failure modes: governance disputes, lack of resources, founder departure), DevRel remains an informal profession with no central institution. Both outcomes are possible.

9. Hardware-DevRel becomes important again

AI’s hardware dependency is producing a renaissance in hardware-developer engagement that the industry hasn’t seen since the 2000s:

• NVIDIA’s DevRel is one of the most strategically important in technology.
• AMD, Intel, Google TPU, AWS Trainium / Inferentia all increase investment.
• Edge-AI hardware (Apple Neural Engine, edge inference chips) drives new developer engagement.

Many DevRel professionals who joined the field through cloud / SaaS work will reskill into hardware-and-software-stack work over the next several years.

10. The geographic distribution continues to broaden

The DevRel field has been disproportionately US- and Europe-centric. The next wave of growth comes from:

• India. Where developer populations are large and DevRel programs are growing rapidly (Aditya, DevRelCon Bengaluru, the growing community of senior Indian DevRel practitioners).
• Latin America. Growing senior cohort, especially in Brazil, Argentina, Mexico, Chile.
• Africa. Particularly Nigeria, Kenya, South Africa, Egypt.
• East Asia beyond Japan. Korea, Vietnam, Indonesia, Singapore continue to mature.

By 2030, the field will look meaningfully more global than today.

11. Compensation continues to align with engineering

Through the rest of the decade, compensation for senior DevRel professionals at developer-product companies will converge with senior engineering compensation. Already, IC4–IC6 DevRel roles at top developer-product companies command total compensation comparable to staff/principal engineers. This continues.

Implications:

• Career attraction improves.
• Career risk of being in DevRel rather than engineering decreases.
• Engineering-to-DevRel mid-career moves become more common.

12. Some current orthodoxies will be relaxed

Predictions in this category are by nature speculative, but a few patterns worth watching:

• “DevRel doesn’t do sales.” Increasingly, DevRel at PLG companies does contribute directly to revenue. The strict separation softens.
• “DevRel reports to product not marketing.” The strong default has emerged, but hybrid and CEO-direct reporting are increasingly common.
• “Vanity metrics are useless.” True — but they remain useful internally as health indicators if used carefully. The all-or-nothing framing will soften.

13. AI-engineering becomes a permanent sub-field of DevRel

The “AI Engineer” identity, popularised by swyx and others starting 2023, has stabilised by 2026 as a real category. By 2030 it will be a permanent sub-discipline of DevRel, with its own conferences, publications, frameworks, and senior practitioners.

This category includes DevRel at:

• Foundation-model providers.
• AI infrastructure platforms.
• Vector databases.
• Orchestration frameworks.
• Agent frameworks.
• AI-developer tools.

The career path “AI DevRel” is now distinct from “Cloud DevRel” or “API DevRel.”

What could surprise us

Several developments could surprise the field:

• A major AI-product DevRel team failure — a high-profile cut at OpenAI / Anthropic / similar — would reshape narratives about how durable AI-company DevRel is.
• A Linux Foundation–level governance event at the DevRel Foundation could either elevate or undermine the profession’s institutional infrastructure.
• A category-defining open-source breakthrough (a new framework that becomes a new standard) could reshape what DevRel work looks like.
• A platform shift (web → AR/VR, or LLM-first interfaces replacing both) could obsolete current channels rapidly.

The field has been surprised before. It will be surprised again.

See also

• ./ai-and-llms.md
• ./plg-and-devrel.md
• ./devex-movement.md
• ./layoffs-and-renaissance.md
• ../12-resources/foundations-and-orgs.md