Staff engineer to design and own Headway's experimentation and feature flagging platform, including assignment logic, exposure tracking, and multi-sided marketplace testing capabilities.
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 ENGINEERING AT HEADWAY
Building a new mental healthcare system at Headway is only possible because of the scale and leverage that software can provide. The engineering team at Headway is a small but mighty team using technology to build that future (and have a fun time while doing it!).
ABOUT THE ROLE
We are looking for a Staff Software Engineer to own how Headway runs experiments. "Ship small, learn fast" is the second principle on the list above, and experimentation is how we actually do it: eleven teams have run hundreds of experiments deciding how patients find a therapist, how quickly new providers get up and running, whether our AI products are working, and how we collect the clinical outcomes data that proves care is effective. You will own the platform all of that runs on.
This is a hands-on technical leadership role with unusually wide reach. You will design and build the core primitives, including how users are assigned to experiments, how we record what someone actually saw, and how we recognize the same person across devices and between browsing anonymously and signing in. You will decide what our long-term experimentation and feature flagging stack should be; we run LaunchDarkly and Statsig today, and that architecture is yours to evaluate and consolidate. You will also make AI a real part of the workflow, from validating an experiment's setup before it starts to catching a broken experiment automatically instead of discovering it in a Slack thread a week later.
You will also evolve our experimentation capabilities to expand into market-based testing. Headway is a multi-sided marketplace, so we frequently need to change something for therapists and measure what happens to patients, which changes both how a test must be designed and how it can be analyzed. We need to test whole geographic markets, not just individual users. We need to hold groups out for long stretches to understand real long-term impact. These capabilities are well understood in the industry and we have not built them yet, and they are the ones our business needs next.
The job is a platform and a program in equal measure. Half of it is the technical foundation. The other half is raising how well the whole company experiments: the defaults, the review, the documentation, and the education that let a team run a trustworthy experiment without needing you in the room. You will gather needs from teams who all want something different, sequence them into a roadmap, and say no clearly, which means acting as part technical product manager for your own platform.
You will sit in the Patient org, where the highest volume of experiments happens, and serve the whole company. Trustworthy results are shared ownership. You will own assignment, exposure, and the experiment data pipelines, which are the parts of the chain that are engineering problems. You will work closely with Data Science, who own statistical methodology, and with the teams who own our event tracking and metric definitions, because a number is only as trustworthy as the weakest link in that chain.
WHO YOU ARE
We are looking for a Staff level engineer who wants their impact measured by what other teams can now do. You think in systems, you are uncomfortable with numbers you cannot explain, and you raise the bar for the people around you.
Sourced directly from the company's job board — apply on their site.