Product Builder

Product Experience Builder

Product Dept / Full Time / Remote

Product management is changing. The most effective product people today don't just define what should be built, they build it. As AI tools collapse the distance between idea and working software, the PMs who will shape the next generation of healthcare technology are the ones who can move from discovery to prototype to shipped solution in days, not months. At Canvas, we're not waiting for that shift to happen.

We're hiring for it now.

The Product Experience Builder is a new kind of role: part product manager, part builder, entirely focused on creating plugins and capabilities that make Canvas more powerful for every customer. Where traditional PMs gather requirements and hand off to engineering, a Product Experience Builder gathers insight and then builds. They build using the Canvas's SDK, AI-assisted development tools, and whatever else it takes to get something real in front of customers fast.

The path from one customer to many is rarely a straight line. A Product Experience Builder may spend weeks forward-deployed with a single customer, building out an entire clinical workflow end-to-end — doing whatever it takes to get them live. Next month, a Product Experience Builder may build a plugin that unlocks opportunities for many customers because a new platform capability has been developed based on customer developer feedback.

The core common concept is speed of iteration: understand the pattern, ship fast for one, build it in a way that works for many.

That loop only works if the person running it has genuine product and design sense. Canvas is built from a growing collection of plugins and extensions, and without strong aesthetic and structural judgment, that kind of system can quickly become incoherent — inconsistent interaction patterns, redundant capabilities, workflows that technically function but feel disjointed to the clinicians using them. A Product Experience Builder must hold the broader design integrity of the Canvas experience in mind even when moving fast on a single customer's problem.

Systems thinking here means not just understanding how plugins compose technically, but ensuring they compose into something that feels like a unified product.

• Use Canvas's SDK, AI-assisted development tools (including Claude Code), and other modern tooling to build and ship plugins directly. While prototypes are good for feedback, success is defined by production-ready solutions
• Drive rapid iteration cycles: get real functionality in front of customers fast, learn from how it's actually used, and improve continuously
• Own the full arc from discovery to deployed plugin — you are the loop between customer insight and shipped capability
• Maintain a high throughput of working solutions; influence at Canvas is earned through demonstrated impact on outcomes, not roadmap ownership

• Design plugins that solve problems for many customers, not just one, thinking in terms of broadly applicable patterns and reusable building blocks
• Think in systems: understand how individual plugins interact with each other, how multi-plugin solutions and agent-based workflows compose into something greater, and design accordingly
• Enforce governance standards for how plugins are built, deployed, versioned, and coordinated, especially as agent-driven capabilities grow in complexity

• Work closely with Platform Engineering to identify gaps in the Canvas platform that limit what plugins can achieve and translate field observations into concrete platform requirements
• Lead efforts to deconstruct monolithic Canvas features into discrete, composable plugins enabling greater…