Trigger
R243245, Director, Product Design - AI in Experience Design, refreshed July 20 after the May 28 original post. High confidence the role is live and actively sourcing. The visibility conflict covered in issue #3 is resolved. Move.
Window
Act this week. A refreshed Director posting in enterprise means the first slate failed or thinned. You are in week one of a 3–5 week window before a second slate locks. Enterprise cycles are slow by default. The refresh itself is the velocity signal. They want this filled.
What this trigger probably means for the design org
Capital One's XD org is not waiting for this hire. The 34 concurrent design roles tell you that. More telling: a Design Systems IC posting that explicitly asks the designer to shift from "traditional asset creator to experience auditor, logic planner, and automation coach" and to design "AI-Native Design Guardrails" governing human intent and automated agent execution. The IC infrastructure for AI governance is already being built. What the org lacks is the person who decides what those guardrails should actually be, how they scale across several hundred designers, and what the review/reversal/escalation model looks like when AI-assisted work becomes the default. That is the mandate underneath this posting.
Your angle
Lead with "Trust Is the New Interface" as an org-design framework. The posting's mandate is AI tooling, process evolution, talent upskilling across the XD function. Your Trust essay's five handoffs (Intent-Setting, In-Progress, Output Review, Decision Gate, Loop Feedback) are the governance layer for exactly that: how designers review, explain, reverse, and govern AI-assisted work. The adjacent Design Systems posting proves Capital One is already converging on this vocabulary independently. You are the candidate who published the framework their org is building toward.
Secondary: Alibaba ($50B+ GMV, enterprise-scale platform redesign) and Thermo Fisher (regulated 0→1, operating-model build) anchor enterprise credibility. They prove you've operated at scale inside high-stakes environments. They are not the lead.
Competitive landscape
Three archetypes likely in this pipeline. Confidence: moderate, inferred from Capital One's visible hiring patterns and role requirements.
- Enterprise design directors from Daniela's network. Capital One's recent senior XD hires pull from PayPal, Google, and Amazon. Large-org credibility. Likely personal rapport with Daniela. Almost certainly no published AI governance framework. They will pitch org experience. You pitch the framework the org is converging on. Your vulnerability: network proximity. Daniela has publicly welcomed PayPal alumni onto her team. A warm referral from that network compresses the trust cycle in ways cold outreach cannot match.
- AI-native design leaders. Strong tool fluency, possibly from an AI company or AI-focused consultancy. They know the medium. They haven't operated at enterprise org scale with several hundred designers. They will pitch exactly what you should avoid: tool proficiency. The posting's named tools (Claude, Gemini, Windsurf) are bait. The role governs how tools get used, not which ones.
- Internal candidates. Thirty-four concurrent design roles means a large, active org. The 7-week gap between original posting and refresh could mean an internal option was explored and didn't work out. If so, the refresh favors external candidates with a differentiated frame.
The Trust essay convergence with the Design Systems posting is your strongest differentiator against all three. No other candidate can claim a published framework that independently mirrors the org's own emerging vocabulary.
Who to contact
Name: Daniela Jorge, SVP and Chief Design Officer. LinkedIn. Former CDO at PayPal.
Public fingerprint: Three signals, all consistent. A March 2026 Graded Gazette interview (her high school alumni publication, not a design-industry venue; know this if she asks where you read it) where she says AI's opportunity and concern both come down to "how do we keep people at the center" and emphasizes considering consequences alongside value. A September 2025 Capital One XD article she shared on LinkedIn, framing XD as carrying "privilege and profound responsibility" for financial well-being; her own post added that XD was "driven by keeping customers at the forefront." A 2023 Capital One interview stating AI requires safeguards against risk and bias and responsible development keeping humans at the forefront of every decision.
The through-line: human governance of AI, consequences alongside value, responsibility at scale. Your Trust essay speaks this language natively.
Warm intro path: Cold. No confirmed overlap between your networks (BCG DV, Alibaba NA, ADPList) and Daniela's visible connections.
Channel: LinkedIn cold DM to Daniela Jorge. Hook on her "people at the center" language mirrored against the Trust framework.
Outreach messages
Subject line (if sending via email): AI governance at org scale — the review and reversal model for XD
Warm message (deploy if a mutual connection surfaces):
"[Name] suggested I reach out. Your framing in the Graded interview — that AI's opportunity and concern both come down to keeping people at the center — is the exact tension I published a framework around: 'Trust Is the New Interface' (junochen.com/trust-is-the-new-interface), five handoffs where human judgment stays in the loop as AI capability scales. I'm building enterprise agents in production daily as Head of Product at TinyFish and working through the governance challenges your XD org is about to encounter at several-hundred-designer scale. Would welcome 20 minutes on how you're thinking about the review and reversal model for AI-assisted design work across XD."
Cold message to Daniela Jorge:
"Your framing in the Graded interview — that AI's opportunity and concern both come down to keeping people at the center — is the exact tension I've been building around. The hardest version of that problem is the org surface: how do several hundred designers review, explain, reverse, and govern AI-assisted work without either rejecting the tools or trusting them uncritically? I published a framework for exactly that (junochen.com/trust-is-the-new-interface) and I'm stress-testing it daily building enterprise agents at TinyFish. I'd welcome 20 minutes on how you're thinking about the review and reversal model across XD."
What not to say:
- Do not pitch tool fluency. The posting names Claude, Gemini, Windsurf, Figma. Every candidate will claim proficiency. This role defines how an org governs tool use. Tool fluency is table stakes, not a differentiator.
- Do not praise Capital One's design culture generically. "I admire what you've built" is empty at CDO level. Reference a specific publication, a specific org-design challenge, or the Design Systems posting's language. Anything else signals you read the About page and stopped.
Cover letter draft
The hardest design problem at Capital One right now lives inside the XD org: how do several hundred designers adopt AI tooling without losing the judgment, craft standards, and human-centered rigor that make the work trustworthy? The Director, Product Design - AI in Experience Design role describes this precisely — roadmaps for AI tooling, process evolution, and talent upskilling across Design. That is an org-design problem with design-system mechanics, and I've spent the past two years building toward it.
I published "Trust Is the New Interface" (junochen.com/trust-is-the-new-interface) as a framework for exactly this: five handoffs where human judgment stays in the loop as AI capability scales — Intent-Setting, In-Progress, Output Review, Decision Gate, Loop Feedback — with a trust ladder (Watch → Verify → Delegate) that gives designers and their leaders a shared language for how much autonomy to grant AI at each stage. Your Design Systems team is already building toward this vocabulary. The IC posting for AI-Native Design Guardrails describes the transition from asset creator to "experience auditor, logic planner, and automation coach." The framework I published is the governance layer those guardrails need to sit inside.
I built the agentic workflows (Agentic Labs at junochen.com — Brand Pulse, Retail Velocity, Carrier IQ) that demonstrate all five handoffs in production. My enterprise platform work at Alibaba.com ($50B+ GMV, +20% daily transactions) and Thermo Fisher ($20M+ margin, pharma, 0→1) grounds this in the scale and regulatory complexity Capital One operates within.
I'm currently Head of Product at TinyFish, an enterprise web agent platform (Series A), where I build and deploy enterprise AI agents daily — agent traces, auditability, attribution, reversibility, governance in production. I moved to product to build AI-natively from zero. I'm returning to design because the problem I want to solve next is the one this role describes: turning individual AI fluency into org-wide design governance at scale. My portfolio is at junochen.com.
Resume emphasis guidance
- Lead with: "Trust Is the New Interface" essay (Jun 2026) and Agentic Labs (Brand Pulse, Retail Velocity, Carrier IQ). AI exposure quality is the dominant rubric axis here. Primary proof.
- Follow with: Alibaba.com — Head of Design and Research, North America ($50B+ GMV, +20% transactions, +2.2pt NPS). Enterprise scale credibility. Proves you've operated inside a large, matrixed org and driven measurable outcomes.
- Third position: Thermo Fisher mySupply ($20M+ margin, 6 pharma partners, 0→1, 12 months). Regulated environment, operating-model build from scratch. Proves you can design how work gets done, not just what gets shipped.
- TinyFish in header: "Head of Product, TinyFish (enterprise web agent platform, Series A)." One line in role description: "Shipped 3 products in 3 months; daily work with agent traces, auditability, attribution, and governance in enterprise deployments."
- Trim or move down: Equinox+ (consumer, wrong domain for this buyer), Red Cross (mission-driven but not the org-transformation proof this role evaluates). Allē can stay mid-resume for dual-surface credibility. Not top three.
- Frame the transition: The resume summary should read as a deliberate arc: enterprise design leadership → agentic AI production → returning to design to solve AI governance at org scale. The TinyFish move was the technical immersion that makes the return more valuable, not a detour.
The non-obvious thing
The Design Systems IC posting is your competitive intelligence advantage. It asks designers to build "AI-Native Design Guardrails" and describes the role transition from "asset creator" to "experience auditor, logic planner, and automation coach." Two things competing candidates almost certainly will not know. First: the org is already building IC-level infrastructure for AI governance, which means the Director role defines the framework those ICs implement. You are not starting from zero. Second: the language Capital One is independently arriving at — "guardrails," "human intent and automated agent execution," "contribution governance" — converges with your Trust essay vocabulary. That convergence is a moat. Reference it in conversation. You are not importing an external framework. You are naming what they are already building toward.
Post-outreach signals
- Response within 5–7 business days = normal enterprise pace.
- Silence past 10 business days = either in process or the message didn't reach Daniela. Follow up at day 10, then day 20.
- Recruiter screen + hiring manager screen in the same week = hot signal on a refreshed posting. Prepare the junochen.com walkthrough framed around org-design governance before the conversation.
- Never follow up more than twice. Three unanswered messages = redirect energy.
- If asked for a portfolio walkthrough: Lead with the Trust essay as org-design framework, then Agentic Labs as production proof, then Alibaba for scale credibility. Do not lead with case studies. This buyer is evaluating whether you can define how designers work with AI, not whether you can design products.
Warning signs
The role may be narrower than the posting suggests. The posting names both strategic vision ("define how Design works with AI") and day-to-day player-coach implementation ("experimentation and adoption curve"). If the actual mandate is closer to internal tooling rollout management than org-wide governance design, the scope ceiling drops significantly.
"Does this role own the standards and decision rights for how AI-assisted work gets reviewed and approved across XD, or is it primarily responsible for tooling adoption and training?" The answer tells you whether this is a transformation mandate or a change-management coordinator role. The former is worth pursuing at this level. The latter is not.
- Gusto just posted fresh: A Head of Design, Unified Service Platform role went live July 22 and explicitly names trust, graceful failure, AI-human handoffs, and "outputs that should not be sent" — the closest vocabulary match to your Trust essay outside Capital One.
- Amplitude's intelligence-layer mandate: The Head of Product Design posting describes a player-coach leading 15 designers across Core Amplitude, Statsig, and Wave, where the commitment point is whether a product team trusts machine-surfaced insight enough to act on it.
- Vanta's governance-heavy Head of Design: The VP-level role asks for AI-native design practice, agentic UX patterns, and launch review frameworks across a 40-person org spanning GRC, Trust, and Platform — with a $365K–$513K base range.
- Capital One's internal AI product proof: Their Chat Concierge article describes a multi-agentic assistant that validates plans, checks hallucinations, simulates execution against policies, and explains the plan to the customer — useful context if Daniela asks how you'd connect XD governance to Capital One's live AI product surfaces.