Principal Product Manager

Who you are

• Builds the first version. You will show us something you built, not something you managed, this is evaluated in the interview
• AI native at product depth. You can reason at a low level about the AI products you intend to ship: context and grounding, evals and quality gates, agent behavior, and cost. Using chat tools to work faster is the baseline everywhere, so it earns nothing here
• Comfortable inside customer environments and contracting cycles, with the judgment to commit responsibly in real time
• Zero to one at Principal scope. 10+ years in product, including at least one product you conceived and shipped that earns real revenue today. We will ask what existed before it, and what was retired to make room for it
• Excellent written communication. Your reasoning gets adopted because it is clear
• Healthcare or regulated data experience (claims, EHR, patient journeys, provider analytics), or a track record of getting fluent fast in a comparably complex data domain like supply chain, energy, or financial data. Time at a company through a platform transition. Experience retiring a product without losing its customers
• Experience interacting with, managing, or building with AI agentic workflows

What the job involves

• Our flagship product Navigator runs investigations that used to take a person weeks, and an ai-augmented product suite interoperates with it to streamline workflows. We are just getting started. What the next generation of the suite actually is remains an open question, and today it needs ownership
• That question is this seat. You will define the next generation of Komodo’s product suite and prove it by building it. The current surfaces are your material and your distribution. The mandate is what comes after them
• Principal here means your answer sets the pattern for every surface that follows. This is a hands-on individual contributor role. You will lead through your thesis and your builds, embedded in small engineering pods, not through a team of direct reports
• Looking back on your first 12 months at Komodo Health, you will have…
• Put a thesis on record for what the next generation of the suite is, argued in working software customers have touched, and won cross-functional and leadership support for it
• Built the first version of at least two new products from that thesis yourself, then ran a pod of four or fewer from prototype to GA with no dedicated project management
• Those products live in customer environments, with measurable revenue, adoption, or retention impact
• Made the current suite smaller. At least one existing legacy solution retired or folded into its successor, without customer churn
• You will accomplish these outcomes through the following responsibilities:
• Own the thesis for what customers touch. Study how they actually work, decide what should exist, and revise the argument as models improve
• Build first versions with AI tools and platform primitives. Bring engineering in to scale what shows value, and drop what does not
• Work inside customer environments when the problem calls for it, scope in real time while contracts are being negotiated, and treat deployment as part of the product
• Propose and defend the shape of the growing portfolio. As the new generation lands, you decide what the existing solutions become
• Package for the field. Partner with sales and marketing on what we sell, run the market analysis behind it, and make sure every new product can be positioned, enabled, and sold
• Set the pattern. Your architecture and your build habits become how the surface pods around you work