Developer Experience Engineer

We're hiring a Developer Experience Engineer to own the developer experience end-to-end, making Black Forest Labs the platform that wins on developer experience. You'll work with the API/platform engineering team, research, and DevRel to design and ship features that improve the developer experience. You'll partner with platform engineering on API design, work with product engineering on developer-facing surfaces, and own the portfolio of entry points developers and agents reach for.

Responsibilities:

• Own DevExp as a product surface - wherever the bottleneck is, that's where you ship next.
• 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.
• Make Black Forest Labs the best visual AI platform for agents to use. Own the MCP server, skills, agent onboarding paths, and the machine-readable surfaces of the platform.
• Design the reference patterns and SDK primitives developers reach for when building agentic workflows on FLUX.
• Stress-test every API and SDK change against 'would Claude / GPT / an autonomous agent get this right on the first try?' - and treat agents as a first-class user across the whole product.

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

Nice to Have:

• Background at a developer platform where DevExp was a top-level metric (Stripe, Vercel, Cloudflare, Modal, Replicate, Resend, Linear, Anthropic platform, etc.).
• You've built or meaningfully contributed to an MCP server real users / agents rely on.
• Experience with media-generation or other high-latency, async, job-shaped APIs - and the UX puzzles that come with them (polling, webhooks, partial results, cost surprises).
• A public surface - OSS, a writeup, a dashboard you're proud of - that lets us see your taste before the interview.