Engineering Manager

Who you are

• We're looking for engineering team leaders and people managers who are product-minded, data-informed, and drawn to systems where correctness is the product
• As an Engineering Manager in Revenue Engine, you'll work closely with Engineering Leadership, Product, Data, Operations, and Finance to shape how Headway records and moves money
• This is an exciting opportunity for a passionate, mission-aligned engineering leader to make an immediate impact at a high-growth company
• You have 3+ years of experience as an Engineering Manager, building and leading teams that delivered business outcomes through technical investment
• You have 3–5+ years of experience as a Software Engineer, with depth in backend and distributed systems: event-driven architectures, workflow orchestration, or high-reliability data pipelines
• You've led work where correctness and data integrity were non-negotiable (financial systems, payments, billing, claims, or a similarly consequential domain), including migrations you had to de-risk rather than simply schedule
• You're comfortable defining "correct" in an ambiguous domain: setting the metric, instrumenting it, and defending it as inputs, counterparties, and volume change underneath you
• You have strong prioritization and roadmap judgment, and you can sequence work for a small team against a clear metric while managing real dependencies on other teams
• You're technical enough to be a credible thought partner in a design review, and you'd rather be close to the architecture of a money-movement system than removed from it
• You've built durable partnerships with non-engineering stakeholders (operations, finance, or compliance) whose work depends on what your systems produce
• Nice to have: healthcare claims, EDI or clearinghouse experience; fintech or payments background; experience standing up observability and SLAs on a system that didn't have them; experience growing a small team into a larger one What the job involves
• We're hiring two Engineering Managers into Revenue Engine. Both roles lead a team end-to-end, and report to a leader who will give you the autonomy to run it while being a close thought partner. We're a technical engineering org: managers here lead through credibility in design reviews, not through distance from the work
• The two teams:
• Claims Platform:
• Claims Platform owns the round-trip between Headway and the payer / clearinghouse ecosystem. Outbound: reliably transmitting claims. Inbound: interpreting whatever comes back: 835 remittances, 277 claim statuses, RARC/CARC codes, rejections, and the long tail of payer responses that don't fit any of those neatly. And in between: recording the result faithfully, so that billing, collections, and the provider and patient experience all operate against the same source of truth
• Why it's interesting: durable workflow orchestration on infrastructure that moves real money, a clean financial-integrity domain, real-time payer-response processing, and a north-star metric: what fraction of appointments get a clear, conclusive payer response with a direct line to company margin
• Billing Infrastructure:
• Billing Infrastructure owns what Headway believes about an appointment's finances, and when. The billing system is a centralized platform (a suite of APIs) that acts as the conductor for Headway's financial outcomes, modeled after a real-world medical biller. It doesn't own how each responsibility is calculated; it owns orchestrating the specialists that do, in the right order, and committing the result. Two functions: compute (orchestrate patient responsibility, payer responsibility, and provider payout across the teams that own each input) and commit (write those results, and the inputs behind them, as immutable snapshots so any financial commitment is fully explainable after the fact)
• Why it's interesting: designing the state machine that decides which financial actions an appointment is eligible for and in what order; guardrail APIs that can refuse a write the domain doesn't allow yet; immutable snapshots of every input and output, so a commitment made months ago can be reconstructed and explained exactly; a shadow mode that lets other teams simulate pricing and billing logic (and compare ML models) against real data without ever committing a financial outcome; and the non-happy paths that make it real, where a refiling, a fee-schedule change, or a correction has to reopen settled state and re-settle it safely
• 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
• A core surface of Headway's financial systems: a platform other teams depend on, and a roadmap you co-own with your product partner
• Technical direction: architecture, build-vs-buy trade-offs, reliability targets, data-model decisions, and the standard the team operates to
• Correctness and operability: the metrics that define "right" for your domain, the obser