Headway Inc is a Ukrainian EdTech company that develops a portfolio of educational apps offering book summaries, short lessons, and cognitive-training products.
1 in 4 people in the US have a treatable mental health condition, but most providers don't accept insurance, making therapy too expensive for most people. Headway’s mission is to fix this by building a new mental healthcare system everyone can access. We started by solving the biggest barrier to care: insurance. The admin work - credentialing, claims, payment reconciliation - is a nightmare. We've automated that. But we're going further. Over 75,000 providers across all 50 states run their practice on our software, serving over 1 million patients. We are building the best tools for therapists to run their entire practice, reimagining the experience of finding a therapist, and investing in the platform foundations to enable this at scale. We aren't just a billing layer; we are becoming the platform where care actually happens. We're a Series D company with $325M+ in funding (a16z, Accel, Spark Capital, etc.), looking for exceptional people to help us achieve this mission. We want your time here to be the most meaningful experience of your career. Join us, and help change mental healthcare for the better. ABOUT THE TEAM & ROLE Mental health care shouldn't come with surprise bills, and it shouldn't cost providers sleep wondering whether they'll get paid for the work they did. At Headway, getting insurance right — reliably, accurately, and in real time — is the single most leveraged problem we solve. It's the difference between a patient who can afford their first session and one who can't; between a provider who chooses Headway and one who doesn't. We're hiring an Engineering Manager to lead the Claims Platform team inside Headway's insurance group. Claims Platform owns the round-trip between Headway and the payer / clearinghouse ecosystem: outbound claim submission, inbound response interpretation, and the structured record of the result — the "claim stack." When an upstream decision is made on what, when, and where to file or refile a claim, your team makes sure the connection works, the most useful possible response comes back cleanly from the payer or clearinghouse (e.g. Stedi), and the result is recorded faithfully — so Claims Success, Billing Infrastructure, and the appointment lifecycle all operate against the same source of truth. Your team owns the machinery that turns upstream decisions on where, when and how we file claims decisions into reliable, interpretable, recorded outcomes, measured against a clear north star: the percentage of appointments with a submittable primary claim that receive a conclusive payer response within 90 days. This is infrastructure the rest of the company runs on — and it's about to matter even more. Headway is building Project Switchboard, a single, authoritative financial state machine for every appointment. In that world, the claims lifecycle is triggered cleanly by upstream billing state, the claims state machine is the master of the claim's world, and results flow back only when appropriate. As we scale and move toward automated and agentic workflows, the reliability and correctness of the Claims Platform is what keeps money moving accurately for patients, providers, and payers. You'll lead this engineering team end-to-end, co-own the roadmap with your PM, and report to a senior manager who will give you the autonomy to run your team while being a close thought partner. We're a technical engineering org — managers here lead through credibility in design reviews and active code contributions, not through distance from the work. WHAT YOU'LL OWN An engineering team — hiring to a high bar, growing the people on it, and setting the culture your team operates by. The Claims Platform surface — a system other Headway teams depend on, and a roadmap you co-own with your product partner. That surface includes the claims lifecycle and status model, the APIs to file and refile claims, clearinghouse response processing (835 remittance parsing, 277 claim statuses, RARC/CARC handling), claims interpretation (issue types/subtypes, ERA confidence evaluation), the claim stack (claim-to-appointment aggregation, including multiple claims per appointment), and integration with invoices. Technical direction — architectural decisions, build-vs-buy trade-offs, reliability targets, and the standard the team operates to. Near-term this includes migrating ERA processing from Celery onto Temporal, defining and committing to SLAs that center on the platform's core function, improving analysis of low-confidence ERAs, auditing CPI matching logic, and guiding the deprecation of reverse ETL for secondary insurance. Cross-functional partnership — working with leaders across the insurance group (benefits, eligibility, corrections) and adjacent groups (Claims Success, Billing Infrastructure, patient billing, payer partnerships, data platform) to keep the whole system coherent — including the explicit, guardrailed handoffs Project Switchboard depends on. Operational health — incident response, on-call sustainability, and the planning rhythm that lets your team ship predictably through high-stakes moments. The failure modes here are real and expensive: when systems diverge on a claim's financial state, the result is mis-paid providers, mis-billed patients, and audit-flagging discrepancies. Your team is the one that keeps that from happening. YOU'D BE A GREAT FIT IF… You have 3–5+ years of experience as a Software Engineer and came up as a builder. You're comfortable in a design review, you read PRs when it matters, and your team trusts your technical read. You've managed engineers for 2+ years — whether as a tech lead with a handful of reports stepping into a bigger scope, or as a manager who has already run an engineering team through a scaling moment. You've built systems other teams depended on — services, APIs, pipelines, or third-party integrations — at meaningful scale. You think clearly about failure modes and treat reliability as a feature, not an