Share

Company Battlecards

On DeckKnow who to contact, what to say, and when to move

On Deck

Know who to contact, what to say, and when to move

SUBSCRIBE CONTACT US

Company Battlecards — Issue 1 | On Deck

Trust in the Job Copy

Trust just became a job requirement

Four postings from this cycle's scan use trust language that would have lived on a values poster two years ago. Now it shows up as evaluable job criteria.

Gusto's Senior Staff Service Designer asks candidates to articulate "what happens when the AI gets it wrong, how uncertainty should be represented to customers." That's a screening question with a right answer. Anthropic's PM Safeguards requires "safety by design upstream" and zero-to-one system work with "detections, evals, interventions." Their Policy Design Manager owns "age assurance, content classification, and safety interventions." OpenAI's Product Design Manager, Foundations wants design quality that "produce[s] cohesive experiences that build trust" across Payments, Identity & Access.

Every one of those phrases describes a deliverable. NIST's AI Risk Management Framework, updated April 2026 with a Critical Infrastructure trust profile, confirms the pattern at the institutional level. Your Trust essay and Agentic Labs work are already operating in this language. The companies writing these postings are catching up to the frame you published.

Trust in the Job Copy

Trust just became a job requirement

Four postings from this cycle's scan use trust language that would have lived on a values poster two years ago. Now it shows up as evaluable job criteria.

What they're actually screening for

Gusto: "how an exception moves between systems and teams," "how work routes between automated and human support," "preserve customer agency"
Anthropic (Safeguards): "metrics to understand the area, performance, blindspots," "risks and benefits of new technologies… beyond past checklists"
Anthropic (Policy Design): "age assurance approaches and content classification frameworks," "designing appropriate interventions"
OpenAI (Foundations): trust as infrastructure layer — Identity, Payments, Access

Why this week matters: These postings are live now. The July 4 holiday compresses response windows. Hiring managers reviewing applications Thursday will have a short stack. If you're reaching any of these companies this week, the trust-as-operations frame is the baseline they're already filtering for.

PART ONE

Five AI-Native Companies, Zero Design-Owned Trust Mandates

OPEN

Swept the job boards at Cursor, Replit, Perplexity, OpenAI, and Anthropic for one signal: which function owns trust decisions about the user experience. At all five, product managers and engineers hold that authority. Design teams exist. None of them own trust. No global design executive surfaced at any of the five. The Head of Design posting you're watching for may never appear — trust architecture is being set right now by PMs and policy leads without a design partner. This maps where authority sits and who to contact instead.

Five AI-Native Companies, Zero Design-Owned Trust Mandates

PART TWO

Every AI Posting Says "Build Trust." They Mean Three Different Things.

OPEN

Every AI design leadership posting uses the word "trust." Anthropic means failure-mode judgment. Gusto means exception-handling architecture. Enterprise buyers mean something else entirely — whether you can narrate organizational change without threatening the people already in the room. They never tell you which version they mean. They evaluate on recognition: the buyer knows their version when they hear it, and if you lead with the wrong one, you get a polite pass. Three tiers, three operational definitions, three different portfolio leads. Here's how to read which one you're facing before the screen starts.

Every AI Posting Says "Build Trust." They Mean Three Different Things.

PART THREE

What Capital One's Hiring Sequence Reveals About the AI-in-Design Director Role

OPEN

Capital One's AI in Experience Design Director role is 33 days old. The July 4 break kills two business days. By July 9, the posting crosses the threshold where it gets refreshed, restructured, or pulled. That's the timing problem. The positioning problem is harder: the sequence of events since Daniela Jorge arrived as Chief Design Officer reveals exactly where this role's authority starts and stops — and it's somewhere more specific than the posting language suggests.