Senior Product Manager, Command Centers

On-site | Vancouver Office – 675 W Hastings St.

Our mission is to amplify human success with AI automation.

In a dental lab, that means technicians spend less time on repetitive casework and more on the complex cases that need real skill, and labs take on volume they used to turn away. We automate the parts of the job nobody wants. 

Our vision is to become the operating system of the dental industry. Not a tool a lab logs into. The system a lab runs on.

A dental lab loses hours every week to a question that shouldn't need asking: where is that case? Orders arrive from a dozen different manufacturer portals, and chasing them down has always been somebody's job.

The Command Center ends that. It gives a lab full visibility of every case — what arrived, what stage it's at, what's stuck and why — updating continuously, in one place. Your job is to build the next generation of it around the way a lab actually works.

• 300 people. Two hubs: Vancouver HQ and Manila operations.
• 145% year-over-year SaaS growth.
• 28 countries. One platform. The dental industry's operating system.
• An in-house AI model research and development team building proprietary intelligence.

A lab isn't one job. It's designers, technicians, quality control, case managers, shipping, the owner — each with a different week and a different definition of what matters today. Full visibility means something different to each of them. The next generation of Command Centers has to be built around how those roles actually work. No written definition exists yet of what the next version of the Command Center must contain, what's optional, or what disqualifies one from shipping.

You write that definition, and you write it from inside dental labs. Then you hold it, while everything else gets built against it.

• Build from what you see: You'll be in dental labs - interviewing and standing next to the end users while they work. We know these workflows, 2,000+ lab customers. What no one has at the fidelity a per-role surface needs is the detail: a designer's week is not an operations manager's, and full visibility means something different to each of them.  
• Define the Command Center spec. What every Command Center must contain, what's optional, what stops one shipping. 
• Own the failure states. A lab can only promise a date if we know the case is actually moving. Automation can stop without announcing it. Staleness and last-successful-sync, exception queues, splitting failures by cause, confidence thresholds, when a case routes to a person and how — all of it exists so the date we gave a lab stays true, or so they hear about it early enough to act.
• Get the measurement live. The number this role is measured on is Weekly Active Role-Fit: the share of the lab roles a Command Center is built for who open it in a normal week. The bar is 80% on pilots. Building the tracking is on you, and baselines get captured before launch, not after.
• Document the decisions. The problem statement, the acceptance criteria, what was decided and why.

• A seat where AI model decisions and product decisions meet.
• Direct customer access across 2,000+ labs — the feedback loop is fast, the stakes are real, and user research here isn't a quarterly exercise.
• A category-defining problem in a $40B industry where the incumbent software hasn't been rebuilt in a generation.
• Production AI tooling from day one: Claude, Cursor, and LLM-powered workflows built in-house — not a sandbox, not a pilot.
• Competitive compensation with salary range disclosed at offer.

We ship before we're 100% certain. We write things down because we have two offices and memory is lossy. We debate loudly and move without resentment. We treat the customer's real problem as more important than an elegant internal process. If you've spent time waiting for permission to try something obvious — you'll notice the difference here immediately.

• 6+ years in product, in B2B SaaS — workflow, automation, or platform. And you've been accountable for something working in production. Maybe you were an engineer before product. Maybe engineers reported to you. Maybe you still write code. Maybe you owned the integrations or the automations and yours was the phone that rang when they broke. 
• You've shipped an AI or automation product to production and can describe what you did about the cases it got wrong — thresholds, fallbacks, what got routed to a human and when.
• You've owned a product surface end to end, discovery through ship, with a named outcome.
• You've measured whether people kept using what you built — retention, weekly actives, adoption by user type. Not launch counts.
• You've done customer discovery in person, in the place the work happens.
• Dental, CAD or manufacturing workflow experience is a plus, not a requirement.

Apply today @ EviSmart Careers