The Role
Lead both product and operations: own the roadmap, operating cadence, and the loop from claims operations to engineering. Write actionable specs, run customer launches, grow the ops team, and increase automation while acting as a strategic second voice to the CEO and a customer-facing leader for health systems.
Summary Generated by Built In
Own how the company runs and how the product gets built. They're the same job here.
A federal arbitration system called Independent Dispute Resolution, or IDR, now determines billions of dollars in healthcare payments each year. Providers win the vast majority of disputes, yet most eligible claims are never filed. The process is manual, fragmented, and resource-intensive, and most providers don't have the infrastructure to pursue what they're owed.
The No Surprises Act created the framework, and the market already exists. Today it runs on spreadsheets, consultants, and static playbooks. We're building the first intelligent system designed to operate inside it.
Two things decide whether this company wins: what we build next, and how well we run the claims we already have. This role owns both.
At most companies, product and operations are separate functions that negotiate with each other. Here they're the same loop, and splitting them would break it.
The person running a claim finds the edge case. The edge case becomes a spec. The spec becomes a feature. The feature changes how the claim runs. If those are different people with different incentives, the loop slows down and the company loses its main advantage.
So you'd own both sides. You'd be close enough to the claims to know what actually breaks, and senior enough to decide what we build about it.
The other hard part is that nobody hands you the answer here. There's no roadmap to inherit, no research team, no analyst prepping a deck. You'd be building conviction about federal arbitration, a domain you probably don't know yet, fast enough to make calls with real money riding on them. Get one wrong and a provider loses what they're owed, or we pay a CMS fee on a dispute we should never have filed.
Recourse is being built in partnership with 25M Health, a healthtech venture firm. We have institutional backing, a shared platform team spanning engineering, strategy, design, and back-office, and early access to large provider systems.
We are actively filing disputes for real customers, including a large multi-facility health system and a litigation-finance partner with hundreds of millions in claim value. This is a funded, validated opportunity with real customers and real data.
We are a small, nimble team. We move quickly and we value clarity over theater. We want this to be the best work of your career. The stretch you look back on as the one where you shipped real things, with people who raised your game, on something that mattered.
We care about clear thinking, high ownership, intellectual honesty, and direct communication. We believe operations, product, and engineering should operate as one pod, not three functions. We want the machines to do machine work, and the humans to do their best work.
You'll report to the CEO and own the operating layer of the company. You will:
- Own the product roadmap and the calls about what we build next and why
- Own the operating cadence: goals, weekly rhythm, throughput and quality metrics, what gets tracked and what gets ignored
- Run the loop between claims operations and engineering, so real-world friction becomes shipped product quickly
- Write specs that get built against. Not requirements documents, specs
- Own customer launches end to end, starting with expanding our anchor health system across facilities and service lines
- Build and grow the operations team as volume increases
- Push the automation rate. Every claim handled manually is a claim the system should have handled
- Be a genuine second voice on strategy, not an executor of someone else's
You've built something before. Ideally you've founded a company, been early at one, or owned a P&L. You know what it feels like when nobody is coming to tell you what to do.
You are AI-pilled. You've used AI tools to do work that would have taken a team. You have opinions about which ones are useful and which are hype. You stay current because the world is changing and you want to see the next shift before anyone else.
You have strong operational common sense. You can walk into a messy process, figure out what actually matters, and produce a clean system. You're not precious about methodology. The goal is throughput and quality, not frameworks.
You have technical fluency. You're comfortable with data, you can query systems directly, and you can get hands on to move work forward rather than waiting for engineering cycles. You don't need to be a senior engineer. You do need to collaborate with engineers as a peer.
You have a bias to action. You don't default to no. Speed of iteration over polish of iteration. You start, you learn, you fix things in motion. Most decisions are reversible and do not need extensive study.
You are intellectually honest and curious. You seek out the things that might disconfirm your beliefs. When you don't understand something, you keep digging. When you're wrong, you say so. You use plain language. You respectfully challenge decisions you disagree with, and once a decision is made, you commit.
You put the team first. You are reliable and fully invested. You know sustainable intensity beats burnout. You take your vacations. You check on your teammates. You build a culture where people do their best work because they are supported, not squeezed.
- 6+ years spanning product and operations, or a founder background where you did both because someone had to
- A track record of designing and running workflows at scale, not just documenting them
- Meaningful technical fluency: comfort with data, analytical tools, and getting hands on
- Deep familiarity with AI tooling. You have shipped things using it, not just demoed it
- Experience writing product specs that engineers actually build against
- Comfort being customer-facing. You'll be in front of health system executives
- A preference for small teams and early-stage chaos over mature org charts
Strong plus, not required: healthcare revenue cycle, claims operations, or exposure to the No Surprises Act and IDR. Experience in regulated environments where correctness and financial impact are tightly coupled is highly valued.
Sound judgment, operational depth, and ownership mindset are required. Grit matters more than pedigree.
This is the closest thing to a co-founder seat that isn't one. You'd own the operating layer of a company with real revenue, real customers, and a market that's growing whether we participate or not.
You'd also have unusual range. Product strategy on Monday, a broken claim on Tuesday, a customer executive on Wednesday, a hiring decision on Thursday. If you like being narrow, you'd hate this. If the last few years have made you want more surface area rather than less, this is it.
If you want this to be the most memorable stretch of your career, where you shipped something real, with a team you respected, in a domain that actually matters, this is the seat. Please apply even if you don't fit 100% of these requirements. We would like to talk.
Recourse is an equal opportunity employer. We do not discriminate on the basis of race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, or any other characteristic protected by law. We believe the best teams are built from people with different backgrounds and perspectives, and we're committed to creating an environment where everyone can do their best work.
The base pay range for this role is $150,000 – $200,000 per year.
Skills Required
- 6+ years spanning product and operations or founder background
- Track record of designing and running workflows at scale
- Technical fluency: comfort querying data and using analytical tools
- Deep familiarity with AI tooling and experience shipping AI-enabled features
- Experience writing product specs that engineers build against
- Comfort being customer-facing with health system executives
- Ability to hire, build, and scale an operations team
- Strong judgment, ownership mindset, and bias to action
- Experience in healthcare revenue cycle, claims operations, No Surprises Act/IDR exposure
- Experience in regulated environments where correctness and financial impact matter
Am I A Good Fit?
Get Personalized Job Insights.
Our AI-powered fit analysis compares your resume with a job listing so you know if your skills & experience align.
Success! Refresh the page to see how your skills align with this role.
The Company
What We Do
Recourse Health builds claims-intelligence software for healthcare providers, automating the manual, resource-intensive IDR and out-of-network dispute workflows created by the No Surprises Act. The company uses AI and LLM-powered reasoning to ingest claims, package evidence, and operate end-to-end dispute workflows so providers can pursue disputed payments at scale while preserving auditability and regulatory compliance.
.jpeg)
