Agent Authority Is the Hiring Filter This Week

Scan window: September 27 – October 3, 2026 Scan coverage: All priority career pages (Anthropic, OpenAI, Suno, Abridge, Brex, Stripe, Ramp, Gusto, Headway, Amplitude, Zoox, Salesforce, Atlassian, Adobe, Rubrik), VC portfolio boards (a16z, Sequoia, Greylock, Lightspeed, General Catalyst, Accel, Insight, Bessemer, YC/WorkAtStartup), and aggregators (LinkedIn Jobs, Wellfound, Built In, Ashby, Greenhouse, Lever). Six signals are sequenced for action below. The full qualified pool, including still-hot signals at OpenAI, Anthropic, Figma, and Handshake, sits in the Active and Monitoring lists. Shelf life: Act Now entries decay by October 10. Act Soon entries hold through October 17.

The Cluster: Authority Over Agent Output

Four of this cycle's signals — Stripe Link, DoorDash New Bets, Amplitude Wave, Ramp Design Systems — are hiring against the same problem under four different names. Stripe writes "agentic commerce." Amplitude writes "agentic workflows." Qixing Zheng at DoorDash writes about decision ownership becoming scarcer as more people can make. Ramp wants repeatable evaluations of design quality that an agent produced. Underneath the vocabulary, each req asks the same thing: who holds authority over what an agent did on a user's behalf, and what does the person exercising that authority actually see?

Portfolio-production implication: The Trust essay covers this ground and it's public, which is why it carries every outreach draft below. CarrierIQ's approval gate and Brand Pulse's visibility layer are the production proof under it. What's absent is the next layer. None of the four forward-looking artifact domains (Inference-Aware UX, Intent-Based Interaction, Agent Infrastructure as UX, Human-Agent System Design) has a public URL. Today you can show a reviewer that you understand the problem and that you've shipped adjacent to it. You cannot show them a design for the thing they are hiring someone to build, and that is the differentiator these four postings are reaching for.

Monday's three moves:

1. Direct buyer contact: Message Dan Nelson at Stripe. He posted within the last 48 hours.
2. Apply-and-route: Apply to OpenAI Consumer Verticals and DoorDash New Bets. Message Qixing Zheng, who says she's hiring for her own team.
3. Verification contact: Reach Meredith Fay at Amplitude to learn how the design org is structured while the Head of Product Design search is still open.

Act Now

Stripe Link — Dan Nelson Is Hiring for Agentic Commerce

Rubric: Company 11 (AI centrality 2, stage/equity 3, design ceiling 3, trajectory 3) | Role 15 (comp 3, scope 3, craft 3, AI exposure 3, portfolio value 3) | Verdict: Act Buyer-route confidence: High Demand family: Agent-authority design Tier archetype: AI-native | Read AI-native playbook before outreach.

What changed: Dan Nelson, Head of Design for Consumer Products at Stripe, has been recruiting Staff Product Designers for Link across two posts. The older one, roughly a month old, frames the mandate as owning visual direction for new bets, bringing "visual conviction" to early concepts, and shaping Link across Checkout, AI partners, and Link's own app. His closing filter: comfort when "the problem is undefined and the canvas is blank." A second post surfaced inside the last 48 hours through a Stripe colleague's public LinkedIn activity and sharpens the ask: "explore the future of agentic commerce… obsessed about craft and quality, love to code." It references multiple Staff hires and adds agentic commerce and coding comfort as explicit filters.

Why it matters: The first post is about owning visual direction on a wallet. The second adds agent-mediated transactions as the frontier, and he wants both in one hire. CarrierIQ maps onto the second half without translation: a user inspects agent-assembled context before authorizing a financial commitment. Issue #13 dropped Stripe on a stale ATS record. Nelson's recruiting activity plus the live careers listing reset that clock.

Confidence: High. First-person hiring language, named role, corroborated by the Stripe careers page.

Window: You are two to three days into a four-day hot window for a hiring post. By Wednesday this is Watch. Move Monday.

Move:

(a) Who: Dan Nelson, Head of Design, Consumer Products, Stripe. Joined roughly two years ago after nine years across Tock and Squarespace. Stated criteria: visual conviction, craft obsession, coding comfort, agentic commerce, tolerance for undefined problems. He is the direct buyer. Katie Dill is the broader Stripe design leader (covered in Issue #10 for the Data & AI role); Nelson owns Consumer Products and Link.

(b) Warm path: Cold. No shared investor, no visible mutual. "Come join us" in his post functions as an open door, so a substantive connection note is sufficient. You don't need an introduction.

(c) Multi-channel outreach plan:

1. Send the connection request with a tailored note, Monday morning.
2. Apply through Stripe careers in parallel, Monday.
3. If the connection is accepted, send the full message within 24 hours.
4. No response by Thursday: one follow-up via LinkedIn message referencing the application.

(d) Connection request draft (~300 chars):

(e) Full outreach message (~240 words):

(f) What not to say: This is a Staff IC role. Nelson is screening for craft conviction and hands-on capability. Team-building, hiring, or org leadership will read as misaligned. Lead with CarrierIQ and the Trust essay; Alibaba is supporting context here, not the opener.

Interview prep flags:

• What to expect: Portfolio review weighted toward visual craft and tolerance for ambiguity. The blank-canvas language means he will test whether you can set a direction, not execute one handed to you. Expect a prototyping or whiteboarding component. "Love to code" is a filter, not decoration.
• Portfolio lead: CarrierIQ's approval gate as agent authority over a financial transaction. Open with the Trust essay framework, then walk CarrierIQ as the production proof. Allē's dual-surface work is the secondary if they probe consumer range.
• Key question to ask: "When an agent completes a transaction through Link on behalf of a user, what does the user see after the fact, and is that surface something you're actively working on or something you're hiring someone to define?"
• Leadership dynamic: Nelson is two years in and building his team. Position as a craft peer who can own visual direction without supervision. The Trust essay shows you were working on his mandate before you saw his posting.
• Competitive differentiator: You've designed agent-authority surfaces in a financial context in production, and published the framework behind them. Most candidates at this level have one or the other. The essay grew out of the shipping, and that combination is difficult to replicate from scratch.

Battlecard handoff: Flag as Company Battlecard candidate. The prior Stripe entry in Issue #10 covered Data & AI; Link and Consumer Products need their own.

OpenAI Consumer Verticals — Two Days Old, Direct Thesis Match

Rubric: Company 11 (AI centrality 3, stage/equity 3, design ceiling 2, trajectory 3) | Role 15 (comp 3, scope 3, craft 3, AI exposure 3, portfolio value 3) | Verdict: Act Buyer-route confidence: Moderate Demand family: Agent-authority design (high-consequence vertical) Tier archetype: AI-native | Read AI-native playbook before outreach.

What changed: OpenAI posted Product Designer, Consumer Verticals on October 1, base range $245,000–$310,000 plus equity. The role owns zero-to-one consumer experiences across health, finance, and general consumer agents, including systems that support complex decisions or take action for the user. Trust, accuracy, safety, transparency, and user agency are named as design requirements.

Why it matters: The requirement list restates the Trust essay's problem set almost item for item, and it sits exactly where agent authority meets high-consequence decisions. CarrierIQ (financial commitment), Thermo Fisher (pharma), and the five handoffs all map. The $245K floor keeps the role just under the rubric's top cash band until leveling is known; equity at OpenAI's stage closes that question.

Confidence: High on role and company. Moderate on the buyer route. Ian Silber is publicly identified as OpenAI's Head of Design, but the requisition names no reporting line or hiring manager. Silber is an org-owner route, not a confirmed requisition owner.

Window: Two days old. Hot through approximately October 22. Apply this week.

Move:

(a) Who: Ian Silber, Head of Design, OpenAI. Org-level design authority. The Consumer Verticals hiring manager is not publicly identified. Gap flagged: Silber may not own this req.

(b) Warm path: Cold.

(c) Multi-channel outreach plan:

1. Apply through the Ashby posting Monday.
2. Send Silber a connection request leading with substance.
3. On acceptance, send the full message positioning the Trust essay and CarrierIQ against the mandate.
4. In parallel, hunt the Consumer Verticals team lead or PM. Adjacent postings or LinkedIn activity may surface the actual hiring manager before the next cycle.

(d) Connection request draft (~300 chars):

(e) Full outreach message (~200 words):

(f) What not to say: Keep Alibaba and enterprise scale out of it. This is 0→1 consumer in high-consequence verticals, so the regulated-domain work and the agent-authority work carry the message. Don't speculate about OpenAI's internal leveling.

Interview prep flags:

• What to expect: Prototyping speed and comfort with instability. Expect questions about designing when model capability is changing faster than the interface can settle.
• Portfolio lead: Trust essay framework, then CarrierIQ as production proof, then Thermo Fisher for regulated-domain credibility.
• Key question to ask: "When an agent takes a health or financial action for a user and gets it wrong, what does the recovery surface look like today, and does this role own it?"
• Competitive differentiator: A published framework for agent-authority design, grounded in production work, paired with a shipping history in pharma and national disaster relief. Plenty of candidates in this pipeline will have frontier thinking. Few will also have high-stakes delivery credentials in regulated domains.

Battlecard handoff: Flag as Company Battlecard candidate. Consumer Verticals is a separate mandate from the previously tracked Youth and Codex roles. Tier Playbook: Read AI-native playbook before outreach.

Act Soon

DoorDash New Bets — Zheng Is Building Her Team

Rubric: Company 7 (AI centrality 1, stage/equity 1, design ceiling 2, trajectory 3) | Role 13 (comp 2, scope 3, craft 3, AI exposure 2, portfolio value 3) | Verdict: Watch. Placed in Act Soon on signal urgency: Zheng's hiring post crosses decay thresholds this week. Buyer-route confidence: High Demand family: Agent-authority design (process-side) Tier archetype: Growth-stage platform | Read growth-stage playbook before outreach.

What changed: Qixing Zheng posted five days ago that she's hiring a Staff Product Designer for Meals for Work inside DoorDash for Business. Her criteria: "someone who thinks in systems and loves to build," hands-on with AI tools, code, and prototyping. San Francisco preferred, New York or Seattle acceptable.

Why it matters: Zheng separately published five observations about AI-assisted design that function as a published evaluation rubric: prototypes as the principal artifact, designer value shifting toward judgment and direction, decision ownership mattering more as AI accelerates making. Read them before you write anything. The formal posting says the role reports to the Head of New Bets Design, and Zheng's first-person "I'm hiring for my team" language confirms she runs the search. Her exact title is unconfirmed; best-supported label is Senior Product Design Manager, New Bets, consistent with Issue #13.

The company score is borderline at 7. DoorDash is public, AI is peripheral to the core product, and org-level design influence is unclear. The role carries the score: New Bets is 0→1 territory with real craft depth and no visible ceiling. The urgency comes from Zheng's post, not from the company.

Confidence: High on Zheng as decision-maker. Moderate on company-level design influence.

Window: Seven days old by Monday, inside the 5–14 day Watch band for hiring posts. Apply and message this week. By October 12 the signal is stale.

Move:

(a) Who: Qixing Zheng, Senior Product Design Manager (best-supported title), New Bets, DoorDash. Her published observations on AI and design are the clearest available evidence of what she evaluates for.

(b) Warm path: Cold.

(c) Plan: Apply through DoorDash careers Monday. Connection request to Zheng the same day. Full message on acceptance, referencing the application.

(d) Connection request (~300 chars):

(e) Full outreach message (~180 words):

(f) What not to say: Don't present as a logistics or marketplace designer. New Bets is build-from-nothing work, so lead the 0→1 portfolio and leave enterprise scale out.

Interview prep (condensed):

• Portfolio lead: Allē's dual surface (consumer plus provider) maps onto Meals for Work (employee plus workplace admin). CarrierIQ for the agent-authority angle.
• Craft filter: Systems thinking and hands-on prototyping. "Loves to build" is a screen. Bring a prototype.
• Key question: "You wrote that faster iteration creates a risk of over-iteration. How does your team decide when to stop?"

Battlecard handoff: Flag as Battlecard candidate. Issue #13 covered DoorDash briefly; New Bets needs its own, with product scope and leveling.

Amplitude — Two Searches, One Org in Transition

Rubric: Company 7 (AI centrality 2, stage/equity 1, design ceiling 2, trajectory 2) | Role 13 (comp 2, scope 2, craft 3, AI exposure 3, portfolio value 3) | Verdict: Watch. Placed in Act Soon because the dual-search signal is fresh and the transition opens a narrow information-gathering window. Buyer-route confidence: Speculative Demand family: Agent-authority design (product-side) Tier archetype: Growth-stage platform | Read growth-stage playbook before outreach.

What changed: Amplitude posted two design roles at once: a Principal Product Designer for Agentic Workflows (Wave) and a Head of Product Design leading a 15-person team across Core Amplitude, Statsig, and Wave. The Head role carries accountability for AI-native workflows, craft quality, and human-agent collaboration.

Why it matters: Two simultaneous searches at different levels in the same function point to a design org being rebuilt rather than backfilled. The open Head role means the senior design seat is empty. Gab Menachem (CPO) is the confirmed executive authority, with nobody settled between him and the team. The Wave posting names Meredith Fay (Lead Designer) as a collaborator, not a manager. An older company profile lists Kim Lenox as VP of Design, which the open Head search suggests is no longer current.

The timing risk is plain: the person who would evaluate you for the Principal role may not be hired yet. Apply now to sit in the pipeline, but expect the real evaluation to wait for the Head to land.

Confidence: Moderate on the role. Speculative on the buyer route; no hiring manager is publicly confirmed for either req.

Window: Both postings are inside the 0–21 day hot band. The vacant leadership seat is what makes the evaluation timeline unpredictable, not the posting age.

Move:

(a) Who: No confirmed hiring manager. Meredith Fay, Lead Designer, is the strongest named design-side contact from the Wave posting. Gab Menachem, CPO, is the executive fallback. Gap flagged: the decision-maker for this role is either unfilled or unidentified.

(b) Warm path: Cold.

(c) Plan: Treat this as a verification contact, not a pitch. Apply to the Principal Product Designer, Agentic Workflows role. Send Fay a connection request with a question about the design org and Wave. What you want back: who evaluates the Principal role, and what the timeline looks like alongside the Head search. If the Head of Product Design lands first, that person becomes the target.

(d) Connection request (~300 chars):

(e) Full outreach message (~160 words):

(f) What not to say: Don't ask about Kim Lenox or point at the leadership vacancy. That's internal context you shouldn't signal awareness of in a cold message.

Interview prep (condensed):

• Portfolio lead: CarrierIQ (reviewing agent-produced output) and Brand Pulse (in-progress visibility) map straight onto agentic workflow design.
• Key question: "When Wave's agent finishes a workflow for a user, what does the user see: a result, or the reasoning that produced it?"

Battlecard handoff: Flag as Battlecard candidate. The dual search and org transition warrant a full Battlecard before any interview.

Watch

Ramp — Design Systems Lead

Ramp posted a Design Systems Lead at $280,000–$385,000 SF/NY base plus equity. The ATS files it under Engineering, while the spec describes the hire as "a designer first" running the design systems team, with agent guidance, AI-assisted generation, and repeatable design-quality evaluations in scope. The company scores well at 10: pre-IPO, accelerating, meaningful equity. The role clears Act on rubric math, but the mandate is design systems, which is not your strongest angle, and the reporting line is unresolved. Whether it sits under Diego Zaks (VP of Design) or an engineering leader changes what the job is. What would escalate: a product design posting on Ramp's AI-native surfaces, or confirmation that this reports to Zaks.

Rubric: Company 10 (AI centrality 2, stage/equity 3, design ceiling 2, trajectory 3) | Role 13 (comp 3, scope 2, craft 3, AI exposure 3, portfolio value 2) | Verdict: Watch — rubric clears Act; positioning fit and reporting-line ambiguity warrant verification before spending outreach. Tier Playbook: Read growth-stage playbook if escalated (Ramp straddles growth-stage and AI-native).

Deprioritize

Stripe Data & AI: Covered in Issue #10 via Katie Dill. No fresh signal this cycle, and Nelson's Link role is the live Stripe opportunity. Pause until a new posting appears.

Window Status Changes