Developer Experience Engineer

Responsibilities

• Own DevExp as a product surface - wherever the bottleneck is, that's where you ship next. One sprint that might be the API contract, the next it's the dashboard onboarding, the next it's an MCP server, the next it's a Python SDK abstraction
• Partner with platform engineering on API design before it ships, not after - bring the developer-and-agent perspective into the room when the contract is being decided
• Work with product engineering on the developer-facing surfaces of the dashboard - playground, API keys, usage, request inspectors, webhook debugging - bringing the DevExp lens to features the rest of the team is already shipping
• Partner with the Growth engineer and Product on the developer funnel - signup → first key → first call → first production call → repeat - and own the DevExp fixes for the cliffs they surface
• Be opinionated. Versioning, error formats, breaking change policy, idempotency, naming - you have takes and you can defend them. The bar is Stripe: an API and SDK so well-designed the docs almost feel unnecessary.

Requirements

• 4+ years building software, with meaningful time on developer-facing products - SDKs, APIs, dashboards, consoles, platforms developers actually use
• Full-stack comfortable. TypeScript / React / Next on the front, Python (and ideally Go or Rust) on the back. You don't need a separate person to wire the two halves of a feature together.
• Deep instincts on API design - you have opinions about error formats, pagination, async job shapes, breaking changes, and you've lived with the consequences of bad ones
• Fluent in the 2026 agent stack - MCP, tool use, the major agent runtimes - and you know what breaks when an LLM is the one reading your error message or browsing your API
• You've shipped developer-facing product that real external developers depend on. Not internal tooling.
• You ship. This is product engineering, not product management with an IDE open.
• Background at a developer platform where DevExp was a top-level metric (Stripe, Vercel, Cloudflare, Mod

Benefits

Additional Information

About Black Forest Labs We're the team behind Latent Diffusion, Stable Diffusion, and FLUX-foundational technologies that changed how the world creates images and video. We're creating the generative models that power how people make images and video-tools used by millions of creators, developers, and businesses worldwide. Our FLUX models are among the most advanced in the world, and we're just getting started. Headquartered in Freiburg, Germany with a growing presence in San Francisco, we're scaling fast while staying true to what makes us different: research excellence, open science, and building technology that expands human creativity. Why This Role FLUX is the model developers want. BFL still has to become the platform they choose. In 2026 that platform is judged by a single question, asked by both humans and the agents acting on their behalf: how fast can I go from idea to a production-shaped call, and how good does it feel along the way? We're hiring one person to own that answer end-to-end. Not the SDK alone, not the dashboard alone, not the API alone - the whole developer experience, for both the humans building on BFL and the agents building on their behalf. You're the person on the team who breathes DevExp: spotting where the platform is friction for a developer or for an agent, deciding whether the fix lives in the API contract, the SDK, the console, the docs surface, the MCP server, or the onboarding flow - and then shipping it. You sit inside product engineering. You work shoulder-to-shoulder with the API/platform eng team (think: designing the next API revision), with research as new capabilities land, and with DevRel. Your job is to make BFL the platform that wins on developer experience, the way Stripe won payments and Vercel won frontends.

Your Match

How well this role fits your profile.

Company Intel

What employees say

Worked at blackforestlabs? Share your experience