Something new at Headway

Build a shared view of payer rates without promising payment

Published Oct 22, 2026

You’re the data engineer. Your team is in the room.

The setting

is a marketplace and software platform that connects patients, health insurers and independent providers of mental health care across the United States. is the software therapists and psychiatric prescribers use to accept insurance and run their practice.

Public payer rates offer a planning signal without proving what a clinician will be paid.

Finance needs comparable rate evidence while Insurance Systems must preserve the uncertainty in quarterly public files.

Who you’d be doing this for

“I had to explain a lower payment to my accountant again, and I still don’t know if it’s a one-off.”

Dagny Nielsen · Independent Mental Health Clinician · a character in this brief

Runs a small outpatient practice and depends on reliable reimbursement to keep insurance appointments available.

What is at stake

Finance cannot reliably compare public payer rates for the same behavioral health service. You must weigh a useful planning dataset against the risk of presenting lagging public files as payment truth.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • planning visibility vs payment certainty
  • self-service analysis vs payer-rule nuance
  • quarterly source coverage vs schema stability
  • reusable models vs narrow first scope

Why Headway

Behavioral health reimbursement determines whether independent clinicians can keep accepting insurance-covered care.

Written with these in mind

data product builderplatform-minded data engineergovernance-focused infrastructure engineer

Not your kind of problem? 104 more at Headway, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Headway. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Staff Data Scientist · no longer posted
    • Data Science here is about understanding those choices: what draws a provider in, what keeps them, and what helps them grow with us.
    • The Provider group owns that relationship and the trust it depends on, because we believe a clinician who feels supported can better help their patients.
  • Staff Data Infrastructure Engineer · no longer posted
  • Senior Data Engineer (opens in a new tab)
    • We partner closely with stakeholders across the company - including Finance, Insurance Systems, Analytics, Product, and Data Science - to ensure that Headway's data platform is scalable, reliable, and secure.
    • Help shape how Headway employees interact with our data through AI-powered tools, ensuring the underlying data layer is reliable enough to power accurate, trustworthy answers
  • Senior Staff Data Scientist - Bayesian Experimentation & Causal Inference · no longer posted
    • Create a clear, shared framework that maps findings to levels of confidence (for example 1–10), where lower levels reflect correlation and early directional evidence, mid levels reflect increasingly credible causal inference, and the highest levels reflect stable, repeatable, decision-grade truths.
    • A major objective of this role is to build and institutionalize a clear map of “what we know” about patients, providers, and payers , with explicit confidence levels that tie directly to business action.
  • Senior Data Infrastructure Engineer · no longer posted
    • The Data Platform team at Headway is a small but mighty team building our Snowflake data platform, data ingestion tooling, AWS infrastructure, CI/CD, and data developer experience to help Headway deliver best-in-class experience for our patients and therapists.
    • Headway is building a new mental healthcare system that everyone can access by making it easy for therapists to accept insurance and scale their practice.

Reporting read before this brief was written

The pieces closest to the situation in this brief.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on moving faster inside a system others depend on.

The same setting, from another role

Each is set around Headway’s Headway for Providers, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to engineer data foundations precise enough that the evidence they produce stays credible long after the system changes.