First-time day at Headway

Fix the scoring path without hiding genuine quality findings

Published Oct 22, 2026

You’re the ai / ml 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.

The feedback model is finding words in notes without finding the gaps those words are meant to resolve.

Prescribers need concise, credible coaching while clinical review needs genuine documentation concerns surfaced consistently.

Who you’d be doing this for

“I got three prompts about a safety plan today, and the plan was already in every note.”

Valentina Ribeiro · Psychiatric Nurse Practitioner · a character in this brief

An independent prescriber receiving real-time documentation feedback after outpatient visits.

What is at stake

Unsupported coaching prompts are appearing in prescriber notes that already contain the requested documentation. You have to weigh faster recalibration against evidence that genuine quality findings still surface.

Why it isn’t already fixed

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

  • fast correction vs. clinician-reviewed evidence
  • lower prompt volume vs. valid quality findings
  • prescriber trust vs. broad model suppression
  • release speed vs. reversible monitoring

Why Headway

Clinical documentation feedback sits directly inside the practice workflow used by independent prescribers accepting insurance.

Written with these in mind

evaluation-minded ML engineerLLM reliability builderhealthcare ML practitioner

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.

  • Senior Data Scientist (opens in a new tab)
  • Staff Software Engineer (Payer) · no longer posted
    • Measuring & Elevating Clinical Quality: Help build the systems that systematically review every prescriber in our network against clinical quality standards — so we can measure, improve, and defend the quality of care Headway delivers.
    • The stakes are real: our most recent launch reviews clinical notes and nudges providers to put a safety plan in place when a patient shows signs of suicidal risk — a system projected to save roughly 1,000 lives a year.
  • Senior Manager, Data Science - Customer Experience · no longer posted
  • Director, Data Science & Analytics · no longer posted

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 fixing one thing without breaking another.

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 make a machine-driven decision dependable and fair at the exact real-world moment a customer is counting on it.