Who we are:

Third Way Health helps medical practices across the United States improve the patient experience while reducing the administrative burden on practice owners. We enable practices to enhance the experience of their patients by providing them with a leading service automation platform and a world class team of service representatives. What unites us is our passion to support physicians and provide better access for patients from all backgrounds.

About the Position:

Every day, our platform schedules appointments, handles inbound and outbound patient calls, verifies insurance eligibility, and moves about a quarter million records through integration pipelines with EHR systems.

At that volume, the details that matter are small ones. A payer changes the shape of a response. A sync quality flag grows from 0.01% to 0.02%. Numbers that read like rounding errors are thousands of patient appointments.

This role exists to work at that level of detail. You will learn how our workflows behave, notice what does not fit, explain why, and drive the fix.

The analysis is not the deliverable. You will look for problems without being assigned them, form a view on the cause, and either fix it yourself or hand a developer a diagnosis clear enough to act on.

Key Responsibilities:

• Finding what is not obvious. Our workflows produce a lot of operational data: scheduling volumes, call outcomes, eligibility responses, sync logs, error codes. You will learn what healthy looks like across workflows, customers, and payers. That is what lets you notice the small deviation nobody is watching for yet.
• Data integrity end to end. You will learn the full path a record travels between systems, and the points where it could drift, duplicate, or drop. When something does go wrong, you trace it to the origin rather than to the nearest plausible suspect.
• Opinionated production monitoring. You will own the library of known failure modes: what each one means, how to diagnose it, and where it escalates. You use that knowledge to sharpen what we monitor and what deserves an alert. Each new pattern you find makes the net tighter.
• Fixes that stick. For each issue, you explain what happened, when it started, what changed, and what the fix should be. You stay with it until it is resolved. Then you write it up for the teams closest to the workflow, so the same issue does not come back to you.

Qualifications:

• Problem obsession and ownership. You cannot leave an unexplained result alone. You dig in and drive it to a resolution without being asked, and without waiting for a playbook that may not exist yet.
• Systems thinker and investigator. You ask how things connect, where they break, and what goes wrong downstream. Then you stay in the logs, exports, notebooks, and config screens until you have an answer rather than a guess.
• Scripting and data fluency. You write scripts, work in notebooks, and query data to inspect, validate, and correct records. Python and SQL are preferred. You can also read an API field mapping, see what it does, and see where it could fail, without writing the code underneath.
• Clear communicator. You explain a technical problem to a non-technical colleague without losing the detail that matters. Fluent English is required.
• HIPAA awareness. You know what PHI is, how to handle it, and why it matters in every system you touch.

Nice to Have:

• Prior experience with healthcare and EHRs
• Familiarity with FHIR R4 or HL7 v2 data formats
• Background in healthcare data, operations, or implementation
• Familiarity with CRM or health record platforms at the data or admin layer, especially Salesforce
• Exposure to MuleSoft or similar integration middleware
• Experience building dashboards, reports, or monitoring for operational teams
• An interest in product ownership. Many people who do well in this role want to own a user experience end to end later in their career