Clinical Product Manager, Healthcare AI

US healthcare providers lose billions every year to denied claims, most of them traced back to documentation and coding gaps no one catches until the payer says no. Adentris is an AI revenue integrity platform that catches them first. Our AI agents read EHR and payer interfaces directly, no API integration required, across five modules: documentation, coding QA, prior authorization, appeals and denials, and discharge summaries. And for providers that don't have their own CDI or billing teams, we run billing as a service on top of the platform.

About Adentris

Adentris builds the AI platform for revenue integrity and compliance in healthcare, one of the largest and most underserved markets in the US. Hospitals, health systems, and behavioral health networks already run their documentation, coding, prior authorization, and denial workflows on our platform, and the customer list keeps growing.

The platform spans five modules (Documentation Compliance, Coding QA, Prior Authorization, Appeals & Denials, Discharge Summaries) plus a real-time documentation co-pilot that works inside any EMR. We're a small, fast-moving team: your work ships in days and shows up in customer results within weeks. Every hire at this stage changes the trajectory of the company.

The founders

You'd be working directly with all three founders. Sergey Yudovskiy (CPO), your direct manager, is a second-time YC founder: he previously ran ElectroNeek (YC W20) as CEO, scaling it to ~$5M ARR across 30+ countries, and comes from a family of physicians, which is why revenue lost to documentation errors is personal, not abstract. Dmitry Karpov (CEO) is also a second-time YC founder with a track record in B2B enterprise products; he leads executive sales, and you'll join those calls as the domain expert. Alex Odin (CTO) is a third-time founder who led AI at ManyChat ($140M+ ARR); his multi-agent architecture is what your specifications will be built on. You'll also work alongside our Clinical Advisory Board of practicing physicians and healthcare executives.

The role

You bring US healthcare domain depth into the product: clinical documentation, medical coding, billing, and compliance. Working directly with the CPO, you turn regulatory and coding reality into precise product specifications, work with engineers daily to build and validate them, and serve as the domain expert in front of customers and prospects. You are the connective tissue between what customers live with and what we ship.

Expected time split: roughly 60% product work, 40% customer-facing. This split is protected.

This is right for you if you've lived inside the US billing and compliance stack, and you want to turn that judgment into a product instead of applying it one chart at a time. It's wrong for you if you know only one of coding, billing, or compliance: this role runs on all three at once.

Your first 90 days

• First 30 days: get inside the five modules and the customers running them. Join sales and customer calls, take over the QA loop on coding and compliance accuracy for one module, and ship your first spec into engineering.
• By day 60: your first major module improvement is specified, built, and validated with you reviewing the edge cases, and you're running the daily requirements loop with engineering.
• By day 90: you're the go-to domain expert on sales calls, and the process for tracking regulatory and coding changes (CMS updates, code set revisions, enforcement trends) exists and runs because you built it.

What you'll own

• Product strategy and roadmap across the documentation, coding, prior auth, and denials modules, in direct partnership with the CPO
• Translating US compliance and coding requirements (CPT, ICD-10, HCPCS, E/M guidelines, modifiers, NCCI edits, LCDs, medical necessity, payer rules, CMS guidance) into precise, testable product specifications
• The daily engineering loop: refining requirements, validating rule logic, reviewing edge cases, and QA of the clinical and coding accuracy of what we ship
• The domain-expert seat on sales and customer calls: walking a coder, a CFO, and a compliance officer through how the product handles their real scenarios
• The feedback loop between customers, sales, and engineering, and the prioritization of domain-driven improvements
• Regulatory and coding change tracking, and the product updates those changes require

Who you are

• 6+ years in US healthcare technology: building or managing a product in RCM, medical coding, CDI, compliance, or an adjacent space
• Hands-on command of all three: coding (CPT, ICD-10, HCPCS, E/M, modifiers, NCCI edits), billing (payer adjudication, denials, medical necessity), and compliance (documentation standards, CMS guidance, payer rules)
• Experience working with engineering teams on complex rule-based or AI-driven functionality
• Real presence in front of customers: you can hold a technical compliance conversation with healthcare executives and their coding teams
• Familiarity with HIPAA

Strong signals

• AAPC or AHIMA certification (CPC, CCS, RHIA, CDIP or similar)
• Knowledge of 42 CFR Part 2 and behavioral health specifics
• Hands-on experience with EMR/EHR ecosystems: Epic, Oracle Health, athenahealth, or behavioral-health-native systems such as Kipu, Alleva, or BestNotes
• Prior work at a healthcare AI company or a billing service provider serving US clients

What success looks like

In the first two quarters: specs for at least two major module improvements shipped, with measurably better coding and compliance accuracy; you're the go-to domain expert on sales calls, and it shows in deal feedback; and a running process exists for turning regulatory and coding changes into product updates.

Details

• Full-time; hybrid in Austin.
• Competitive salary plus meaningful equity
• Healthcare and 401(k) benefits

The interesting thing about Adentris is that it's not one hard problem, it's four, and they stack on top of each other.

Reading software that was never meant to be read. Most EHRs (Epic, Oracle Health, MEDITECH, athenahealth) either don't expose an API for what we need or take the better part of a year to integrate. So our AI agents operate the interface directly, the way a person would: reading the screen, navigating the workflow, pulling what matters. That's what lets us onboard a new provider in about 30 days instead of twelve months. Getting a UI-driven agent to behave reliably across a dozen systems that all look and act differently is a genuinely hard reliability problem, and it's the foundation everything else sits on.

Processing clinical data at scale. Behind the agents we're handling data for hundreds of thousands of patients: charts, notes, coding, claims history. It has to be ingested, normalized across wildly inconsistent source systems, and made queryable fast enough to act on. This is a real data-engineering problem, not a wrapper around a model.

Evaluating it in real time against a moving rulebook. We check documentation and coding against many different rulesets at once: payer rules, coding guidelines, and regulatory constraints that change and often conflict. Doing that in real time, at the moment a claim is being built rather than weeks later, is the core of the product. We run documentation, coding QA, CDI and pre-bill checks as a single pass over the same data instead of four disconnected tools.

Doing all of it under real constraints. We work with PHI under HIPAA and 42 CFR Part 2, so data segregation, access control and security aren't features we bolt on later, they shape the architecture from the start. And because we sit directly in the claims path, our bar for accuracy and stability is closer to fintech than to typical SaaS. A wrong action isn't a bug ticket, it's someone's claim. We care a lot about correctness, observability, and systems that fail safely.

We're a small team, so you'll own real surface area and ship to live US providers, not demos.

We keep this simple and fast: you talk directly to the founders who make the decision, no recruiters and no panels.

1. Call with Sergey, CPO (45 min). Your future direct manager. Your background across coding, billing, and compliance, how you've turned domain knowledge into product before, and an honest look at where Adentris and its five modules are today.
2. Domain working session (60–90 min). A realistic scenario from our world: an anonymized clinical note and the denial that followed it. You walk us through what's wrong — the coding issue, the documentation gap, the compliance angle — and how you'd spec the fix for engineering. This is the job in miniature.
3. Call with Dmitry, CEO (45 min). The customer-facing side: how you'd walk a CFO and their coding team through a hard scenario, and how you think about the market.
4. Decision. Sergey and Dmitry decide together, typically within 72 hours of the last call. References, then a direct compensation conversation with a founder.