Skip to content

Black Forest Labs

Developer Experience Engineer

Black Forest Labs is hiring a Developer Experience Engineer. It pays €140k-€190k a year and Level rates it ; you can apply on Black Forest Labs.

Level's read on this job

  • Works on AI ●●●○ is how Level rates this role: the daily work is on AI products, without building the model.
  • The posting mentions Claude, Anthropic and Replicate among its tools and skills.
  • Level classes it as a mid-level role.
  • Black Forest Labs has 14 other open roles on Level.

AI in this role

ClaudeAnthropicReplicateStable Diffusion
ai-agents

About Black Forest Labs

We’re the team building the foundational layer for visual intelligence: multimodal models trained jointly on images, video, audio, and action to see, generate, and understand the world.

Our founding team pioneered latent diffusion and Stable Diffusion, the breakthroughs that made generative AI accessible to millions. With FLUX, we're pushing into generative media at scale, machines that act in the physical world, and emerging applications in computer use.

Our FLUX models top public benchmarks and run in production in some of the world's biggest platforms. We're a small, fast growing research lab competing with the largest companies in the world. From our labs in Freiburg to San Francisco, we're building what comes next.

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.

What You’ll Work On

  • 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

  • Make BFL 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 (errors an LLM can recover from, capabilities discoverable without a human reading docs, audit trails that make sense when most of the traffic on an account isn't a person).

  • Own the portfolio of entry points developers and agents reach for — SDKs (Python, TypeScript, more on demand), MCP server, skills, OpenAPI / typed surfaces — and treat them as a portfolio, not a hierarchy. SDKs add composable workflows and sane defaults for async / polling / retries; MCP and skills make BFL trivially usable from any agent loop. DevRel and the Creative Technologist team partner on examples, content, and showcase work on top of these surfaces — you own the surfaces themselves.

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

What We’re Looking For

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

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

How We Work Together

We’re a distributed team with real offices that people actually use. This role is based in Freiburg or San Francisco, and you’ll join us in the office at least 2 days a week, or one full week every other week.

Everything we do is grounded in four values:

  • Obsessed. We are a frontier research lab. The science has to be right, the understanding deep, the product beautiful.

  • Low Ego. The work speaks. The best idea wins, no matter who said it. Credit is shared. Nobody is above any task.

  • Bold. We take the ambitious bet. We ship, we do not wait for conditions to be perfect.

  • Kind. People over politics. We treat each other with genuine warmth. Agency without empathy creates chaos.

If this sounds like work you’d enjoy, we’d love to hear from you.

Base Annual Salary:

EU €140,000 - €190,000 + Equity

Note: We may use AI-assisted tools to help organize applications. All hiring decisions are always made by our team.

How we rate this

Developer Experience Engineer at Black Forest Labs rates 71 out of 100 for how much of the daily work is AI. That makes it Works on AI (AI Level 3 of 4). The level is about AI in the job, not seniority.

Classification

Works on AI. The daily work is on AI products, without building the model.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.

Prepare for this job

Built from this posting and from similar jobs on Level.

Skills and AI tools this role asks for

AI agentsClaudeAnthropicReplicateStable Diffusion

Questions you could be asked

  1. How do you decide when an AI agent can act on its own versus asking for approval first?
  2. Walk me through how you've used Claude in your day-to-day work.
  3. What are the limits of Anthropic that you've run into, and how did you work around them?
  4. What's a project where you used Replicate hands-on?
  5. Walk me through how you've used Stable Diffusion in your day-to-day work.

Adapt your resume

  • List these exact terms on your resume: AI agents, Claude, Anthropic, Replicate, and Stable Diffusion. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
  • Show where AI is part of your daily process, not a one-off project. This role expects it to be a running habit.

Get your CV reviewed before you apply

Send your CV and the role you want next. Your review arrives by email within 3 days.

Get new software engineering jobs (Works on AI ●●●○ or higher) by email

One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free.

Similar roles

Software Engineering roles that work on AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at Black Forest Labs

Related searches

Same AI level