The pull to get what works to more people
The pull to make things make sense
Explanation · Confused → Understood
The pull to get what works to more people
Spread · Contained → Widespread
The pull to make things make sense
Explanation · Confused → Understood
The pull to get what works to more people
Spread · Contained → Widespread
The pull to bridge what's apart
Connection · Separate → Connected
The pull to give inner experience external form
Expression · Internal → Expressed
An AI developer advocate helps outside developers learn about, adopt and succeed with an AI product, model or platform. The job is a mix of engineering and teaching. A typical week might include writing a tutorial, building a sample application, recording a video walkthrough, answering questions on a forum and giving a talk at a conference. The advocate also carries information the other way, telling the product team where developers get stuck and what they ask for.
Called a developer advocate, developer relations engineer or developer evangelist, and found in technology companies in the US, Europe, India and other regions. Spread is the pull: the work makes a tool known and usable by far more people than the team that built it could reach alone. Explanation is close behind, because most of the effort goes into making something complicated clear enough for a developer to try.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
You are judged by whether developers succeed, not by how many people attend a talk. Honest advocates say where a product is weak, because developers find out fast, and trust is the thing that the role depends on. Advocates who only promote lose their audience.
The ground moves quickly in AI. Models, tools and best practices change within months, so an advocate keeps learning new material while teaching the last version. Content ages fast, and old tutorials need updating or removing.
Most advocates start as software engineers, data scientists or technical writers who also teach: they write a blog, give talks, run a meetup or contribute to open-source projects. Some come from teaching or technical support. A degree in computer science helps but is not required, and a public record of useful tutorials and projects counts for a great deal. Careers lead to senior and lead advocate roles, developer relations management, product management, or engineering and technical writing roles.
Tutorials, sample code and documentation are exactly the content AI drafts fastest, and AI tools are already a normal co-author for this material. But developer trust is built through live demos, honest answers and a real relationship with the community, and that trust does not transfer to AI-written content published without real review.
Routine content drafting keeps automating; value concentrates in the two-way translation between developer pain points and product-team priorities, and in live, in-person credibility a generated page cannot carry.
People drawn to AI Developer Advocate / Technical Educator are often drawn to these, in the order they are closest. The ones marked sit in a different field entirely.