Product Manager, Revenue Cycle

What You'll Do

• Own the revenue cycle product across our primary markets: Australia, the UK, and the US.
• Decide what we build, what we don't, and what we sequence next across the clinical coding engine, the coder seat, and the EHR connections that close the loop from documentation to funded claim.
• Forward-deployed: go on-site at health systems, watch coders work their queues across fragmented systems, and come back with a scoped pilot, a clear done-state (accuracy and throughput targets, the workflow being replaced, the date you finish), and a prototype.
• Make ROI legible end-to-end: build the financial model for every engagement, communicate it in language a CFO will sign off on, and bake the proof points into the product itself so every deployment shows its own value.
• Own coding accuracy as a product metric: define what accuracy means (against coder ground truth, auditor review, or CMS standard), build the evaluation infrastructure to measure it, decide where the human-in-the-loop earns its place, and ship fixes with before/after evidence.
• Sit with the clinicians upstream: shape the CDI queries, documentation prompts, and point-of-care nudges that turn a good visit into a codable one before the coder ever opens the queue.
• Navigate AI resistance in coding departments: from the coder who does not want to be replaced to the IT team with six months of procurement ahead of them, find the path through.
• Partner with engineering on the connection and evaluation layer: code mapping, workflow orchestration, and the accuracy framework each health system deployment relies on.
• Shape the commercial posture for revenue cycle: pricing structure, the proof points that support enterprise deals, the outcome metrics that make renewal straightforward, and the case studies, ROI narratives, and sales enablement that Marketing, Sales, and Solutions Engineering need to close.
• Be the connective tissue across functions: weekly with Sales and Solutions Engineering on live deals, Customer Success on deployed accounts, Engineering on what ships next, and Marketing on what the market hears.

What You'll Need

• 5+ years shipping product in healthcare: selling to or building for health systems, not adjacent to them. We care more about what you've deployed than years on the clock.
• Working fluency in revenue cycle: ICD-10, DRG assignment, HCC capture, E&M levelling. You should not need to be taught the workflow you are building for.
• ROI-first thinking: you start with the financial model and work backwards. You can build a health system's business case without a commercial analyst.
• Passion for AI, shown through hands-on building, prototyping, or side projects.
• Fluency with core LLM concepts and systems (prompting, fine-tuning, embeddings, retrieval, evaluation) and the judgment to translate these into reliable, user-facing products.
• Strong opinions, weakly held; you'll shift the room when you're right.
• Data fluency with diagnostic teeth: you can look at a coding accuracy report, identify where the model is failing, and specify what needs to change.
• -igh tolerance for 0-to-1 ambiguity: this product is at discovery and prototype stage. You will help decide what it becomes.