Trigger
Design Director, Provider Experience posted on Ashby, June 4, 2026. 29 days old. Confidence: high this is live and active.
Window
You're in the best part of the cycle. At 29 days, the initial resume flood has been screened and the committee has calibrated on what they actually need. The July 4 weekend compresses everything: decision-makers come back Tuesday to shorter inboxes and sharper priorities. H2 headcount unlocks across the industry mid-July, which means budget for this role is either confirmed or about to be.
The quieter inbox works in your favor. If this posting is still live at 45 days without reposting or language changes, the search may be stalling. Monitor around July 19; if nothing has changed by then, the window has degraded.
What this trigger probably means for the design org
Headway's EHR expansion (September 2025) turned the provider platform from a billing-and-scheduling tool into an AI-assisted clinical operating system: transcript-powered progress notes, integrated telehealth, insurance-native documentation. Every AI output on that surface carries direct clinical and financial consequence for the provider who signs it. A wrong note is a compliance event. Headway says explicitly that AI-assisted notes are "compliant, clawback-protected, and insurance-ready," which tells you the company already understands the consequence layer. They need someone who can design for it.
The posting's explicit requirement for AI tooling fluency — Claude, Cursor, MagicPatterns — tells you this team builds with AI as a core material. Reasoning from pattern: this role exists because the provider experience just became dramatically more complex, and the design problem is consequence-aware trust calibration at every AI-generated output.
Your angle
Lead with Thermo Fisher. The match is structural. Thermo Fisher's entire value was exception-first design in a regulated multi-stakeholder operation: 197 orders on screen, surface the 3 that matter, catch the deviation at the batch kanban stage instead of the delivery gate where it costs 3–5× more to fix. $20M+ margin recovered, 6 pharma partners, 100% adoption, 12 months 0→1.
Headway's provider needs the same architecture applied to clinical workflows. AI drafts a note, flags an insurance issue, suggests a scheduling change. The provider needs to see the exception. Same design problem wearing different domain clothes.
Bridge to the Trust essay. "Trust Is the New Interface" gives you the calibration framework (Watch → Verify → Delegate) that maps directly to a provider deciding whether to accept an AI-drafted progress note. One confident wrong note does more reputational and financial damage than ten correct ones repair. That line will land with anyone building AI-assisted clinical tools.
Agentic Labs handles the tooling fluency question silently. Brand Pulse, Retail Velocity, Carrier IQ are live and solo-built. They demonstrate the Claude/Cursor workflow the posting asks for without you needing to claim it.
Secondary if needed: Allē's dual-surface model (consumer + provider backoffice) maps to Headway's two-sided platform, but keep Thermo Fisher in front. This role centers on the provider operating system.
Who to contact
Name: Jake Poses, Vice President of Product, Headway. Approximately 15 months in seat. Per Headway's leadership announcement (March 2025), he oversees product, product design, and product marketing. Confidence moderate-high he owns this hire. The posting doesn't name a hiring manager, but the org structure points here.
Public fingerprint: Jake posted on LinkedIn on June 29 asking for introductions to customer-support PMs and product leaders. He frames customer support as "increasingly becoming a product" and says Headway is investing in PM to support patients and providers. Four days ago. That's your hook. His older writing (2017 hiring-mistakes piece, 2016 Thumbtack retrospective) shows a product-building and hiring-philosophy orientation but isn't recent enough to lead with. No public posts from Jake specifically about design leadership or AI in clinical workflows.
Warm intro path: Headway's investors include a16z, Accel, Spark Capital, Thrive Capital, and GV. Spark's Will Reed sits on the board. Accel's Amit Kumar has been involved since seed. No public overlap found with BCG DV or Alibaba networks. Check your a16z and Accel connections first. If none surface, this is cold.
Channel: LinkedIn cold DM calibrated to his June 29 post. If you find a warm path through a16z or Accel, switch to the warm message below.
Outreach messages
Warm message (assumes mutual connection):
Hi Jake — [Name] suggested I reach out. Your framing of support-as-product resonated because I spent 12 months building exactly that kind of operational-workflow-turned-product-surface at Thermo Fisher, where the design challenge was making exceptions visible before they became costly failures in a regulated pharma supply chain ($20M+ margin recovered, 100% partner adoption). I've been building and writing about how that same exception-first pattern applies to AI-assisted clinical workflows — my essay "Trust Is the New Interface" lays out the calibration framework for when users should trust, verify, or override AI outputs. I'd love to talk about the Provider Experience Director role and how I think about designing for consequence-aware AI systems. Would you have 20 minutes next week?
Cold message:
Hi Jake — your June 29 post about customer support becoming a product caught my attention because it maps to a problem I've shipped against: turning operational workflows into product surfaces in regulated environments. At Thermo Fisher, I designed an exception-first supply chain platform for pharma partners where catching a deviation early saved 3–5× versus catching it at the delivery gate, recovering $20M+ in margin across 6 partners in 12 months. I see the same design architecture in Headway's AI-assisted provider workflows, where the provider needs to know which AI output to trust and which to intervene on. I published a framework for exactly this — "Trust Is the New Interface" — and would love to discuss the Provider Experience Director role. Open to a brief conversation next week?
What not to say:
- Do not frame this as a patient-experience play. The posting is about the provider operating system. Leading with consumer health thinking signals you didn't read the role.
- Do not question whether design has a seat at the table in outreach. Headway puts product design under the VP Product. That structure is deliberate. Challenging it in a DM tells them you're evaluating a decision they've already made. Assessing design's real influence matters, but save it for the interview. (See Warning signs below.)
The non-obvious thing
Headway's Ashby board currently lists five design roles: this Provider Experience Director, a Design Director for Core Insurance & Design Systems that has been posted since October 2025 (nine months), plus Staff and Senior Product Designer roles across Group Practices, New Channels, and Provider Onboarding.
The Provider Experience posting uses explicit speed, consequence, and AI language. The Core Insurance posting uses none of it. Same company, completely different design profiles across roles. A nine-month-old director search running alongside a fresh one means either the design org is expanding rapidly across verticals, or the Core Insurance search failed and the committee learned something from that failure that shaped this posting's language. Both readings are useful.
Ask about the Core Insurance role in your first conversation. If it failed, the answer reveals what the committee actually evaluates. If it's paused, the answer reveals prioritization. Either way, you learn something no other candidate will think to ask.
Warning signs
Headway's culture principles emphasize speed ("Better, Faster, Fewer") and conviction-flexibility ("Strong Belief, Weakly Held"). No independent employee-review pattern was accessible to validate whether design has real organizational influence or is structurally subordinate to product and engineering. The absence of a dedicated design executive in Headway's public leadership structure is worth noting, though it may simply reflect the company's stage. It does mean the Design Director will need to advocate for design quality within a product-led org rather than from an independent seat. If that dynamic drains you, probe it in the first conversation before investing further. Once you're in the room, ask directly how design decisions escalate when they conflict with product or engineering timelines. The answer will tell you more than any job posting can.
- Headway's integrated care pipeline: Their May 2025 announcement that physicians can refer patients through existing EHRs in under two minutes, with closed-loop status updates back to referring clinicians, adds a multi-stakeholder coordination layer to the provider experience that could expand this role's scope.
- Gusto's AI-failure language as prep material: Gusto's Senior Staff Service Designer posting explicitly names AI error handling, escalation ownership, and "what happens if this breaks?" as design problems, which is the sharpest public articulation of the same consequence-aware handoff challenge Headway faces and useful vocabulary for your interview.
- Ramp's parallel Director search: Ramp posted a Director, Product Design role on June 8 with AI-native design-org language around agents, memory, and shipping PRs, but the lead narrative there is financial velocity, not clinical consequence — a completely different angle from your Headway positioning.
- The stale Core Insurance posting: Headway's Design Director, Core Insurance & Design Systems has been listed since October 2025 with no AI or speed language, and checking whether it has been reposted or revised by mid-July will tell you whether the design org is scaling or struggling to close.