Developer AdvocateActive$200K–$230K

Fireworks AI
Apply now

The opportunity

Fireworks is the platform for specialized intelligence, enabling companies to build, train, and serve AI models tailored to their own data, workflows, and products. Founded by the team behind PyTorch and backed by AMD, Atreides, Benchmark Capital, Index Ventures, Lightspeed,…

What you'll do

  • You've published a body of technical work (tutorials, apps, deep dives) that: developers cite and competitors read.

  • When a major model drops, Fireworks has authoritative, runnable content out: fast enough to be part of the conversation rather than a follow-up to it.

  • You have a credible, recognized presence in developer communities where we: weren't previously part of the discussion.

  • You've spoken at multiple significant events and left behind a workshop or: talk that others on the team can now deliver.

  • Product and engineering can point to specific roadmap decisions that changed because of feedback you surfaced.

  • The content and launch standards you set are what new advocates onboard into,: and they hold up without you in the room.

What they're looking for

  • + years of combined engineering and developer-facing experience , with real: time in both. For example, several years shipping production software plus meaningful time in DevRel, developer education, technical writing, or solutions engineering. We're flexible on the ratio and inflexible on the requirement that both are genuinely there.
  • You can code and read diffs. Strong Python; comfortable in: TypeScript/JavaScript. You've built and deployed applications yourself, and you can review someone else's sample and tell whether it's good.
  • Hands-on with the modern AI stack. You've worked with LLM APIs in production,: built with at least one agent framework, and have personally fine-tuned, evaluated, and deployed a model, not just read about it. You understand what inference latency, throughput, and cost actually depend on.
  • A public track record. Technical writing, talks, videos, open-source work, or: a following you earned. Something we can go read or watch that shows you can explain hard things well to engineers.
  • Demonstrated speaking ability. You've presented at conferences, meetups, or: workshops, and you're comfortable doing it on short notice about something that shipped last week.
  • Learning velocity. You can go from "this paper came out Tuesday" to "here's a: working implementation and an honest assessment" quickly, and you have a system for staying current rather than relying on luck.
  • Ownership instinct. You pick your own topics, scope your own projects end to: end, and don't need a content calendar handed to you. This role is early enough that you'll be defining the work as often as executing it.