--- title: 'Engineer, Data & Integrations at recoursehealth.com' canonical: 'https://feeny.ai/job/engineer-data-integrations-recoursehealth-com-san-francisco-qfbcxyhjpmcz' type: 'job' last_seen: '2026-09-12' --- # Engineer, Data & Integrations at recoursehealth.com - **Company:** recoursehealth.com - **Location:** San Francisco, CA - **Compensation:** $160k–$190k - **Employment:** full-time - **Work type:** onsite - **Posted:** 2026-07-29 - **Last confirmed live:** 2026-09-12 - **Apply:** https://jobs.gem.com/recoursehealth-com/am9icG9zdDo3VeSLSRLlVb4Zdu9kapfI ## Job description Healthcare data arrives as faxed PDFs and thirty-year-old EDI formats. Make it usable. ## Why This Exists 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. Everything we do starts with data we don't control. A health system sends us 835 remittance files, 837 claim files, and explanation-of-benefits documents. If we can't reliably turn that into structured, trustworthy records, nothing downstream works. ## Why This Is Hard (and Interesting) Healthcare data is genuinely, memorably bad. An EOB arrives as a scanned PDF at fax resolution. Each payer formats theirs differently, so Cigna's table layout has nothing in common with United's. A single claim gets split across CPT codes in ways that only make sense if you know the payer's internal logic. Some of our customers have six separate legacy systems that reports have to be pulled from, none of which have an API. Then there's the standards layer. 835 and 837 files follow the EDI spec, mostly. The parts where they don't are where the interesting bugs live. The prize for solving this is large. Reliable ingestion is the thing that lets everything else scale, and almost nobody in this market has done it well. ## Who We Are 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. ## The Role You'll own how data gets into Recourse and stays trustworthy once it's there. You will: - Build and maintain the ingestion pipeline for 835 and 837 files across every customer format we encounter - Own document parsing: OCR on scanned EOBs, LLM-assisted extraction, and the consistency guarantees that make it reliable - Build integrations with customer systems, SFTP endpoints, clearinghouses, and eligibility services - Design the data model that everything downstream depends on - Build the validation and reconciliation layer that catches bad data before it reaches a claim - Solve the "same document, two different answers" problem, which is the hardest reliability issue we have - Partner with operations to understand what real-world data actually looks like, not what the spec says it should look like We build with Claude Code daily and run a Codex review pass on every slice. The stack is TypeScript, Next.js, Prisma, and PostgreSQL on Google Cloud, with LLM reasoning throughout. ## Who You Are You like the unglamorous problems. Parsers, pipelines, edge cases, and reconciliation. The stuff that never demos well but decides whether the company works. You are AI-pilled. You've used LLMs for real extraction and parsing work and you know where they help and where they hallucinate. You have opinions about which tools are useful and which are hype. You are rigorous about correctness. Determinism matters here. If a pipeline gives different answers on different runs, that's a bug you take personally. 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. You ask questions when you don't understand something. You say so when you're wrong. 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 take your vacations. You check on your teammates. You help build a culture where people do their best work because they are supported, not squeezed. ## What You Bring - 4+ years building data pipelines, integrations, or backend systems in production - Strong SQL and data modeling instincts - Experience with messy real-world data: parsing, extraction, validation, reconciliation - Comfort with TypeScript or Python. The specific stack matters less than the ability to pick things up - Hands-on experience using LLMs for structured extraction from unstructured sources - Experience building in regulated or security-sensitive environments (HIPAA, SOC 2, PCI, financial controls) is a plus - A preference for small teams and early-stage chaos over mature org charts Strong plus, not required: healthcare data specifically. EDI, X12, 835/837, HL7, FHIR, clearinghouses, or revenue cycle systems. If you have it, you'll move faster. If you don't, we'll teach you. Sound judgment, technical depth, and ownership mindset are required. Grit matters more than pedigree. ## Why This Role Data quality is the constraint on this entire business. Solve it well and every other part of the company gets faster. That's a rare position to be in as an engineer. You'll also build expertise in a genuinely scarce area. Healthcare data engineering is unglamorous, hard, and in permanent demand. The people who are good at it never struggle to find interesting work. 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. ## Equal Opportunity 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. ## About recoursehealth.com ## Company Overview - **One-liner**: Recourse Health provides an AI-powered claims-intelligence platform that automates the end-to-end federal Independent Dispute Resolution (IDR) process for healthcare providers, optimizing disputes for dollars recovered rather than win rate. - **Entity Type**: Private (Seed stage) - **Headquarters**: San Francisco, California, USA - **Founded**: 2026 - **Founders**: David Hegarty (CEO & Founder) ## Core Business - Primary industry/industries: Healthcare Technology (Healthcare IT), Claims Management, Revenue Cycle Management - Target customers: Healthcare providers (physician groups, hospitals), particularly those navigating the federal IDR process created by the No Surprises Act (B2B). - Mission or purpose statement: To run federal IDR for physician groups and optimize every filing for dollars recovered, lowering the filing threshold and maximizing recovery per claim. ## Products & Services - **Recourse Claims Intelligence Platform**: A SaaS platform that uses AI and large language models (LLMs) to automate the entire IDR workflow. It ingests standard 837/835 claims data, confirms eligibility, maps deadlines, and prioritizes disputes with the highest recovery potential. - **Claims Intelligence**: An AI-powered module that analyzes claims and remittance data to guide the offer and supporting evidence for each dispute. - **Submission Intelligence**: An automated module that assembles the evidence package, addresses statutory factors, and files the complete IDR submission on time. - **Recovery Intelligence**: A dashboard for tracking every active dispute, dollar at stake, and recovery outcome, with the system learning from each result. - **CMS Filing Benchmark**: A free service that reviews a provider's public CMS filing record and compares their performance against 632 high-volume filers. ## Market Standing - **Valuation/Market Cap**: Not publicly disclosed. - **Key Metric**: The company is venture-backed, having raised a **Seed VC** round. Lead investor is **25Madison**. - **Notable Investors/Partners**: **25Madison** (lead investor). - **Growth Signals**: A very early-stage startup (founded in 2026) that has already secured venture funding and launched a live product. The company is addressing a specific, high-stakes pain point created by a federal regulation (No Surprises Act), with a clear value proposition tied to recovery dollars. The CEO has a strong background, having previously founded Nutshell Labs and held roles at Credit Karma, Opendoor, and Microsoft. ## Competitive Advantages - **Outcome-Focused Approach**: The company explicitly differentiates itself from competitors by optimizing for "dollars recovered" rather than the industry-standard metric of "win rate." They claim that across 5.7 million decided claim lines, the highest-win-rate filers recover the least money per dollar offered. - **End-to-End Automation**: Recourse automates the entire IDR lifecycle, from eligibility finding to submission and tracking, which they claim makes smaller claims economical to pursue. - **Low-Friction Integration**: The platform works from existing 837 and 835 files that providers already produce, requiring no new system of record. - **Contingency-Based Pricing**: The company's compensation comes only from the recovery they create, aligning their incentives directly with the client's financial outcomes. - **AI/LLM Powered Reasoning**: Uses advanced reasoning to strengthen the "ask" and the evidence behind it, providing auditability and compliance. ## Strategic Focus - **Scaling Engineer & Growth Team**: The company is actively hiring for roles like **Engineer, Claims Platform** and **Growth Analyst, Market Intelligence**, indicating a dual focus on product development and market expansion. - **Expanding Claim Coverage**: The first lever of their strategy is to lower the filing threshold, allowing providers to pursue a larger pool of eligible claims. - **Increasing Recovery per Claim**: The second lever is to strengthen the filing strategy to increase the value of each completed dispute. ## Why Work Here - **Early-Stage Impact**: As a seed-stage startup founded in 2026 with 1-10 employees, new hires will have a massive impact on the product, culture, and direction of the company. You work directly with the founder. - **High-Stakes Problem**: The work directly addresses a complex, federally-mandated process (the No Surprises Act), helping healthcare providers recover millions in disputed payments. The work is meaningful and quantifiable. - **Remote-First Culture**: The company operates with a remote workspace, though there is a presence in San Francisco, CA. The careers page lists roles as "In-Office or Remote," suggesting flexibility. - **Strong Founder**: David Hegarty (CEO & Founder) has a proven track record with experience at Credit Karma, Opendoor, and Microsoft, and is currently the sole executive. Working here means learning directly from a seasoned founder. - **Technology Stack**: The company is building with AI and LLMs, offering a modern and challenging technical environment. - **Perks**: Specific perks are not listed, but as a VC-backed startup, standard benefits (equity, health, etc.) are likely. ## Sources 1. [recoursehealth.com](https://www.recoursehealth.com/) 2. [builtin.com](https://builtin.com/company/recourse-health) 3. [cbinsights.com](https://www.cbinsights.com/company/recourse-health) 4. [linkedin.com](https://linkedin.com/company/recoursehealth) 5. [cbinsights.com (People)](https://www.cbinsights.com/company/recourse-health/people) 6. [gem.com (Careers Page)](https://jobs.gem.com/recoursehealth-com) ## Other roles at recoursehealth.com - [Growth Analyst, Market Intelligence](https://feeny.ai/job/growth-analyst-market-intelligence-recoursehealth-com-san-francisco-jz277amebapb) — San Francisco, CA - [Growth Lead, Provider Pipeline](https://feeny.ai/job/growth-lead-provider-pipeline-recoursehealth-com-san-francisco-j0j55205305g) — San Francisco, CA - [Provider Partnerships Lead](https://feeny.ai/job/provider-partnerships-lead-recoursehealth-com-san-francisco-zsf84430pc6s) — San Francisco, CA - [AI Engineer, Decision Intelligence](https://feeny.ai/job/ai-engineer-decision-intelligence-recoursehealth-com-san-francisco-6665xenhts39) — San Francisco, CA - [Lead, State Arbitration](https://feeny.ai/job/lead-state-arbitration-recoursehealth-com-san-francisco-hpbhhjqy1jfv) — San Francisco, CA - [Analyst, Payer Strategy](https://feeny.ai/job/analyst-payer-strategy-recoursehealth-com-san-francisco-p0z3wc7b3zyk) — San Francisco, CA - [Head of Product](https://feeny.ai/job/head-of-product-recoursehealth-com-san-francisco-dc7q6p07aj30) — San Francisco, CA - [IDR Analyst](https://feeny.ai/job/idr-analyst-recoursehealth-com-san-francisco-4qtnc9hkfwfm) — San Francisco, CA - [Engineer, Claims Platform](https://feeny.ai/job/engineer-claims-platform-recoursehealth-com-san-francisco-tjmz9sxpfc1w) — San Francisco, CA