About Caret HealthCaret Health runs care coordination for rural and critical-access hospitals. Rural hospitals are accountable for value-based-care outcomes and eligible for reimbursable programs — remote patient monitoring, chronic and transitional care management, annual wellness visits, quality-gap closure, cancer navigation — that they have nobody to staff. We supply both: the platform the programs run on, and, where a customer wants it, the people who run them. That combination makes us unusual. The clinical platform is licensed and used directly by hospital care teams, and it is also the system our own staff work when we deliver programs on a customer's behalf. It carries real clinical operations across 50+ hospitals and a large rural patient panel — quality measures tracked, discharges worked against a 48-hour clock, monitoring alerts triaged, billable time documented. This role owns that platform.
The role:
You will own the Care Operations Platform: the system care teams work in every day to run every program we deliver. Patient records and statuses, protocol and tasking engines, work queues, task outcomes, the team inbox, multi-program logic, roles and access — plus the integrations that feed it. The bar is high. These are people doing clinical work under deadlines, on patients with real conditions, in organizations that are already short-staffed. A confusing screen costs time that a rural care team does not have. A broken data feed means a care gap nobody knows about. This is an execution-heavy product role with room to grow into strategy. You'll run discovery, write the specs, own the planning, run the release train for your area, and be accountable for whether what you shipped actually got adopted. You'll report to the Chief Product Officer, who currently carries this scope directly — your first job is to take it off their plate and run it better. What you'll own Platform ownership. The clinical platform end to end: roadmap, backlog, specs, and outcomes. You decide what gets built next in your area and say no to the rest, using a simple test — does it protect revenue, improve our cost-per-outcome, or advance our AI and data position? Discovery and research. Run a continuous loop with the care teams, team leads, and operations managers who use the platform. Watch the work as it actually happens and turn observations into a ranked, evidenced problem list rather than a wish list. You'll be the person who can say what actually slows a care team down, with numbers attached. Integrations. Clinical data arrives from EHRs, payer sources, monitoring devices, telephony and messaging providers, and partner platforms. You own the product side of these: what we ingest, how it maps, what happens when a field is missing or a feed goes quiet. Integrations must be seamless for the user and observable for us — a care team should never have to think about where the data came from, and we should know a pipeline is degraded before a customer tells us. Hypotheses and metrics. Every meaningful thing you ship starts as a stated hypothesis — what we believe, what we expect to change, how we'll know — and ships with success metrics defined before the build. You'll instrument the work, read the results honestly, and kill what didn't work. Our product analytics stack is already in place and under-used; you'll change that. Planning and delivery. Break quarterly direction into epics, specs, and well-written tickets. Own sprint planning and the backlog with the engineering leads. Keep cross-team dependencies visible and resolved before they become slips. Release management. Own the release train for your area: scope, readiness, regression coverage with QA, release notes, rollout, and what happens when something goes wrong. Our cycle is slower than it should be — shrinking it, safely, is one of the things we'll measure you on. Adoption. Shipping is half the job. You own whether features are actually used: rollout plans, in-product guidance, enablement materials and documentation, adoption targets per release, and follow-up on the ones that miss. A feature sitting at 11% adoption is an open problem, not a completed ticket. Practices. Help raise how the whole product function works — brief and spec templates, definition of ready and done, the decision log, the metrics review. We're building the PM layer close to from scratch, and you'll leave real fingerprints on it.
What we're looking for:- Required3–5 years as a product manager, including healthcare product experience — clinical workflow, care management, population health, digital health, RCM, or an equivalent regulated clinical domain
- Hands-on experience owning integrations with third-party systems — EHRs, clearinghouses, device or telephony vendors, data partners — and a clear point of view on what makes an integration feel seamless to the user and observable to the team running it
- A track record of shipping: features that reached production and changed a number you can name
- Experience with workflow-heavy products used by demanding daily users under time pressure
- Strong discovery instincts — you go to where the work happens rather than relying on tickets and secondhand requests
- Fluency with metrics. You can define them, instrument them, question them, and resist the pretty ones that don't drive decisions
- Excellent written communication. We run on written briefs, specs, and decisions across several time zones
- Comfort owning a release process: coordinating QA, managing scope under deadline, and being accountable when it slips
- Enough technical depth to hold a real design discussion with engineers — you don't need to code, but you do need to understand what you're asking for
- Authorized to work in the USA strong plus
- Working knowledge of quality measures and gap closure (HEDIS or similar) — specs, eligibility, evidence, measurement periods
- Familiarity with clinical coding and billing: ICD-10, CPT/HCPCS, LOINC, and the reimbursement mechanics behind remote monitoring, chronic care, transitional care, and wellness-visit programs
- Direct EHR integration experience — FHIR, HL7v2, aggregation layers, or native vendor APIsExperience with complex rules, protocol, or workflow engines
- Familiarity with product analytics tooling and SQL-level comfort with your own data
- Experience introducing product process into a team that didn't have one
- Not required
A clinical background. You'll work closely with clinicians and a clinical reviewer; you don't need to be one. Curiosity about the clinical domain matters far more than credentials in it.
Practicalities
Remote, US-based only
Reports to the CPOCompensation depends on experience and location; we're happy to discuss the range early in the process
