Five live roles. Five different people across the table. Your portfolio is the same in each room. Your presentation should not be.
These five surfaced in the current pulse check as the highest-signal openings across your target list. Each one represents a distinct buyer archetype. The framework below replaces abstract tier logic with named rooms so you load the right version of your story before you walk in.
The July 4th weekend kills Thursday afternoon through Monday. If you're reaching out to any of these five, send by Wednesday. A message that lands in a holiday inbox loses its signal.
Quick-Reference Matrix
| Room | Lead Pillar | Supporting Pillar | Hold in Reserve |
|---|---|---|---|
| Suno — Head of Product Design | Agentic AI: Trust Is the New Interface essay → Brand Pulse live proof | Alibaba enterprise trust at scale | 0→1 builds (Thermo Fisher, Red Cross) |
| Capital One — Director, AI in Experience Design | Agentic AI: live systems + Trust essay five-handoff framework | Alibaba (mandate-building) + Thermo Fisher (cross-org adoption) | Equinox+, Allē, Red Cross |
| Headway — Design Director, Provider Experience | 0→1 high-stakes: Red Cross → Thermo Fisher | Allē dual-surface platform | Agentic Labs (Q&A only) |
| Ramp — Director, Product Design | 0→1 high-stakes: Thermo Fisher ($20M margin, operational systems) | Trust essay "one wrong answer" frame + Alibaba trust signals | Red Cross, Equinox+ |
| Gusto — Sr. Product Design Manager, Payroll | 0→1 high-stakes: Red Cross (zero-error, federal oversight) → Allē | Alibaba trust architecture at transaction scale | Agentic Labs (Q&A only) |
Cross-cutting pre-work: Your homepage metadata now reads as design leadership, not Product Designer. That's resolved. Two gaps remain live. First, the homepage still links to TinyFish ("Currently: Head of Product, TinyFish"), which invites the product-vs-design question before you've framed it. Second, the private essay at what-do-you-count.html still delivers full HTML, including TinyFish pricing content, before any password check runs. Any technically literate buyer sees it. Remove the homepage link to the private essay before outreach to Capital One or Suno. The Homepage Copy Audit covers the full fix. Until then, be ready with the TinyFish reframe in every room.
Suno — Head of Product Design
Who this is. A top design-function hire spanning Product Design, Design Engineering, and UXR in a CPO-led org. Jack Brody, their Chief Product Officer (ex-Snapchat, 10 years), is the product executive. Expect founder involvement in the loop. No existing VP Design or Head of Design layer is publicly visible. High confidence this is the senior-most design role in the company.
What they're actually evaluating. Whether you already have a framework for what design becomes when the system generates the output. High confidence. Suno is AI-native. Every candidate will have strong product design work. The differentiator is whether you've already thought through the problem they're solving, or whether they'll have to teach you what agentic creative products demand.
Lead with. The Trust Is the New Interface essay. Open with it before any case study. The five-handoff framework maps directly to how a user interacts with AI music generation: intent-setting, in-progress visibility, output review, decision gate, loop feedback. Then show Brand Pulse as live proof you built the thing, not just theorized.
Support with. Alibaba. Transition: "Trust at Alibaba was a buyer committing six months of inventory on the strength of a screen. Trust in agentic products is the same architecture applied to systems that act on your behalf." The $50B GMV scale proves you can build cross-functional mandates, not just prototypes.
Cut or hold. Cut Red Cross and Thermo Fisher from the deck. They read as regulated-enterprise proof. Noise here. Equinox+ stays in reserve for a Q&A about consumer product intuition only.
IC+manager frame. Tilt toward hands-on craft and vision. The role asks for someone who stays close to the work while building the org across three functions. Show Agentic Labs architecture decisions. When you discuss Alibaba, emphasize the three sprint structures you designed, not the team you managed.
Landmine. "You built Agentic Labs solo. Can you lead a team doing this?" Reframe: "Solo builds are how I pressure-test frameworks before scaling them. At Alibaba, I took trust architecture I'd developed through direct research and operationalized it across three cross-functional sprint teams. Build the conviction hands-on, then scale the org around it."
Capital One — Director, AI in Experience Design
Who this is. A CDO-level org transformation role. This person sits on the XD "top of house" team, partners with the SVP Chief Design Officer and their Senior Leadership Team, and owns AI tooling roadmaps, process evolution, and talent upskilling across a large, matrixed design organization. The posting says "player-coach" who implements day-to-day and influences the C-suite.
What they're actually evaluating. Can this person make a large design organization change how it works with AI? Moderate confidence. The role language strongly supports this read, but the reporting structure and org scale are not publicly confirmed. The buyer is likely a design executive navigating their own transformation who needs someone who has already lived the transition.
Lead with. Invert the standard logic. Do not open with case studies. Open with: "I've already built the agentic workflows you're trying to install at scale." Walk through the live Agentic Labs systems and the Trust essay's five-handoff framework as the design operating model behind them. The essay is your credential here.
Support with. Alibaba and Thermo Fisher, reframed as org-change evidence. Alibaba: "Named a structural gap, built the research case, secured executive mandate, led adoption across three cross-functional teams." Thermo Fisher: "Six pharma partners adopted a system I designed from zero in twelve months." Both prove you drive adoption across organizational boundaries.
Cut or hold. Cut Equinox+, Allē, and Red Cross. They read as product design cases. This room evaluates org transformation capability.
IC+manager frame. Tilt toward influence and operating model. Show the Trust essay's framework as something you'd install as a design operating model across a matrixed org. This room evaluates altitude.
Landmine. "Your background is product design. This role is org transformation." Reframe: "Every system I've built required changing how an organization worked. At Thermo Fisher, the design problem was getting six pharma partners to abandon spreadsheets and adopt a shared operating system. That's an org-change problem with a design surface." The TinyFish question ("You're Head of Product, why a design role?") could surface here too. The Ramp reframe below is portable. Use it and pivot to published work immediately.
Headway — Design Director, Provider Experience
Who this is. A Director building a design leadership layer for Headway's provider EHR, the daily operating system for tens of thousands of mental health providers. Headway is hiring two Director-level roles simultaneously (Provider Experience and Core Insurance & Design Systems). High confidence they're standing up a design-leadership structure. The role specifies Claude, Cursor, and MagicPatterns as standard design tools. They want a Director who ships in that workflow.
What they're actually evaluating. Can this person lead provider-facing complexity in a regulated, insurance-adjacent environment while raising craft across an AI-native design team? High confidence based on role language that explicitly names hiring, AI practice contribution, and EHR workflow ownership.
Lead with. Red Cross. "Six systems consolidated to one, three roles that never shared a system, surge-ready for 10× volume." Maps directly to provider EHR complexity. Transition to Thermo Fisher: "Same pattern at pharma scale. Operational workflows where exceptions must surface before they become costly."
Support with. Allē. The dual-surface redesign (30M consumer members + 40K provider practices) proves you can hold both sides of a platform simultaneously. Headway's provider experience exists in tension with the patient experience. Allē is your proof you've navigated that tension.
Cut or hold. Hold Agentic Labs for Q&A about AI-native design practice. Don't present it. The role wants AI fluency as a working method. If asked, reference your Agentic Labs builds as evidence you've shipped with these workflows.
IC+manager frame. Balanced. The role says "hire, attract, and manage a team" while contributing AI practice. Show team-building evidence from Alibaba and Thermo Fisher, and show a design decision you made yourself. Red Cross works well: you were both the GM and the designer.
Landmine. "You're currently Head of Product. We're hiring a Design Director." Keep it direct: "Product leadership sharpened how I think about commercial outcomes. At Alibaba, I was Head of Design and Research running three cross-functional sprints across a $50B platform. At Thermo Fisher, Product Design Director, system adopted by six pharma partners. The work speaks to the scope."
Ramp — Director, Product Design
Who this is. A senior product-design leader who starts by owning a product area and team, with room to expand. The reporting line is not publicly disclosed. Ramp's role language is unusually specific about what design means there now: building tools and agents, designing memory, shipping PRs, rethinking process as new capabilities unlock. They want a builder who leads.
What they're actually evaluating. Can this person ship high-impact financial products at Ramp's velocity while helping define what design becomes in an AI-native company? High confidence. The posting's emphasis on product judgment, craft, systems thinking, and cross-functional influence with technical teams makes the evaluation frame clear.
Lead with. Thermo Fisher. "$20M margin recovered. Pharma supply chain exceptions that surface at the delivery gate cost 3–5× more than if caught a week earlier. Financial workflow errors have the same cost curve." Then the Trust essay's core line: "One confident wrong answer does more damage than ten correct ones repair." That sentence was written for this room.
Support with. Agentic Labs as builder credibility, then Alibaba for trust-signal architecture at transaction scale. The search redesign (34% of sessions sorted by Response Rate in month one) shows you can design trust into high-frequency decision surfaces.
Cut or hold. Cut Equinox+ and Red Cross. This room rewards density over breadth. Three cases, tightly connected, beat five that force the buyer to synthesize.
IC+manager frame. Tilt toward builder. Show the Thermo Fisher module architecture. Show a design decision where your judgment determined the outcome. Then briefly reference team scale at Alibaba. Builder first, leader second.
Landmine. "You're Head of Product at TinyFish. Why design?" This will surface at Ramp, Capital One, and Suno. Same answer every time:
"Product leadership sharpened how I think about commercial outcomes as design problems. I took the role deliberately. Now I'm returning to design leadership with a stronger product-judgment foundation."
Do not elaborate. Pivot to published portfolio immediately.
Gusto — Senior Product Design Manager, Payroll
Who this is. A design manager within an 80+ person design org, owning payroll. The posting calls payroll "one of Gusto's most complex and consequential product areas" and names it as the foundation of trust with every business on the platform. The role partners across Product, Engineering, Compliance, and Ops, and specifically asks the manager to lead AI and automation initiatives that reduce manual work without compromising accuracy or trust.
What they're actually evaluating. Can this person absorb payroll complexity, partner across six functional boundaries, and lead AI initiatives where the cost of error is a missed paycheck? High confidence. The posting is explicit: accuracy, compliance-adjacent partners, trust, AI-assisted design judgment, and shared standards across a large design org. The buyer wants proof you've operated in consequence-heavy constraints and didn't try to move fast and break things.
Lead with. Red Cross. "$847K disbursed, 1,689 cases in two weeks, zero retraining for surge volunteers, federal oversight from day one." Money moving through a system where errors affect real people, compliance is non-negotiable, the interface absorbs complexity so the user doesn't have to. Then Allē. Red Cross proved you can design for zero-error consequence. Allē proved you can do it inside a large platform with 30M members, 40K provider practices, and compliance-adjacent constraints, while driving measurable business outcomes: 3.2× redemption, $42 CAC. Both are systems where design absorbs complexity so the user never sees it.
Support with. Alibaba trust architecture. The -47% buyer-security-concerns reduction shows you can design trust into systems where money changes hands. Payroll's core design problem, stated differently.
Cut or hold. Hold Agentic Labs and the Trust essay for Q&A only. Lead with consequence. The role asks for AI fluency, but the evaluation will weight accuracy and compliance navigation more heavily. Moderate confidence on this read. If the conversation tilts toward AI early, the Trust essay's "one confident wrong answer" framing maps directly to payroll.
IC+manager frame. Tilt toward cross-functional partnership and operating within structure. Gusto has 80+ designers. They're hiring you to strengthen a critical pillar within an established org. Show how you partnered across six pharma companies at Thermo Fisher, worked within federal oversight at Red Cross. The signal you want to send: this person will make the existing system better.
Landmine. "Your AI work is experimental prototypes. Payroll requires zero-error production." Reframe: "Every system in my portfolio operates under that constraint. At Red Cross, a wrong disbursement was a family without housing. At Thermo Fisher, a missed exception was $20M regulatory exposure. The Agentic Labs work applies the same rigor to AI systems. The question I designed around: when does the agent act, and when does the human gate?"
- Ramp's agentic CX posting: Their Product Manager, Agentic CX role defines the human-operator and AI-agent division of work explicitly, which means the design Director will inherit that framework as a constraint or a collaboration surface.
- Headway's second Director opening: The Core Insurance & Design Systems role covers insurance operations, design systems, and internal tooling, and maps even more directly to Thermo Fisher's regulated-complexity proof than the Provider Experience role does.
- Capital One's player-coach language: The AI in Experience Design posting names Claude, Gemini, Claude Code, Stately, XState, and Windsurf as tools the Director should model day-to-day, which means your Agentic Labs builds are not just positioning but literal tool-fluency proof.
- OpenAI's Product Design Manager: The role covering Payments, Identity & Access, and developer tools is live but posted April 15, putting it outside the freshest action window — monitor for repost or language changes that signal a reset search.