SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Fireworks is a Series D AI infrastructure platform (valued at $17.5B) backed by NVIDIA, Sequoia, Benchmark, and others, enabling companies to build, train, and serve specialized AI models on their own data. As a Developer Advocate, you'll be one of the first in this role, helping set standards for how Fireworks engages the developer community.
You'll operate at the intersection of engineering and technical communication. On the engineering side, you ship production-quality code: cookbooks, quickstarts, reference applications, and end-to-end tutorials that developers can fork and run immediately. You understand batching, quantization, fine-tuning, and can hold technical conversations with senior engineers. On the communication side, you write clearly enough that senior engineers forward your work, you're effective on stage, and you have or build a real presence in developer communities (GitHub, X, Reddit, Hacker News, Discord, open-source projects).
Key responsibilities include: shipping runnable technical content that bridges zero-to-working-inference and production-ready systems; owning launch response when major models or techniques drop, with working demos and honest benchmarks within days; showing up at conferences, hackathons, meetups, and developer events (expect 20-25% travel quarterly); speaking and teaching at significant events; bringing developer friction and feature gaps back to product/engineering with evidence; and measuring impact through adoption, activation, and time-to-first-successful-build metrics.
Success in year one means publishing a body of technical work that developers cite, having authoritative runnable content ready when major models launch, building credible presence in communities where Fireworks wasn't previously part of the conversation, speaking at multiple significant events, and helping product/engineering prioritize based on real developer needs.
The role is based in San Mateo, CA or London, UK. If London-based, you'll anchor European developer community presence, work across time zones with a primarily US team, and travel periodically to San Mateo for onsites. Travel is concentrated around major events and launches.
