About Us:
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, NVIDIA, Sequoia Capital, and TCV, Fireworks powers production AI with hundreds of state-of-the-art open models across text, image, embedding, audio, and multimodal workloads. Today, Fireworks is a Series D company valued at $17.5 billion, bringing together an ambitious, collaborative team that's building the future of enterprise AI.
The Role
Every developer who tries Fireworks has a first five minutes. They land on the site, sign up, grab an API key, pick a model, and make their first call. If it works, they build. If it fails, they leave, usually for good.
Developer Experience drives that journey and everything after it: the path from first visit, to first successful API call, to a team running production workloads and growing on Fireworks across inference, fine-tuning, and the rest of the platform.
We're looking for a product-minded engineer to join as one of the first engineers on Developer Experience, and own the surfaces that make that path real: signup and onboarding, the developer console, quickstarts, the API and model playground, model choice and defaults, error messages, pricing, billing and usage, and lifecycle messaging.
You'll work directly with external customers, from solo developers to enterprise engineering teams. You'll get on calls, watch them build, and turn what you learn into products that customers and developers actually use. You'll also look across the whole platform, from inference and fine-tuning to the console and billing, for the places where a new 0-to-1 product can unblock users and drive exponential growth.
This is a high-autonomy IC role on a small team. There's an early roadmap, but the market moves every week, so you'll help find the problems as much as solve them. You'll own features end to end: from watching where developers get stuck, to designing the fix, to shipping it, to seeing whether it worked. If you're the kind of engineer who ships fast, cares how a product feels, and doesn't wait to be told what to build, this role has enormous leverage and nothing standing between you and impact.
What You'll Do
- Own product surfaces end to end across the developer journey: signup, onboarding, the developer console, quickstarts, the API and model playground, model selection, errors, pricing, billing, and usage. Scope the problem, build it, ship it, instrument it, and iterate on real usage.