Who holds the hiring decision, and can you reach them?
Swept all six companies — Amplitude, Gusto, HackerOne, Fieldguide, Vanta, Capital One — for one signal: who is the confirmed buyer for the design leadership role, and what is the strongest available route to them.
The routing landscape is thinner than expected. One contextual finding first: the sweep checked for VP Product, VP Design, CPO, or founding executive hires across the set in the last 90 days. Zero. Menachem at Amplitude is closest — appointed CPO on April 14, now 117 days in seat. Outside the receptivity window where a new leader is actively shaping their team, but still the freshest executive arrival in the set. His public activity — Agent Analytics, session failures, traces — shows he is defining the product direction the design role would serve. Whether his appointment triggered the design search or preceded it remains unresolved.
Five patterns, ranked by how much they should change what you do this week.
1. Only one confirmed buyer in the entire set
HackerOne's posting names the reporting line explicitly: Director of AI Product Design reports to CPO Nidhi Aggarwal. A message to Aggarwal reaches the decision-maker. Everywhere else, buyer identity is inferred from public signals with varying confidence.
Gusto: Amy Thibodeau is the plausible owner based on her public connection to the AI-first design transition. The posting does not name the reporting line.
Amplitude: Gab Menachem has formal oversight of design, but whether the Head of Product Design reports to him directly or through an intermediate layer is unknown. A 2024 company profile still lists Kim Lenox as VP of Design with no confirmed departure. Succession search and new-scope hire carry different internal politics. Worth naming in conversation, not resolving from the outside.
Vanta: Jeremy Epling is the likely buyer based on his stated scope (product, engineering, and design report to him), per the timeline reconstruction. The posting does not confirm this.
Fieldguide: Lauren Abulaban's hiring activity names the design mandate directly. Not confirmed as the formal hiring manager.
What this means for your outreach: When you know the recipient is the buyer, your message can go straight to the design problem and your proof. When the recipient might forward your message internally, the message has to survive forwarding — legible to someone who didn't choose to read it, shorter, one proof point instead of a framework, a specific ask the forwarder can endorse without having to explain you.
Quick-reference priority order:
- HackerOne — confirmed buyer, clean hook, no gates
- Gusto — strong hook, plausible buyer
- Amplitude — product-language translation required, succession question worth naming
- Vanta — authority confirmed by prior coverage, weaker hook
- Fieldguide — comp verification before positioning
- Capital One — verify the mandate is alive before anything else
2. Capital One's posting went dark
The R243245 requisition now shows postingAvailable: false on Workday. The role does not appear on Capital One's design jobs index. This supersedes the assessment in Issue #5, which carried high confidence the role was live and actively sourcing.
Could be filled, paused, pulled into a retained search, or canceled. No way to distinguish from outside.
Capital One moves from Act to Verify. Patrick Dohan publicly promoted the search with specific language about defining design's relationship to AI. If you reach out, lead with the mandate — how design orgs absorb AI at the practice level — not the requisition. That framing works whether the role moved to a retained firm, got paused, or filled. If the mandate is alive, you've opened the right conversation. If the role is gone, you've had a useful exchange that costs you nothing.
Confidence: High that the public posting is unavailable. Low on why.
3. What each contact can credibly carry into the organization
The question underneath "warm or cold" is whether the person you're writing to has publicly articulated the design problem the role solves. That determines how much translation your message needs to do.
Aggarwal (HackerOne) and Thibodeau (Gusto) both give you vocabulary you can mirror directly. Aggarwal's posting names autonomous systems, human oversight, accountability — your Trust essay maps to that language with almost no translation. Thibodeau's public record connects to the tension between automation and human judgment in Gusto's design practice.
Menachem (Amplitude) speaks in product language — Agent Analytics, session failures, conversion. Your outreach needs to translate into his frame. Lead with the intelligence-layer problem: what happens when the product surfaces an insight the user doesn't trust? Not design practice language.
Epling (Vanta) has structural authority but less public design-problem vocabulary. The hook has to come from the posting and from Kawamoto's departure context, not from Epling's own statements.
4. Two routes need verification before full positioning
Two companies in this set have gates that should be resolved before you invest in a fully positioned outreach package.
Fieldguide: Abulaban has publicly named the design mandate (rethinking audits with AI, end-to-end design ownership). Good hook material. But the published base range is below your cash floor. A short message confirming whether the range is flexible costs ten minutes. A fully positioned outreach package for a role that can't clear your floor costs two hours you could spend on HackerOne or Gusto.
Capital One: The posting is unavailable (Pattern 2). The mandate may still be alive, but the requisition is not publicly open. A short message to Dohan about the AI-in-XD mandate costs ten minutes. A full positioning package for a role that may no longer exist costs the same two hours.
Resolve the gate, then invest.
5. The fifteen-minute move that upgrades the most routes at once
The research could not verify mutual LinkedIn connections for any of the seven contacts — Daniela Jorge, Patrick Dohan, Amy Thibodeau, Gab Menachem, Jeremy Epling, Nidhi Aggarwal, Lauren Abulaban. Mutual connection counts are only visible to the signed-in viewer. The entire set defaults to cold, and only you can check for an upgrade.
Check your LinkedIn mutual connections with all seven names. Fifteen minutes. One mutual who has seen your work converts a cold message into an introduced one. One mutual who works at the target company converts it into an internal referral.
You cannot know which routes are upgradeable until you check.
- Kim Lenox's current status: Amplitude's December 2024 profile still lists Lenox as VP of Design, and no departure or role change has been confirmed — whether the Head of Product Design search is a succession or expansion changes how you position in conversation with Menachem.
- Vanta's stale design page: The official design-careers page still names Deb Kawamoto as VP Design despite her publicly stated end-of-June departure, which means the company's public org surface is lagging the actual leadership transition by at least six weeks.
- HackerOne's accept-modify-reject pattern: Their Agentic Validation documentation specifies that users may accept, modify, or reject agent output rather than receiving automatic disposition — a more precise hook for your outreach than generic "human-in-the-loop" framing.
- Gusto's AI-native design shift: The company's "From Designers to Builders" account describes moving within one quarter toward an AI-native operating model where designers work closer to the codebase, which is the organizational context underneath the Head of Design role Thibodeau likely owns.