Developer Experience Engineer

Own developer experience as a product surface across the entire BFL platform—from API design and SDKs to dashboards, console, docs, and MCP servers. You'll work shoulder-to-shoulder with platform engineering, research, and DevRel to make BFL the platform developers and agents choose, the way Stripe won payments and Vercel won frontends.

What you'll do

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

What you'll need

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

What they offer

• Distributed team with offices in Freiburg and San Francisco; work hybrid with at least 2 days per week in-office (or one full week every other week), or remote with monthly in-person week.
• Travel costs covered for in-person time.