AI Developer Advocate Jobs
Code + Community.

AI Developer Advocates are the bridge between AI companies and their developer community. Your job is to help developers succeed with AI tools and APIs. This includes creating tutorials and documentation, speaking at conferences, building demo apps, engaging on social media, gathering product feedback, and generally being the technical face of the company to the outside world. It's equal parts engineering, teaching, and community building.

You don't need a PhD or ML research background. What you need is the ability to understand AI concepts deeply enough to explain them simply, and enough coding skill to build real implementations. If you can build applications with LLM APIs, understand concepts like RAG, embeddings, and prompt engineering, and can learn new technical material quickly - you're technical enough. The communication and community skills are often harder to find.

Content creation is learnable. Most successful Developer Advocates weren't natural content creators - they developed the skill through practice. Start small: write about what you're learning, document solutions to problems you've solved, share code snippets with explanations. You don't need to be a polished YouTuber on day one. What matters more is authenticity and genuine helpfulness.

Very. Most AI DevRel roles offer remote or hybrid options, since the work involves engaging with a distributed global developer community. That said, expect travel for conferences, company offsites, and community events - typically 20-40% depending on the role. Many advocates appreciate this balance: focused work from home, with regular opportunities to connect in person.

Common paths include: Senior DevRel/Staff Advocate (deeper expertise, larger impact), DevRel Lead/Manager (building and leading DevRel teams), Head of Developer Experience (strategic role combining DevRel, docs, and DX), Product roles (your community insight makes you valuable in product), and Founding/Startup roles (many advocates start companies serving developers). The community and reputation you build open many doors.

No. While a following helps, companies care more about the quality of your communication and your ability to grow an audience than your current numbers. A well-written blog post, a useful GitHub repo, or a clear talk at a local meetup can be more impressive than 10K Twitter followers who don't engage. Focus on demonstrating the skills - the audience will follow.

It probably isn't, and you should hold the money. Most cohort dropouts are people who couldn't articulate what they were shipping when they signed up. That's why the consult exists, and why I turn down most applications. If we get on the call and you can't tell me what you'll have shipped at the end of week 8, I'll point you to the AI Native Engineer community until you can.

Yes, the cohort works for people shipping their first serious AI system whether the goal is to land a senior role or to launch a product. The shipped system serves both equally well.

You need to be able to code in Python or TypeScript. Complete beginners can follow the classroom they get access to before the cohort sessions to come in well-prepared.

You'll spend 3 hours every Tuesday in the live session and roughly 3 hours of async work in between, for 8 weeks. The Tuesday session time is fixed.

It's a four-figure investment that we discuss during the 30-minute consult, alongside whether the cohort is the right fit for your project.

Yes, most attendees do. The live session is one Tuesday a week and the async work fits around your existing schedule, as long as you can carve out roughly 6 hours a week.