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 7 | On Deck

Risk-Reading Framework

Name the Risk Before You Name Yourself

Job postings are negotiated documents. Most of the language is boilerplate. But each one usually contains a sentence carrying specific operational anxiety, and that line tells you more about the hire than everything around it.

Find it. Scan past collaboration-and-impact language. Look for the verb phrase attached to a consequence: balancing speed against risk, deciding when output is ready, retaining human oversight. Someone wrote that because the cost already showed up.

Use their words. "Deciding when an AI output is ready, needs review, or should not be sent" is how the buyer describes a supervision problem. Pull the phrase into your outreach. Your framework vocabulary earns credibility after you've demonstrated you read the posting at the operational level.

Lead with it. Your first outreach sentence names what breaks if this hire fails. That framing survives forwarding. Your credentials land harder inside a conversation already oriented to the right problem.

Caveat: some postings are aspirational wish lists, not scars. Treat the fear sentence as a working hypothesis you act on while verifying.

Risk-Reading Framework

Name the Risk Before You Name Yourself

Caveat: some postings are aspirational wish lists, not scars. Treat the fear sentence as a working hypothesis you act on while verifying.

Fear sentences from this cycle:

Gusto: "deciding when an AI output is ready, needs review, or should not be sent" — automated service completing a consequential action without human judgment

Capital One: "balancing speed against risk" across an org-wide AI rollout — tooling deployed to hundreds of designers without governance

HackerOne: "humans retain oversight, accountability, and strategic decisions" — agent acting on a security judgment before a human intervenes

Amplitude: "quality to erode unless Design creates coherence without turning into an approval bottleneck" — cheap AI-generated interfaces destroying product coherence

If you can't find it: the posting is too generic to act on, or the real mandate is hidden. Open with a question about what they're actually solving.

PART ONE

Only One Confirmed Buyer Across All Six Companies

OPEN

Swept all six companies for one signal: who holds the hiring decision, and can you reach them? One confirmed buyer — HackerOne's CPO, named in the posting. One posting that went dark — Capital One's requisition is no longer publicly available. The rest are inferred from public signals with varying confidence. The routing landscape is thinner than expected, and a fifteen-minute LinkedIn check you haven't done yet could upgrade the most routes at once. Five patterns, ranked by what they should change this week.

Only One Confirmed Buyer Across All Six Companies

PART TWO

The "Quality-Under-Acceleration" Buyer

OPEN

Amplitude, Gusto, and Vanta all adopted AI, watched it accelerate their teams, and then watched quality degrade. Now they're hiring design leaders to fix it — but they'll screen out anyone who sounds like they'll slow things down. This decoder reconstructs what these buyers actually test versus what they post. The stated criteria are generic: AI fluency, craft depth, player-coach. The real evaluation: can you build quality infrastructure that scales beyond your own hands, at the speed they've already committed to? Tells in postings and conversations, three fears they won't name, and the moves that win or lose them.

PART THREE

Vanta: The Search Is Five Weeks Old. Move This Week.

OPEN

Vanta's Head of Design posting is five weeks old. No language change, no interim leader announced, no public shortlist. VP Design searches at this stage typically close in one quarter — that puts the narrowing window at three to five weeks from now. Epling's blended-model philosophy and the sandbox-enabled agent expansion mean this isn't a standard backfill — it's a quality-governance mandate, and your Trust essay maps directly to the problem his engineering team is documenting in public. Contact Epling by end of this week.