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.
Cloud findings arrive faster than their operating context.
Fast routing protects response time, while engineer review protects the severity decision.
Who you’d be doing this for
“My client was waiting and I was staring at a screen instead of pulling up their note.”
Lwin Kurniawan · Independent Therapist · a character in this brief
Runs a solo practice on the platform and depends on uninterrupted access to client schedules, notes, and billing.
What is at stake
Cloud findings are consuming long investigations before anyone can judge their severity. You have to decide where the route system's suggested owner and severity hand over to the security engineer who sets the severity, when a Wiz finding on AWS storage arrives.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- likely-owner paging vs. on-call interruption
- cross-system context vs. least-privilege access
- evidence depth vs. summary readability
- pilot focus vs. reusable workflow
Why Headway
Provider scheduling, clinical records, and claims workflows depend on AWS services that must remain secure and available.
Written with these in mind
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 Security Engineer (Infrastructure) (opens in a new tab)
- Build out and mature Headway's cloud security posture: Build an AI-native approach to configuration standards, hardening, and vulnerability remediation across our AWS footprint.
- Staff Infrastructure Engineer · no longer posted
- You will lead the work to isolate blast radius, make autoscaling trustworthy, and build a self-serve infrastructure platform so that the Infrastructure Engineering team focuses on the strategic and unusual, not the routine.
- Architect and own the cloud platform that every engineer at Headway deploys on.
- Senior Security Engineer (Product) · no longer posted
- Since then, we’ve grown into a diverse, national network of over 60,000 mental healthcare providers across all 50 states who run their practice on our software and have served over 1 million patients.
- Build Agentic Security Tooling: Move beyond rules-based automation to agentic workflows that address potential code problems at scale across our rapidly growing codebase.
- Senior Software Engineer (Trust Foundations) · no longer posted
- Building for trust is non‑negotiable in our mission of making mental healthcare more accessible and affordable across the US: patients share sensitive information, payers demand demonstrably strong controls, and providers depend on reliable, secure infrastructure.
- Champion operational excellence - Instrument services, tune alerting, own on‑call runbooks, and drive post‑incident hardening.
Reporting read before this brief was written
The pieces closest to the situation in this brief.
TKSoftware launched ICONIC Pro on September 14, 2026, a practice management system with its own clearinghouse, priced at $1 per claim and available to behavioral health and mental health practices.
TKSoftware Launches ICONIC Pro, Uniting Practice Management and Clearinghouse in a Single System (opens in a new tab) · tksoftwareinc.com · Sep 14, 2026
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
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.
New clinicians are missing first appointments after completing early onboarding steps.
You must decide whether AI drafts explanations from evidence or only assembles the evidence for PM review.
Virginia clinicians are unsure whether their enrollment records are complete before January 29.
You must decide which readiness signals prompt action without implying payer approval.
Clinicians are receiving lower payments while claim records still look processed.
You must choose which suspected downcodes can move automatically and which need human review.
Other problems with a similar purpose
In each of these, as in this one, the aim is to use evidence to make delivery leaner and more efficient without treating reliability as something to trade away.
Mine operations managers are waiting on fixes while reviews reopen for missing vehicle evidence.
You must decide whether AI marks uncertain evidence or holds the change for an engineer to investigate.
Worker-type concerns are appearing repeatedly across payroll API migration feedback, but their source evidence is scattered.
You must decide where the drafting of clusters from Operations and Compliance feedback stops and where a product manager's own reading of the source examples has to begin.
Daily event-air exceptions are producing conflicting explanations for the same cost and service variance.
You must decide what AI can match and draft, and what reviewers must verify before finance acts.
