16. AI Developer Advocate
Evidence label: Role family, often posted as Developer Advocate, Developer Relations Engineer, or Technical Evangelist for an AI platform.
What they do
Build the bridge between an AI platform and the developers who use it. Part engineer, part educator, part community builder. They go deep enough technically to build real things with the platform, then turn that knowledge into tutorials, documentation, sample projects, and public presence that helps other developers succeed.
Responsibilities
- Build technical demos, sample projects, and integrations using the platform's APIs
- Create developer content: tutorials, blog posts, video walkthroughs, conference talks
- Represent developer needs and pain points to the product and engineering teams
- Engage with developer communities (Discord, GitHub, forums, social)
- Speak at conferences and run workshops
- Onboard strategic partners and enterprise developers
- Gather and synthesize developer feedback into product improvements
Required skills
| Technical | Soft |
|---|---|
| Solid software engineering foundations | Clear technical writing |
| Deep familiarity with the platform/API | Public speaking confidence |
| Ability to build quick, illustrative prototypes | Community instinct |
| Understanding of developer experience (DX) | Empathy for confused users |
| Familiarity with AI concepts (prompting, RAG, agents) | Curiosity and continuous learning |
What makes this role different
The audience is other developers, not end users. DevRel success measures developer activation (do developers try the product?), retention (do they keep using it?), and advocacy (do they tell others?). Credibility is the core asset, which means you have to actually build things, not just talk about them. A DevRel who hasn't shipped real production code with the platform has no credibility with the audience they're trying to reach.
Where these roles are
AI labs, model providers, agent frameworks, and developer-facing platforms use Developer Advocate or Developer Relations titles. Confirm the current employer and product scope before treating an old listing as evidence of an open role.
Entry paths
Software engineer with a public presence (blog, open source, conference talks), technical writer with engineering background, early AI community member who builds in public.