The posting was dispersed. Its mandate is now scattered across three functional roles that went live in the same window. Your entry point just changed shape, and the new shape is better for you.
Here is what the sequence tells you, and what to do about it.
The Decay Sequence
R243245, Director, Product Design - AI in Experience Design, posted May 28, 2026. Reports to SVP/CDO. Mandate: define how Capital One's hundreds-person XD org integrates AI into its design practice. An org transformation role, full stop.
Three moments in the posting's lifecycle matter:
- May 28: R243245 goes live on Capital One's careers site. Director level. AI + Experience Design. Clear org-wide scope.
- July 3–4: During a research pass, the direct URL still resolves, but the role no longer surfaces through search or category navigation. The posting is being withdrawn from candidate discovery while the underlying req sits in some administrative state.
- July 9: Direct URL returns 404. Same generic error page Capital One's Radancy front end serves for URLs that never existed. Searching for R243245 returns nothing.
The decay was staged, and that staging is the signal worth reading. A role that vanishes overnight was filled: someone accepted, HR closed the req, the page drops. A role that fades from search surfaces first, then loses its direct URL days later, was being actively managed out of visibility. Someone decided to stop showing it before someone decided to kill the page. Two decisions, made at different moments, possibly solving different problems.
What 34 Design Postings Reveal
Capital One's design careers page currently lists 34 roles. The org is not contracting. Three director-level product design roles posted July 6–7 alone.
None replicate R243245's scope. The Concierge Products director leads Velocity Black and backend agent experiences within Premium Design. The Acquisitions director owns Core Card Experiences. The IC director in Customer Acquisitions leads craft excellence across revenue-driving products. Product-portfolio leadership roles. They own surfaces.
R243245 owned the operating model.
Now look at three other postings that went live in the same window:
Design Systems IC manager: Explicitly says the hire will "move beyond a traditional Figma-only system role," govern AI-native environments, create AI-generated-pattern criteria, coach designers on AI-assisted tooling.
Senior Director of Research & User Intelligence: Lists AI-enabled continuous discovery tools, synthetic data, and automated research workflows as preferred qualifications. Ten-person team across Experience Platform, Marketing & Messaging, and Developer Experience.
Design Operations manager: Covers standards, process, tooling, design process bottlenecks.
Read those three postings together and you are reading R243245's job description broken into pieces and distributed across functional owners. AI-in-design-systems. AI-in-research. AI-in-operations. The same mandate, three containers instead of one.
The Jorge Gap
Daniela Jorge holds the SVP and Chief Design Officer title, formerly CDO at PayPal. That is confirmed through Capital One sources and public profiles. What is not publicly established from any authoritative source I can verify: her start date at Capital One, her PayPal departure timing, or any public signal about her priorities for the XD org. No conference talks found. No authored Capital One design blog posts. No press interviews about AI integration or org transformation. Capital One's own AI/customer-experience blog content names other leaders, not Jorge.
This gap costs you analytically.
Without a temporal anchor for Jorge's arrival, I cannot distinguish between a CDO eight months in (still diagnosing, first structural experiment failed, R243245 was a hypothesis that didn't survive contact with the org) and a CDO eighteen months in (executing a deliberate phased rollout, R243245 was always going to decompose into functional roles once she understood where the leverage points were). The first scenario means she is still learning what shape the AI-practice mandate should take. The second means she has already decided, and the three functional postings are the decision.
Both scenarios lead to the same prediction. They lead to slightly different outreach angles, which I'll address below.
The public silence itself is a signal. A CDO who posted R243245 in May, evaluated the response or rethought the shape by early July, and redirected the mandate into functional roles is building internally, executing against a roadmap she hasn't made public. That pattern is consistent with someone who has a strategy and is implementing it, whether or not the outside world can see the architecture.
The Claim
R243245 was restructured.
The staged decay, the absence of any repost combining director + AI + Experience Design under a different ID, and the simultaneous appearance of AI-practice language in three functional roles that collectively cover R243245's scope all point the same direction. If the role had been filled, there would be no reason to scatter its language into adjacent postings. If it had been paused with intent to reactivate, the URL would more likely persist in some holding state rather than return the same 404 as a fabricated URL.
What would have to be true for this to be wrong: Capital One filled R243245 in late June, the new hire starts in July, and the AI language appearing in Design Systems, Research, and Design Ops was planned independently of the role's closure. Three functional roles all acquiring AI-practice language in the same window that a dedicated AI-practice director role disappears would have to be coincidence. That requires more explanation than the dispersal hypothesis.
Confidence: medium-high. Posting lifecycle and cluster shape point the same direction. The Jorge tenure gap is the limiting factor on whether the dispersal was a correction or a planned phase transition.
What Each Scenario Means for You
If restructured (most likely): The consolidated entry point is gone, but the need got distributed across three functional owners. Capital One is embedding AI capability across design systems, research, and operations simultaneously, without a single leader coordinating the integration. That coordination gap is your angle. You are naming a problem the org just created for itself.
If filled: You missed R243245 specifically, but the dispersal pattern still matters. If someone was hired into R243245 and the AI-practice language still appeared across three functional roles, one of two things happened: the hire's scope was narrowed on arrival (the org absorbed part of the mandate before the person started), or the hire is now the person coordinating across Design Systems, Research, and Design Ops. In the first case, the coordination gap persists and your angle holds. In the second case, that person is who you should be mapping to. Either way, the three new director roles (Concierge Products, Acquisitions, Customer Acquisitions) are live, and the Concierge Products director with its "backend agent experiences" language has the closest surface area to your Agentic Labs work, though it is a product-portfolio role requiring different positioning entirely.
If paused: A paused req at Capital One's scale typically reactivates within 4–8 weeks if the mandate survives budget review. The July cluster burst confirms H2 headcount is unlocked. If a new director-level role appears in the next 2–3 weeks that recombines AI + design practice + org scope, R243245 was paused and reshaped. That becomes your direct application target.
The Move
Reach Daniela Jorge directly. LinkedIn. The restructuring is your opening.
Narrative fit: You've built the agentic workflows Capital One is now trying to install across three separate functional teams without a unifying framework. Your Trust essay provides the trust architecture for how humans and AI systems hand off decisions. Your Agentic Labs (Brand Pulse, Retail Velocity, Carrier IQ) demonstrate live implementations of the exact patterns their Design Systems, Research, and Ops roles are each trying to solve in isolation. The outreach angle: "You're embedding AI practice into design systems, research, and operations simultaneously. I've built the frameworks for how those pieces connect and published the trust architecture that governs them. Here's what I mean." Link the essay. Link Agentic Labs. Let the work carry the argument.
If Jorge is eight months in and still shaping the mandate, this outreach reads as a candidate who sees the problem she's solving and has a framework for it. If she's eighteen months in and executing a deliberate decomposition, it reads as someone who understands the coordination challenge her phased approach creates. Both land.
Secondary evidence if the conversation advances: Alibaba for enterprise-scale org credibility ($50B+ GMV, multi-surface redesign, named the structural gap and built the mandate). Thermo Fisher for regulated-environment navigation and multi-stakeholder platform architecture.
Tuesday or Wednesday next week, morning. The three director postings from July 6–7 confirm Jorge is actively building. The coordination gap between the distributed AI-practice roles is freshest right now, before someone internal fills it or the org adjusts around it.
- Ramp's director posting ages: Diego Zaks, VP Design, is the visible buyer for Ramp's Director, Product Design role, and the posting hits the 22–42 day extended band next week, so probe before it goes stale.
- Headway's provider mandate sharpens: Headway's Design Director, Provider Experience posting names AI-assisted clinical documentation, billing, and insurance verification as core scope, making it the cleanest current match for your Thermo Fisher and Red Cross proof.
- Perplexity just posted design systems: A Design Systems Lead role posted July 9 asks for someone to bootstrap semantic tokens, own the design-system repo, and bring AI tooling into the workflow, which is useful signal even if the level is below your target.
- Capital One's Concierge director names agents: The freshest product-portfolio role in the cluster, Product Design Director for Concierge Products, explicitly covers "backend agent experiences" within Premium Design, and is worth watching as a fallback application target if the Jorge outreach opens a different conversation.