Developer Advocate - fireworks

OpenTalent; San Francisco (CA); Hybrid; USD 140,000 - 210,000; Full time

Job summary

OpenTalent in San Francisco is seeking a developer content engineer to create runnable tutorials and end-to-end guides. You will publish cookbooks, quickstarts, and reference apps that move developers from zero to production-ready inference calls.

You’ll build demos, benchmarks, and concrete how-to content, engaging with communities across docs, blogs, and social platforms to broaden OpenTalent’s voice and impact.

Responsibilities

• Publish runnable content (tutorials, apps, deep dives) that developers can fork and run.
• Create end-to-end tutorials and reference applications leading to production-ready results.
• Own launch responses with demos, benchmarks, and how-to guides for immediate usage.
• Engage developers on multiple platforms (docs, blogs, Discord, newsletters) and external venues.
• Identify friction and feature gaps and communicate them to product/engineering with evidence.

Job description

WHAT YOU'LL DO

Build things developers can run. Ship cookbooks, quickstarts, reference applications, and end-to-end tutorials that take a developer from zero to a working inference call and then to something production-shaped. Everything you publish is code someone can fork and run, not a screenshot of code that worked once on your machine.

The bar is content a senior engineer respects and a new developer can follow, ideally both in the same artifact.

Own the launch response. When a significant model or technique lands, you're among the first credible voices with a working demo, an honest benchmark, and a "how to actually use this today" guide. You'll help build the internal loop (model access, eval harnesses, publishing paths) that makes day-one content a process rather than an all-nighter.

Show up where developers are, owned and unowned. On our properties, that's docs, blog, examples, cookbooks, Discord, and the developer newsletter. On properties we don't own, that's GitHub, X, Reddit, YouTube, Hacker News, and the open-source projects our developers depend on, including contributing code and reviewing PRs where it matters.

You answer real questions in public and turn the recurring ones into permanent content.

Speak, teach, and run the room. Conference talks, hands-on workshops, hackathon mentoring, and developer dinners. You'll help decide where Fireworks shows up and what we say when we get there, and you'll build the material so the next person can deliver it without starting over.

Be the developer's voice inside Fireworks. Bring friction, feature gaps, and unmet needs back to product and engineering with evidence: a failing repro, a thread of five people hitting the same wall, a competitor's ergonomics that are simply better. Then close the loop publicly when we ship the fix.

Measure what you do. You'll instrument your own work: what content drove signups, which events produced developers who actually built something, where people fall out between first call and production. We care about adoption, activation, and time to first successful build. We do not care about impressions, booth scans, or attendance counts, and we won't ask you to report them.

WHAT SUCCESS LOOKS LIKE IN THE FIRST YEAR

• 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.