Developer Relations has always been about meeting developers where they are, but what happens when "developers" aren't just humans anymore? AI agents are rapidly becoming first-class consumers of our APIs, documentation, and tooling, and they don't attend meetups or watch conference talks but are rather parsing your public documentation and sample repositories at 3AM, making decisions based on what they discover. It's happening now and it fundamentally changes what Developer Relations needs to be.
This talk explores how DevRel must evolve when the audience has rapidly expanded to include two new categories of users: humans who build with the help of AI-enabled tools, and AI that operates autonomously. We'll dig into the critical questions: is the documentation agent-readable? Are the APIs designed for non-human consumers? What does "developer experience" mean when the developer never sleeps and has no patience for ambiguity?
We'll also address the new challenges head-on: trust gets harder when agents act on behalf of users, support gets messier, and traditional success metrics start to break down. The upside is proportionally substantial: DevRel teams equipped with AI tools can produce more content, reach more developers, and respond faster than ever before, multiplying their impact.
Whether you're in DevRel, building developer tools, or just curious about where this is all heading, this session will give you a practical framework for thriving when your newest power users don't have a physical presence. So far…

Learning outcomes:
- Developer Relations now serve two new audiences, AI-assisted developers and AI agents, each with different expectations and needs.
- Traditional metrics are not suitable for the Agentic age.
- AI tools multiply DevRel impact and teams that embrace them gain a competitive edge.
- When agents act on behalf of developers, trust and guardrails become DevRel problems.