Experience designing or shipping a CLI, SDK, API, or MCP surface used at scale
Experience designing agent-facing documentation, Blueprints, Skills, or other material intended to teach a model how to operate a system
Familiarity with OAuth, scoped tokens, or least-privilege access models — or an appetite to make permissions feel humane
Hands-on experience building with coding agents or LLM-driven tooling, with a view on where the agent loop breaks down today
Design-engineering literacy: motion, prototyping, or front-end fluency
Experience evolving a developer-first product toward larger teams and enterprises without losing the original audience
Writing, talks, or side projects that show your craft and point of view on developer experience
This is a new category, and nobody has all the answers yet — including us. If you're the kind of designer who's curious enough to figure things out, ship, learn what's wrong, and try again, we'd love to hear from you
If this role excites you but you don’t meet every single requirement, we’d still love to hear from you—your unique experience might be just what we need
7+ years of product design experience, ideally on developer tools, infrastructure, APIs, or another technical, credibility-driven product. You may have worked as a product designer, a designer who codes, or something harder to label — the title matters less than the work. At this level, we expect someone who has owned a major surface or product area end to end and set the direction others built against
Craft that spans GUI and non-GUI surfaces. You have an eye for detail that borders on obsessive — the wording of an error, the shape of a command, the structure of an API response, the spacing of a dashboard — and you're as rigorous about a CLI message or an SDK method as you are about a screen. Your portfolio shows strong web UI work alongside text-first thinking: command design, API ergonomics, MCP/SDK design, docs-as-experience, or conversational interfaces
You design the whole journey, not a surface at a time. Your portfolio shows end-to-end experiences — a user carried coherently across interface boundaries, CLI to API to SDK to dashboard and back — where you designed the model once and expressed it everywhere it appears, rather than polishing one surface in isolation
A genuine point of view on what AI-native products mean for design — including how a product should show up to an agent, and not only to a person
Comfort near code. You can read it, prototype with it, and collaborate with engineers without a translation layer in between
The judgment to define quality where no established playbook exists, and the rigor to hold that bar once you've set it
Clear, direct communication and cross-org influence. You can make the case for AX to technical and non-technical partners alike, in rooms where it's easy to treat it as purely an engineering concern — and you can align product, engineering, and leadership around a direction without formal authority over them