Job opportunity
Senior Product Designer
Camunda
About The Role
Mission
Own the experience of everything customers and agents use without a UI: the public API, CLI, SDKs, and configuration. Make it fast to get to production and trustworthy once there, and make it the interface of the future for agents.
Time split
30% Strategy
Own the overall headless experience across products, making it the interface agents prefer to work with, held to a consistently high design bar
Define and evolve API and developer-experience conventions (patterns, consistency, error handling, documentation standards)
Treat agent-facing surfaces (MCP servers, tool descriptions, schemas, CLI output) as designed products, not by-products of the API
Define how we measure agent experience (agent task success rate, error recovery rate, tool-call efficiency) and test designs with agents as well as with people
Set the standard for how agents discover, call, and recover from errors in our APIs and tools
Collaborate with Product, FDE, Marketing, and Legal on topics that touch the headless experience
Align with the UI/UX product designer so UI and headless feel like one product (shared terminology, patterns, journeys)
Enable builders with tools, training, and guidance, and give feedback on epics
70% Initiative work
Co-own assigned initiatives with the PM
Own the headless customer journey and experience of each initiative, from first API call to production operation
Focus on Time to First Production and Production Confidence
Design the agent journey inside each initiative: how an agent builds, runs, and operates the solution on a user’s behalf, including recovery when a call fails
Level
Senior. The role combines hands‑on initiative work with shaping principles that outlast any single initiative. If the scope grows toward setting direction across teams, we will revisit Principal.
What You Will Do
Own the headless experience as one product with clear ownership and a real design bar
Shorten the path from first API call to running in production
Build confidence that teams can trust the API in operation
Design for agents as first‑class users, alongside humans
Keep one experience together with the UI/UX product designer at the seam between UI and headless
Enable builders so API design quality does not depend on one person
What You’ll Be Doing
Own the headless experience as one product with clear ownership and a real design bar
Shorten the path from first API call to running in production
Build confidence that teams can trust the API in operation
Design for agents as first‑class users, alongside humans
Keep one experience together with the UI/UX product designer at the seam between UI and headless
Enable builders so API design quality does not depend on one person
Expected outcomes (first 6 to 12 months)
A clear definition of what "good" looks like for the headless experience, with principles and conventions that builders actually apply
Measurable progress on Time to First Production for the assigned initiatives
A well‑defined interface with the UI/UX product designer, with no breaks between UI and API experiences
Agents can discover, call, and recover from errors in our APIs and tools without human help, with a measurable agent task success rate
What You Bring
Ability and/or willingness to use our product.
Design background with real experience on API, developer, or platform products (not a pure engineer)
B2B SaaS experience, ideally in highly regulated industries
Has designed APIs, CLIs, MCP servers, or tool schemas that LLM agents consume, and knows how they fail (ambiguous errors, non‑idempotent calls, capabilities an agent cannot discover)
Hands‑on experience with agent‑first or AI‑first experiences
Ability to make abstract systems concrete, testable, and explainable
#J-18808-Ljbffr
Apply on source site Mission
Own the experience of everything customers and agents use without a UI: the public API, CLI, SDKs, and configuration. Make it fast to get to production and trustworthy once there, and make it the interface of the future for agents.
Time split
30% Strategy
Own the overall headless experience across products, making it the interface agents prefer to work with, held to a consistently high design bar
Define and evolve API and developer-experience conventions (patterns, consistency, error handling, documentation standards)
Treat agent-facing surfaces (MCP servers, tool descriptions, schemas, CLI output) as designed products, not by-products of the API
Define how we measure agent experience (agent task success rate, error recovery rate, tool-call efficiency) and test designs with agents as well as with people
Set the standard for how agents discover, call, and recover from errors in our APIs and tools
Collaborate with Product, FDE, Marketing, and Legal on topics that touch the headless experience
Align with the UI/UX product designer so UI and headless feel like one product (shared terminology, patterns, journeys)
Enable builders with tools, training, and guidance, and give feedback on epics
70% Initiative work
Co-own assigned initiatives with the PM
Own the headless customer journey and experience of each initiative, from first API call to production operation
Focus on Time to First Production and Production Confidence
Design the agent journey inside each initiative: how an agent builds, runs, and operates the solution on a user’s behalf, including recovery when a call fails
Level
Senior. The role combines hands‑on initiative work with shaping principles that outlast any single initiative. If the scope grows toward setting direction across teams, we will revisit Principal.
What You Will Do
Own the headless experience as one product with clear ownership and a real design bar
Shorten the path from first API call to running in production
Build confidence that teams can trust the API in operation
Design for agents as first‑class users, alongside humans
Keep one experience together with the UI/UX product designer at the seam between UI and headless
Enable builders so API design quality does not depend on one person
What You’ll Be Doing
Own the headless experience as one product with clear ownership and a real design bar
Shorten the path from first API call to running in production
Build confidence that teams can trust the API in operation
Design for agents as first‑class users, alongside humans
Keep one experience together with the UI/UX product designer at the seam between UI and headless
Enable builders so API design quality does not depend on one person
Expected outcomes (first 6 to 12 months)
A clear definition of what "good" looks like for the headless experience, with principles and conventions that builders actually apply
Measurable progress on Time to First Production for the assigned initiatives
A well‑defined interface with the UI/UX product designer, with no breaks between UI and API experiences
Agents can discover, call, and recover from errors in our APIs and tools without human help, with a measurable agent task success rate
What You Bring
Ability and/or willingness to use our product.
Design background with real experience on API, developer, or platform products (not a pure engineer)
B2B SaaS experience, ideally in highly regulated industries
Has designed APIs, CLIs, MCP servers, or tool schemas that LLM agents consume, and knows how they fail (ambiguous errors, non‑idempotent calls, capabilities an agent cannot discover)
Hands‑on experience with agent‑first or AI‑first experiences
Ability to make abstract systems concrete, testable, and explainable
#J-18808-Ljbffr