Skip to content
Camunda

Senior Product Designer

USEASTRemote · region unclear
Senior · FullTime · Products
POSTED 3 NOVVERIFIED 3H AGO
Apply Ask
Open for
0d
since 3 Nov
H-1B · FY25
1
certified LCAs
Hiring · 30d
48
−2 net · open roles

Camunda is the enterprise platform for agentic orchestration, enabling organizations to coordinate AI agents, people, and systems across complex, end-to-end business processes. With built-in governance, auditability, and human oversight, Camunda gives enterprises the control they need to move AI from pilots to production — safely and at scale. Trusted by over 700 organizations worldwide, including 9 of top 10 US banks, Camunda helps enterprises boost operational efficiency, accelerate time-to-value, and deliver better customer experiences.

Fully remote and global, we are in the middle of something bigger: transforming into an AI-first organisation, built on our own platform. We use Agentic AI to automate, orchestrate intelligent processes, and elevate human contribution across every team.

Named GP Bullhound’s Top 100 Next Unicorn list, 2025 Great Place to Work certified. Visionary in 2025 Gartner® Magic Quadrant™ for Business Orchestration and Automation Technologies. ranked 3rd in Flexa's 2026 Most Flexible Companies, We’re growing fast and looking for top talent to join our team. If you want meaningful work, visible impact and put something genuinely rare on your CV, keep reading.

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

Source · CamundaFirst seen 3 NovOriginal ↗