Product Experience Builder

Canvas Medical•San Francisco, CA

1d•Remote

About The Position

Canvas Medical, established in 2015, is the EMR company accelerating everyday medicine at the speed of science. Canvas helps customers optimize the clinician experience using its unified architecture and developer tools - enabling optimized workflows, connected patient experiences, and integrated healthcare data. Canvas works with customers across all care models and verticals, from direct-to-consumer virtual care to at-risk complex care and everything in between. 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 one 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.

Requirements

Experience in product management, solutions engineering, or a hybrid technical role — with a track record that includes shipping solutions, not just designing or coordinating them
Demonstrated ability to use modern AI-assisted development tools (Claude Code, Replit, Cursor, or similar) to build functional software independently
Ability to tackle complex problems and deal with ambiguity. When others struggle knowing where or how to start, you are able to use your first principles thinking skills to make forward progress
Systems thinker in two dimensions: you understand how components interact technically (composability, dependencies, governance) and how they interact experientially (consistency, coherence, the feel of the whole). You are able to hold both simultaneously and balance the tension that may exist
Strong product and design sense: you have taste. You know the difference between a technically correct solution and a genuinely good one, and you stay alert to the way a growing plugin ecosystem can quietly drift into an incoherent experience if nobody is watching
Rapid iteration instinct: you believe the fastest way to learn is to build something real and put it in front of users, and your default mode is shipping, but you iterate with an eye toward what scales beyond the customer in front of you
Comfortable operating across technical and non-technical audiences. You can write a plugin spec for a coding agent, explain it to a clinician, and whiteboard the architecture with an engineer
Collaborative by nature: knows that building the right thing requires listening to Support, Implementation, Sales, and Customer Experience, not just forming opinions independently
Healthcare technology background preferred, with understanding of clinical workflows and the operational realities of care delivery

Nice To Haves

Hands-on experience with Python or similar languages
Familiarity with FHIR or clinical data standards
Experience building on top of EMR or health tech platforms
Background in designing agent-based or multi-step automation workflows

Responsibilities

Build, Ship, and Iterate: 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
Build the Plugin Ecosystem: 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
Drive Platform Evolution: 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 flexibility and configurability than currently sits inside the core product
Prioritize platform investments by understanding which capabilities would unlock the most leverage across the customer base
Bring a first-principles perspective to what Canvas's extensibility layer should look like in 1, 2, and 5 years
Partner Across Customer-Facing Teams: Work with Support, Implementation, Sales, and Customer Experience to understand where customers are struggling, what they're asking for, and what patterns exist across accounts
Translate those signals into a prioritized view of what the plugin ecosystem most needs, balancing quick wins with foundational capabilities
Share early builds and prototypes with customer-facing teams to validate direction before investing in polish
Act as the connective tissue between what customers experience in the field and what gets built into the wider plugin catalog
Shape Product Vision: Develop a point of view on where the Canvas plugin ecosystem should go: what capabilities are missing, what interactions are underserved, and what new workflows become possible with the right building blocks
Contribute to Canvas's public-facing developer experience: documentation, guides/ examples, and patterns that help customers and partners build on Canvas more effectively
Partner with product leadership to align the plugin roadmap with Canvas's long-term platform strategy