How to Route
Classify the target in thirty seconds. One question per tier:
- Does the posting signal that the company needs someone who has already named the design problem their product category faces? Frontier AI.
- Does the posting emphasize shipping under regulatory, clinical, or financial constraint? Regulated Platform.
- Does the company run a marketplace or platform where trust architecture is the product itself? Enterprise.
- Does the posting describe transforming how design operates internally? Enterprise Design Org Transformation.
If a company fits two tiers, match the posting language, not the brand narrative. Read the job description, not the About page.
Short week. Hiring managers clearing inboxes Wednesday before a four-day weekend will spend less time per message. Front-load harder than usual. Send before Thursday or wait until July 7.
Tier 1: Frontier AI → Suno
The buyer here is hiring someone who has already named the design problem they're working on. At frontier AI companies, the design brief has not yet been written. Portfolio cases showing shipped screens are irrelevant because the problem those screens solved has not been defined yet at the target company. Your Trust essay is a stronger opener than any case study because it proves you operate at the problem-definition layer. Lead with it.
Opening hook:
"I wrote 'Trust Is the New Interface' because I kept watching AI products fail at the same handoff: the moment the system acts and the user has to decide whether to believe the result. That essay maps five handoffs in every agentic workflow and a trust ladder — Watch, Verify, Delegate — that I think applies directly to what Suno is building. I wrote the essay while building live agents to test the framework against real system behavior."
Proof block:
Name the agents by name and function. Brand Pulse processes 76 live signals into one decision surface and forces a specific design question: how do you build confidence when the agent sees more than the user can verify? Carrier IQ orchestrates five insurance carriers in 90 seconds and solves a different trust problem: how does an operator verify a result without slowing the loop? Both are live, solo-built, and exist because the trust framework needed to be tested against real system behavior.
Closing ask:
"I'd like to spend 30 minutes on how Suno thinks about the trust gap between generation and user confidence — where in the workflow users hesitate, and what you've tried. I have a point of view, but I'd rather pressure-test it against what you're seeing in production."
This works because Suno is pre-consensus on what "design" even means for their product. The cover letter demonstrates that you've already started the work they haven't yet figured out how to scope.
Tier 2: Regulated Platform → Headway
The buyer needs proof you've shipped under real regulatory or operational constraints. Headway's provider experience sits at the intersection of clinical documentation, insurance verification, billing, and AI-enabled care workflows. The hiring manager has reviewed portfolios full of clean UI with zero evidence that the designer understood what happens when compliance requirements, federal oversight, or payer rules constrain every surface. They need proof you've shipped under that weight and delivered measurable outcomes anyway.
Opening hook:
"The hardest design problem I've solved wasn't visual. It was building the American Red Cross national disaster relief platform under active federal oversight, where a caseworker had to resolve identity, residency, and eligibility before entering a single line item, and untrained volunteers had to use it on day one of a surge deployment."
Proof block:
- Red Cross: Replaced six legacy systems with one unified platform, deployed nationally inside a single disaster response cycle. $847K disbursed, 1,689 cases opened in the first two weeks. Team of one designer, one researcher, one PM, two engineers, two BAs. Every surface designed for auditability under federal review.
- Thermo Fisher: $20M+ margin impact, 100% partner adoption. Adds the commercial-constraint layer.
- Allē (for the multi-sided dimension): Dual-surface design across 30M members with 3.2× redemption lift and $42 CAC. Proof you can hold both sides of a platform in tension without optimizing one at the expense of the other.
Closing ask:
"I'd welcome a conversation about how Headway balances AI-enabled workflow transformation with the compliance and clinical-documentation constraints that make healthcare design fundamentally different from consumer product design. I have specific experience building under those constraints and shipping anyway."
A note on sequencing. Headway's posting says they're building an AI-first design team and expects designers to prototype in code using Claude and Cursor. That's exciting language, but read what the posting actually asks the design director to do: define what an AI-native practice management experience looks like across scheduling, documentation, session experience, and client engagement. The AI tooling is how they'll build. The constraint environment is what they're hiring you to navigate. A single Headway session touches scheduling, telehealth, clinical documentation, outcome measurement, insurance verification, and billing. That is a Red Cross problem. Lead with Red Cross because it proves you can build a mission-critical platform from zero, under federal oversight, with a small team, and deliver measurable outcomes in weeks. Save the AI-native practice capability for the conversation. It's real, but it comes second.
Tier 3: Enterprise → Alibaba
The buyer is hiring for architectural thinking validated by platform-scale outcomes. The proof needs to be denominated in transactions, GMV, and behavioral change across millions of users. No equally sharp live role signal exists for this tier right now, so the framework stays more portable. Use it for any enterprise company where the design leader role is fundamentally about platform-scale systems thinking. Adapt the hook to the specific company's trust problem, but keep Alibaba as the anchor.
Opening hook:
"I redesigned the trust architecture for Alibaba's cross-border marketplace — the system that determines whether a buyer in São Paulo believes a seller in Shenzhen will deliver what they promised. That work moved daily transactions up 20% and reduced buyer security concerns by 47%."
Proof block:
Alibaba trust architecture: +20% daily transactions, -47% buyer security concerns, +2.2pt NPS lift, across a platform processing $50B+ GMV. Every surface from seller verification to shipment tracking to dispute resolution had to reinforce the same trust signal without requiring the buyer to understand the underlying complexity.
Closing ask:
"I'd like to discuss how trust signals compound or decay across a multi-step transaction flow on your platform — whether the confidence a user builds at discovery survives through fulfillment and resolution, or whether each stage resets the trust equation. I've built the architecture that solves that problem at Alibaba scale and have a specific framework for how it translates."
At this tier, the metrics do the positioning work. The numbers are unambiguous and the scale is undeniable. Keep the hook tight and let Alibaba carry the weight.
Tier 4: Enterprise Design Org Transformation → Capital One
This tier inverts the standard logic entirely. Capital One is hiring someone to install a new operating model for how design works inside a large enterprise. The buyer has reviewed a hundred portfolios from people who have "led design teams at scale." None of them built the agentic workflows, the AI-native design practice, the new operating model that Capital One is trying to figure out how to adopt across thousands of designers and product teams.
Lead with the essay and the live agents. Case studies and team-building narratives come later.
Opening hook:
"I've already built the agentic workflows you're trying to install at scale — designed them, coded them, shipped them live. 'Trust Is the New Interface' is the design framework. Brand Pulse and Carrier IQ are the live systems. I built them solo to test a thesis: that the trust handoff between human and agent is the defining design problem of this generation of product work, and that you cannot design for it without building the agents yourself."
Proof block:
Trust essay: five handoffs in every agentic workflow, a trust ladder (Watch → Verify → Delegate) that gives design teams a shared vocabulary for where human oversight belongs in any AI system. Live agents built solo to validate the framework against real system behavior. Brand Pulse: competitive intelligence agent, 76 signals, one decision surface. Carrier IQ: parallel quote orchestration, five carriers, 90 seconds, behavioral transparency as a design pattern for operator trust.
Then, and only then, the enterprise credibility layer: Alibaba trust architecture at $50B+ GMV. Red Cross national platform deployment under federal oversight. Thermo Fisher at $20M+ margin. These prove you can operate at enterprise scale. They belong in the second paragraph. The first paragraph belongs to the work Capital One is trying to figure out how to start — work you've already done.
Closing ask:
"I'd like a conversation about operating model, not portfolio. Specifically: how Capital One is thinking about agentic-native design practice at scale — where the trust framework lives in your workflow, how designers interact with agents in production, and what the org structure looks like when AI is a design material woven into every workflow. I have a point of view built from doing this work, and I'd rather have that conversation than walk through slides."
The standard Director+ cover letter assumes the buyer wants to see your track record of leading teams and shipping products. Capital One's org-transformation hire inverts that assumption. They have plenty of people who can lead teams. They are looking for someone who has built the practice they're trying to install. Your essay and live agents function as a working prototype of the operating model Capital One needs. The case studies prove enterprise credibility. The essay and agents prove you've already started building what they're still scoping.
Before You Send
- Pick the tier. The proof blocks stay constant across targets within each tier. The hooks and closing asks require real adaptation to each target company's specific product, public design challenge, and whatever you can learn about what their hiring committee is actually solving for. Do not treat this as find-and-replace. The proof is portable. The framing requires work every time.
- Click every portfolio link in your proof block. If a case page has been restructured, renamed, or taken down since this was written, the framework needs to adapt. A cover letter that names a project the hiring manager can't find when they click through is worse than omitting it.
- Match the closing ask to the buyer. One pattern across all four tiers: the closing ask is calibrated to what each buyer type actually wants to talk about. Frontier AI wants to discuss the unsolved problem. Regulated platforms want to discuss shipping under constraint. Enterprise wants to discuss systems-level architecture. Org transformation wants to discuss operating model. A mismatched closing ask tells the hiring manager you don't understand what role you're applying for, regardless of how strong your proof is.
Hiring managers clearing inboxes on Wednesday before the Fourth will remember the candidate who was specific over the one who was polished. Write the letter tonight. Send it tomorrow morning.
- Ramp's agentic CX signal: Ramp's live Product Manager, Agentic CX posting defines a human-operator and AI-agent hybrid model and asks the owner to decide how agents and humans divide work, which makes it a strong pairing target for the Trust essay framework alongside their Director, Product Design role.
- Gusto's payroll correctness language: Gusto's Senior Product Design Manager, Payroll role updated June 25 centers trust, compliance, and reducing operational complexity for small businesses, mapping cleanly to a Thermo Fisher or Red Cross lead under the Regulated Platform tier.
- Headway's second design director role: Beyond Provider Experience, Headway's Design Director, Core Insurance & Design Systems posting covers insurance platform foundations, design systems at scale, and internal tooling, which would shift the lead case from Red Cross to Thermo Fisher if you target that role instead.
- Capital One's role specifics on AI tooling: The live Director, Product Design - AI in Experience Design posting explicitly names Claude, Gemini, Claude Code, and Windsurf as tools the director should model day-to-day, confirming this is a player-coach role where your solo-built agents are direct proof of working fluency, not just strategic framing.