The earlier scan sorted seven AI design roles into three jobs. The current landscape is denser — Brex, Ramp, Gusto (six qualifying roles), Adobe (two), and Amplitude are all confirmed live — and three groupings no longer hold. Five distinct accountability units are visible across the active target list.
Your current routing groups targets by company archetype: AI-native, enterprise, growth-stage. That grouping is now misleading you. Brex and Ramp are both AI-native fintech. They are hiring for different jobs. Gusto has six open roles spanning four of the five clusters below. One version of your story sent to all six gets averaged down to nothing.
The five mandates, ranked by how many active targets they contain. For each: the firing condition, the posting language that reveals it, which junochen.com evidence to lead with, and who to direct it to.
1. Consequential-action trust
Firing condition: Automated action causes irreversible harm in a domain where users cannot afford to be wrong.
Active targets: Brex Staff Product Designer, AI. Handshake Staff Designer, Student Experience. Headway Staff Product Designer, Provider Practice Growth (cash band $212K–$265K; crosses the $250K threshold only at the top). Gusto Staff Designer, HR Experiences. Gusto Senior Staff Designer, Finance.
Posting tells: "trust," "transparency," "human-in-the-loop," "consequential," "when to ship / when not to ship," "review and correct," "agency."
Evidence lead: Trust essay + Carrier IQ. The Brex posting literally describes your framework — delegate, monitor in-progress, review outputs, establish trust — without citing it. For Gusto HR, the service-boundary language maps directly to the Trust essay's decision gate: when does the agent hand back to a human? For Headway, the AI front desk handles booking and follow-up for providers while a real patient is on the other end — Thermo Fisher (completed as Product Design Director at BCG DV) supplies the regulated multi-party workflow proof, and the Trust essay adds the automation-boundary language. TinyFish production experience (agent traces, auditability, governance) is the verbal credibility layer in conversation, not the portfolio lead.
Five of your active targets sit here. This is where your published work is most differentiated — most AI-native designers have built trust patterns internally but haven't published the design thinking behind them.
Buyer intelligence: At Handshake, May-Li Khoe (VP of Design) likely owns the Student Experience search — the VP of Product, Handshake AI is a separate business unit and does not manage this role (see clarification below). At Brex, no public design leadership signal found — the role sits on the AI team, so the hiring manager is likely a VP or Head of AI Product rather than a design executive. Route through the AI team's leadership page. At Headway, Jake Poses (VP of Product) likely owns the search, but his decision proximity to this specific Staff role has not been recently confirmed. At Gusto, six simultaneous design hires across four accountability units implies an active Head or VP of Design making these decisions, but no name confirmed on public surfaces.
Identifying Gusto's design leader unlocks outreach to four of the five mandate clusters — more coverage from a single name than any other research action available.
2. Coherence across autonomous surfaces
Firing condition: The product fragments into disconnected experiences as teams ship independently.
Active targets: Amplitude Head of Product Design. Adobe Senior Director of Design, Firefly.
Posting tells: "coherence," "consistency," "across [multiple surfaces]," "without becoming [bottleneck/gatekeeper]," "quality as [speed/volume/AI] increases." The anxiety is entropy — things flying apart faster than taste can hold them together.
Evidence lead: Amplitude's posting says the problem is preserving coherence while autonomous pods keep shipping fast. Alibaba is the direct answer: you held coherence across homepage, search, and PDP — three surfaces with competing stakeholders — while leading cross-functional sprints and staying in the production work yourself. The posting explicitly rejects the executive-delegator model. For Adobe Firefly, the mandate splits: coherence is structural, but the posting also names MAU growth and retention as success metrics. Lead coherence, support with Allē growth proof (3.2× redemption, 47% lapsed reactivation).
The prior Amplitude brief already identified this mandate. The confirmed posting language validates it without changing the evidence routing.
Buyer intelligence: Both roles ARE the design leadership hire — the buyer sits above. At Amplitude, the Head of Product Design reports into product leadership; no confirmed name for the hiring executive on public surfaces. At Adobe, the recently filled Head of Design, Adobe Creative role may be the Firefly buyer or an adjacent peer — the filled posting confirms someone is now in seat, but the name has not surfaced publicly. If you have any Adobe network connections, use them here.
3. Adoption and retention economics
Firing condition: The numbers don't move.
Active targets: Ramp Director, Product Design. Gusto Staff Designer, Retirement. Adobe Firefly partially (MAU growth, retention).
Posting tells: "adoption," "conversion," "retention," "funnel," "engagement," "product impact," "business metrics," "growth."
Evidence lead: Ramp's posting says the Director earns broader scope by first establishing trust and product impact within a single product area. That is the Alibaba story: you named a structural gap nobody had framed, built the mandate yourself, delivered +20% daily transactions. Ramp is hiring someone who proves impact before claiming authority. Allē supplies the economic metrics (3.2× redemption, $42 CAC, 47% lapsed reactivation) if the conversation turns to growth-specific proof. Ramp requires AI-assisted prototyping (Claude, Cursor), so TinyFish production currency supports — but the accountability unit is product impact, not AI architecture.
Leading with the Trust essay or forward-looking artifacts here would be a misroute. The buyer is measuring shipped outcomes.
Buyer intelligence: At Ramp, the Director role itself is the design leadership hire. The buyer is likely VP Product or a co-founder. No public design leadership signal found, which is consistent with a company hiring its first senior design leader. At Gusto Retirement, same gap as Cluster 1: the Gusto design leader is the key unknown.
4. Infrastructure that enables others to ship
Firing condition: The rest of the org can't produce quality work at the speed AI makes possible.
Active targets: Gusto Staff Designer, Design Systems. Adobe Group Product Design Manager, Systems.
Posting tells: "systems," "tokens," "components," "adoption [of the system, not the product]," "enable," "tooling," "infrastructure," "documentation." "AI" appears here as the production method — AI-assisted design tooling, LLM-readable documentation, MCP servers — not as the product.
Evidence routing: Skip. You have no published design-systems case study, no infrastructure-as-product proof. The Gusto posting says deliverables are code and equates the level to Senior Staff engineering. Competing candidates from Figma, Shopify Polaris, or similar systems teams will outperform on the specific construct being tested. Revisit only if a forward-looking artifact in the Agent Infrastructure as UX domain ships and directly addresses this accountability unit.
5. Organizational capability installation
Firing condition: The org doesn't change how it works.
Active targets: Capital One Director, Product Design - AI in Experience Design. Gusto Senior Product Design Manager, Payroll.
Posting tells: "operating model," "workflow transition," "upskilling," "practice," "how the team works," "AI-assisted [design/work]," "quality standard [for the team, not the product]."
Evidence lead: Trust essay as methodology — the five handoffs translated from customer-agent to designer-AI workflows — plus Agentic Labs as demonstration of what the methodology produces. The Capital One brief already established this routing. Gusto Payroll is a compressed version of the same mandate: leading a team through an AI-workflow transition within a single product line.
Buyer intelligence: At Capital One, Patrick Dohan is the strongest first route — his public hiring post says "I'm hiring" and describes the mandate in his own language. Daniela Jorge (SVP and Chief Design Officer, formerly CDO at PayPal) is the executive sponsor and likely final evaluator. Jorge has been in seat long enough to have established her evaluation framework; the Trust essay's vocabulary should map to how she thinks about scaling AI capability across a hundreds-person design org. At Gusto Payroll, same design-leader gap as the other Gusto clusters.
Reported absences
Atlassian: No qualifying Staff+ or Director+ product design opening confirmed. A Senior Designer, Design Systems role exists but falls below threshold.
Stripe, Anthropic, OpenAI: No new qualifying postings beyond what prior scans cover.
Suno, Abridge, Salesforce: Swept, no qualifying Staff+ or Director+ product design posting found on employer-controlled careers surfaces. Suno and Abridge remain thin-signal companies where roles may be unadvertised or filled through network.
Handshake clarification
The VP of Product, Handshake AI is a separate business — human-data labeling for AI model training — with its own product org. It does not manage the Student Experience design role. The Staff Designer, Student Experience remains a consequential-action trust role in Cluster 1. May-Li Khoe likely still owns that search.
The pattern that changes behavior
Gusto alone has six roles across four accountability units. Brex and Ramp are both AI-native fintech, but Brex buys trust architecture and Ramp buys product impact. The company name tells you where to look. The posting's accountability unit tells you what to say when you get there. Across the clusters, one research gap keeps recurring: Gusto's design leader is unidentified, and that single name would unlock outreach to four of the five mandates. Find that person first. Then read every posting for the firing condition before you choose your evidence lead.
- Ramp's earn-then-expand model: Ramp's Director posting says you start with one product area and earn broader scope through demonstrated impact, which means the first outreach should name which area you'd want and why, not claim the whole portfolio.
- Gusto's design-systems-as-code bar: The Design Systems Staff posting equates the level to Senior Staff engineering and lists MCP servers, prompt engineering, and eval systems as deliverables, confirming that some "design" roles have moved entirely past the portfolio-and-prototype evaluation surface.
- Webflow's agent-inside-design-systems framing: Webflow's new CPO and SVP of AI Transformation announced in July, and the company's August product post says agents should work inside existing design systems, permissions, and activity logs with humans retaining control of live publication — language that maps directly to your supervision and decision-gate themes, though no qualifying design vacancy has surfaced yet.
- Adobe Firefly's filled Head role: Adobe's Head of Design, Adobe Creative posting now shows as filled, meaning someone is newly in seat who may be the buyer or peer for the Firefly Senior Director search — worth identifying through Adobe network connections before reaching out.