Start With Figma, Stop Scanning Stripe

Six fresh signals in five days. Three of them (Figma, Motive, Gusto) come with a named person and a reason to write on Monday. Siro and Handshake clear Act Now on a different basis: both decision-makers have publicly described the design problem your Trust essay was written about. Everything else is deferred or dead, with the reason stated.

Act Now

Figma — Director, Product Design, AI & Context

Conditional thesis: Worth pursuing if the Context Platform pillar is building trust and transparency infrastructure for AI-generated design outputs, which is the problem your Trust essay and the Agentic Labs builds already address.

Abort trigger: The role is a pure management layer with no hands-on AI product influence, or Context Platform turns out to be data infrastructure with no user-facing design surface.

What changed: Figma posted a Director, Product Design — AI & Context role overseeing the Context Platform pillar and managing a multi-team design group.

Why it matters: Director-level scope on the AI pillar at a company whose product is design itself. Highest ceiling in this queue. Your Agentic AI pillar carries the relevance; Alibaba carries the scale.

Rubric: Company 10 (design influence ceiling maximal, trajectory accelerating, AI a primary strategic bet). Role 15 (3/3/3/3/3 — director comp with $290K–$376K base plus equity, AI pillar scope, craft depth through product influence, AI-native exposure, strong portfolio value). Clears Act.

Confidence: Moderate. The posting is confirmed. The reporting line is not publicly determinable.

Window: Fresh posting. Expect 3–4 weeks of active slate-building.

Tier Playbook: Read Enterprise platform playbook before outreach.

Battlecard status: Battlecard candidate — request before interview.

Move:

(a) Who: Noah Levin, who grew Figma's Product Design org from 3 to 80+. Treat him as sponsor and router, not as the confirmed hiring manager. Loredana Crisan is CDO. Where this director role actually reports is not public, and that gap is worth raising early.

(b) Warm path: Cold.

(c) Standard sequence. Engage with Levin's design-leadership content first.

(d) Connection request: "Noah — the AI & Context director role maps to work I've been doing on trust architecture for agentic systems. I led design for Alibaba.com ($50B+ GMV) and recently shipped enterprise AI agents from 0→1. Would value a conversation. junochen.com"

(e) Full outreach message:

Noah,

The hardest design problem in AI right now is the gap between what a model can do and what a user should trust it to do. I've spent the last two years working on that gap. Through Agentic Labs I designed and shipped three AI products that handle trust calibration in production: Carrier IQ automates insurance quoting, Brand Pulse interprets real-time sentiment. Most recently, as Head of Product at TinyFish, I shipped an enterprise web agent platform from zero and worked daily with agent traces, auditability, and governance.

Before the AI work I led design and research for Alibaba.com's North America platform — $50B+ GMV, a full redesign across homepage, search, and product detail pages, +20% daily transactions. That's where the enterprise-scale muscle comes from.

The Context Platform pillar sounds like it sits between those two threads: making AI outputs trustworthy enough that designers act on them without second-guessing. My published essay "Trust Is the New Interface" lays out a five-handoffs framework for exactly that kind of human-agent calibration.

Portfolio and essay at junochen.com. Happy to walk through the AI work in detail.

Juno

(f) What not to say: Don't position as a pure AI specialist. Figma reads for design judgment and taste first. Lead with the judgment applied to AI, not the vocabulary.

Interview prep flags:

• Format: Portfolio review with design leadership, then cross-functional sessions with product and engineering on the AI pillar.
• Portfolio lead: Trust essay as the conceptual opener, Carrier IQ for production AI trust design, Alibaba for enterprise scale.
• Key question: "How does the Context Platform define success — model accuracy, user confidence in the output, or something else?"
• Leadership dynamic: A CDO in place means design already holds structural authority. Position as someone who does her best work when design has a seat, not someone who needs to fight for one.
• Differentiator: You've shipped trust architecture for AI systems in production. Most director candidates have managed AI-adjacent teams without designing the trust layer themselves.

Motive — Director, Product Design

Conditional thesis: Worth pursuing if the role carries real product influence over Motive's AI-powered fleet platform and Kahn's player-coach language means hands-on design leadership rather than a management title over a thin team.

Abort trigger: Design reports into product management with no strategic seat, or "player-coach" turns out to mean a team of one.

What changed: Motive posted a Director, Product Design role. A current employee's hiring post describes it as reporting to Kahn with direct executive alignment and AI-centric workflows.

Why it matters: You designed fleet platforms at BCG Digital Ventures. Cummins/ZED Connect paired a consumer-facing IoT product for owner-operators with predictive asset management for commercial fleets — a closer domain match than most director candidates can produce.

Rubric: Company 11 (AI-native fleet platform, pre-IPO with $1.3B+ growth financing, accelerating trajectory). Role 14 (3/3/3/2/3 — director comp with $225K–$295K base plus RSUs, player-coach craft depth, moderate AI exposure through fleet AI, strong portfolio value). Design influence ceiling is the open question; see abort trigger. Clears Act.

Confidence: High on role existence and hiring manager. The titles don't agree — the posting says VP of Design, the employee post says SVP, Product Design. Moderate on design influence ceiling: the posting uses "cross-functional collaboration" three times, which usually means design doesn't have the seat yet and they're hoping the hire will earn one.

Window: Fresh posting with active employee amplification. 3–4 weeks.

Tier Playbook: Read Enterprise platform playbook before outreach.

Battlecard status: Battlecard candidate — request before interview.

Move:

(a) Who: Jadam Kahn, SVP/VP Product Design. Public signal worth using: a first-person request for a "strong player/coach" design manager. He also posted about Motive's AI Assistant, crediting design for embedding an agent that surfaces contextual insights and recommends actions.

(b) Warm path: Cold.

(c) Standard sequence. Engage with the player-coach or AI Assistant post.

(d) Connection request: "Jadam — the Director role caught my eye. I designed fleet management platforms at BCG DV (Cummins/ZED Connect: IoT + predictive asset management) and recently shipped enterprise AI agents from 0→1. Your player-coach model matches how I lead. junochen.com"

(e) Full outreach message:

Jadam,

Your framing of design leadership as player-coach — hands-on with the product while growing the team — is how I've operated for the last decade. The Director role maps to two threads in my background that rarely show up in the same candidate.

Fleet management: as Product Design Director at BCG Digital Ventures, I designed Cummins/ZED Connect from zero. A dual-surface platform spanning consumer-facing IoT (driver hours, routes, locations for owner-operators) and predictive asset management for commercial vehicle fleet maintenance, across mobile, tablet, and web.

AI in production: most recently as Head of Product at TinyFish, I shipped an enterprise web agent platform from zero and worked daily with the problems your AI Assistant is solving — contextual intelligence, recommended actions, trust calibration for AI-generated outputs.

I've also published three AI products through Agentic Labs (live at junochen.com) and a framework for human-agent trust design, "Trust Is the New Interface."

Fleet-domain experience and AI production depth in one candidate is what I'd bring. Happy to walk through any of it.

Juno

(f) What not to say: Don't overindex on distributed team management. Kahn's posts put craft and product ownership ahead of team growth.

Interview prep flags:

• Format: Portfolio review focused on product outcomes, then a conversation with Kahn about design philosophy and team-building. The player-coach emphasis suggests he'll want to watch you think through a problem live.
• Portfolio lead: Cummins/ZED Connect for domain match, Carrier IQ for AI trust design, Alibaba for enterprise scale.
• Key question: "How does the AI Assistant's design surface evolve — is the team designing the model's behavior or the interface around it?"
• Leadership dynamic: The VP/SVP title discrepancy suggests the org is still settling. Ask about reporting line and scope in the first conversation, not the fourth.
• Differentiator: Fleet management plus AI production experience. That pairing is rare at director level.

Gusto — Senior Staff Product Designer, Finance

Conditional thesis: Worth pursuing if the Senior Staff role carries real UX vision authority across Gusto's four finance product areas and the scope can expand.

Abort trigger: The role is scoped as a senior IC executing inside product-manager-defined requirements rather than setting UX direction.

What changed: Cameron Wu, Head of Design for New Revenue Streams, publicly wrote that he's hiring this role and invited direct messages. He described the hire as a strategic thought partner setting UX vision across Business Money, Consumer Money, Payments, and Risk. The Greenhouse posting is live. Upgraded from Watch to Act Now on access-path clarity.

Why it matters: Wu's open invitation is the cleanest access path on this list.

Rubric: Company 10 (2/3/3/2 — 80+ person design org, pre-IPO with strong growth, design influence high, trajectory stable). Role 14 (2/3/3/3/3 — Senior Staff comp with $202K–$253K base plus RSUs, UX vision scope across four areas, strong craft depth, AI exposure through financial decision surfaces, strong portfolio value). Clears Act.

Access path: Wu publicly invited candidates to message him and the posting confirms the search is live. His DMs-open post is roughly three months old, so he may no longer be watching inbound from it. If nothing comes back within 48 hours, route through Greenhouse only and treat this as Act Soon.

Confidence: High on Wu as scope owner. His first-person hiring language is the strongest public ownership signal across all five Act Now entries.

Window: The Greenhouse posting is live. Monday tells you whether the DM channel still works.

Tier Playbook: Read Growth-stage platform playbook before outreach.

Battlecard status: Battlecard candidate — request before interview.

Move:

(a) Who: Cameron Wu, Head of Design, New Revenue Streams. Owns this search publicly. Amy Thibodeau sits above him as the function-level design sponsor.

(b) Warm path: Cold, but DMs-open lowers the barrier. DM is the primary channel; skip the connect-first sequence.

(c) Deviation from standard: DM Wu on LinkedIn, apply through Greenhouse in parallel, one follow-up at 5 days referencing the application. No DM response by Wednesday, route through Greenhouse only.

(d) Connection request: "Cameron — your Senior Staff Finance role maps directly to my background. At BCG DV, I designed Thermo Fisher mySupply ($20M+ margin, 100% adoption) and Allē (30M members, 3.2× redemption) from 0→1. Would love to discuss. junochen.com"

(e) Full outreach message:

Cameron,

Setting UX vision across four financial product areas — Business Money, Consumer Money, Payments, Risk — is the kind of scope I've spent my career building toward.

As Product Design Director at BCG Digital Ventures, I designed Thermo Fisher mySupply from zero: a pharma supply-chain platform that reached $20M+ margin impact and 100% adoption across six pharma partners in twelve months. High-stakes, regulated, no tolerance for error. At BCG DV I also redesigned Allē's dual-surface experience for 30M members, driving 3.2× redemption lift. Financial products where trust in the transaction is the design problem.

Most recently, as Head of Product at TinyFish, I shipped an enterprise AI platform from zero, which gave me production-level depth in how AI changes financial decision surfaces.

The strategic thought partner framing in your post is what drew me. I want a role where the designer owns UX vision across a product area.

Portfolio at junochen.com — the Thermo Fisher and Allē cases are the most relevant.

Juno

(f) What not to say: Don't lead with AI. Gusto's finance products aren't AI-native, and the AI experience is secondary here. Lead with the financial product track record.

Interview prep flags:

• Format: Portfolio review, a design exercise or critique session, and cross-functional conversations with PM and engineering leads.
• Portfolio lead: Thermo Fisher for high-stakes financial product design, Allē for consumer-facing financial UX at scale.
• Key question: "What's the relationship between the four finance product areas — are they converging toward a unified money experience, or staying distinct?"
• Leadership dynamic: Wu owns the scope, Thibodeau sponsors the function. The Senior Staff title means influence without formal authority, so show where you've already done that.
• Differentiator: You've built regulated financial products from zero with measurable margin impact, which is unusual at Staff IC level.

Siro — Director, Product Design

Conditional thesis: Worth pursuing if Siro's design surface is the behavior-change layer — how AI insight becomes a daily habit for sales reps — and the Director role carries real influence over that interaction model.

Abort trigger: The role is a UI execution seat on top of a data product defined entirely by engineering and data science.

What changed: CEO Jake Cronin recently described Siro as a change-management company, arguing that the bottleneck in AI adoption is human behavior rather than technology. He named four levers: skills, user conviction, role modeling, and formal mechanisms such as rituals and workflow integrations.

Why it matters: That thesis is your Trust essay applied to one vertical. Carrier IQ is the production version of the same pattern.

Rubric: Company 10 (AI-native core product, Series B with meaningful equity, accelerating — 100K reps adopted). Role 15 (3/3/3/3/3 — $250K base plus equity, end-to-end design ownership with direct founder partnership, hands-on craft across mobile/web/AI, AI-native exposure, highly differentiated portfolio value). Design influence ceiling is the unknown; thin design-org visibility at this stage means you may be the first senior design hire. Clears Act.

Confidence: Moderate. Cronin is the decision partner per the posting. No public Head of Design identified.

Window: Series B, CEO posting actively. Founder attention is narrow. Reach out by Wednesday.

Tier Playbook: Read AI-native playbook before outreach.

Battlecard status: Battlecard candidate — request before interview.

Move:

(a) Who: Jake Cronin, CEO and co-founder. Both the outreach target and the hiring authority.

(b) Warm path: Cold.

(c) Standard sequence. Comment substantively on the change-management post first. Founders respond or they don't; don't chase past one follow-up.

(d) Connection request: "Jake — your change-management framing for AI adoption matches my own work on trust architecture for agentic systems. I've designed AI products where the core problem is turning model output into user behavior change. Would value a conversation. junochen.com"

(e) Full outreach message:

Jake,

Your framing of Siro as a change-management company — that the bottleneck is human behavior, not technology — is the thesis I've been building around.

Through Agentic Labs I designed and shipped Carrier IQ, an InsurTech product that automates insurance quoting. The design problem wasn't the automation. It was getting agents to trust the output enough to change their daily workflow, which meant designing trust calibration at every step: what the user sees, what they can verify, when they delegate, what happens when the system is wrong.

I published a framework for this called "Trust Is the New Interface" — five handoffs that move a user from watching AI output to delegating decisions. The levers you described (conviction, role modeling, rituals, workflow integration) sit directly on that trust ladder.

Most recently, as Head of Product at TinyFish, I shipped an enterprise web agent platform from zero and worked through the production-level problem of embedding AI into existing work rhythms.

Your willingness to return to production code to understand AI-era bottlenecks tells me Siro values hands-on depth. That's how I operate.

Portfolio and essay at junochen.com.

Juno

Before sending: if the Inference-Aware UX or Intent-Based Interaction artifacts are published at junochen.com by then, link one directly in place of the general portfolio line. They show the interaction models underneath the essay.

(f) What not to say: Don't claim to understand field sales operations. You understand the interaction-design problem. Let Cronin fill the domain gap.

Interview prep flags:

• Format: Series B with a thin design org means a loose process. Likely a direct conversation with Cronin, possibly a product critique. Founders at this stage evaluate taste and judgment far more than process.
• Portfolio lead: Trust essay as conceptual opener, Carrier IQ for production proof. Bring the forward-looking visual artifacts if they're live.
• Key question: "Of the four levers you named — skills, conviction, role modeling, formal mechanisms — which one is the current design bottleneck?"
• Leadership dynamic: Cronin is CEO and hiring authority, with no public Head of Design. You may be interviewing for scope definition as much as for the work. Ask early: "Is this the first dedicated design leadership hire, or is there an existing team?"
• Differentiator: You have a published framework for the exact problem Cronin described publicly, and three shipped products that prove it works in production.

Handshake — Staff Product Designer, Handshake AI

Conditional thesis: Worth pursuing if the Handshake AI product is building agentic recruiting workflows where the design surface is the agent's behavior rather than a UI layer over matching algorithms.

Abort trigger: The AI product is a recommendation feed with no design influence over model behavior, or the Staff role is scoped as a feature designer inside a PM-defined roadmap.

What changed: Handshake posted three Staff Product Designer roles simultaneously — Handshake AI, Autonomous Recruiting, Student Experience. Three at once signals org-wide buildout with budget behind it.

Why it matters: Pre-IPO, AI a primary strategic bet, and the AI role sits on your Agentic AI pillar. A wrong AI recommendation here lands on someone's career, which makes the trust-design problem harder than in most AI products and makes your framework more directly applicable.

Rubric: Company 10 (AI a primary strategic bet, pre-IPO, VP Design in place and building out, stable-to-accelerating trajectory). Role 14 (2/3/3/3/3 — Staff comp with pre-IPO equity, AI product scope, hands-on craft, AI-native exposure, highly differentiated portfolio value). Clears Act.

Confidence: High on Gabe Schindler as scope owner for Handshake AI, confirmed as Head of Design for that product via the Products That Count interview. His authority over the other two roles is unconfirmed. May-Li Khoe (VP of Design) is the function-level route. Focus on the AI role through Schindler.

Window: Fresh cluster, budget apparently approved. 3–4 weeks.

Tier Playbook: Read Growth-stage platform playbook before outreach.

Battlecard status: Battlecard candidate — request before interview.

Move:

(a) Who: Gabe Schindler, Head of Design, Handshake AI.

(b) Warm path: Cold.

(c) Standard sequence. Engage with the Products That Count piece or his LinkedIn content.

(d) Connection request: "Gabe — your Products That Count piece on AI-era design tracks with my work on trust architecture for agentic systems. I've shipped AI products from 0→1 and published a framework for human-agent handoffs at junochen.com. Would love to connect."

(e) Full outreach message:

Gabe,

The challenge you described in your Products That Count interview — building AI products where design decisions shape what the AI does, not just how it looks — is the problem I've been working on across three AI products and a published framework.

Through Agentic Labs I shipped Carrier IQ (InsurTech quote automation), Brand Pulse (real-time brand sentiment), and Retail Velocity (CPG field intelligence), all live at junochen.com. Each one needed a trust layer designed deliberately: what users see about the AI's reasoning, when they can override it, how the system earns enough confidence to change daily behavior.

I published that thinking as "Trust Is the New Interface," a five-handoffs framework for human-agent trust calibration. Most recently, as Head of Product at TinyFish, I shipped an enterprise web agent platform and worked with agent traces, auditability, and governance in production.

Handshake AI sits at a high-stakes intersection: AI-mediated decisions about people's careers. The trust architecture there is harder than in most AI products because the consequences of a wrong recommendation are personal.

Portfolio and essay at junochen.com.

Juno

Before sending: if the Human-Agent System Design or Agent Infrastructure as UX artifacts are live, add one direct link. They're the strongest thing you have for this particular reader.

(f) What not to say: Don't claim familiarity with Handshake's recruiting product unless you've used it. Position around the trust-architecture problem, not the domain.

Interview prep flags:

• Format: VP Design and Head of Design layers means a structured loop. Portfolio review with Schindler, cross-functional sessions, likely a VP-level conversation with Khoe.
• Portfolio lead: Trust essay, Carrier IQ, Brand Pulse, plus the forward-looking artifacts if published.
• Key question: "How much of the Handshake AI design surface is the model's behavior versus the interface around it?"
• Leadership dynamic: Schindler owns the AI product, Khoe owns the function, and you'll need both. Trust architecture for Schindler; Alibaba and enterprise-scale leadership for Khoe if she's in the loop.
• Differentiator: You can walk through how trust calibration works at each handoff — the published framework and three shipped products make that argument specific and provable.

Act Soon

Webflow — Staff Product Designer, Agentic CMS

Conditional thesis: Worth pursuing if the Agentic CMS product gives the designer real influence over how AI agents create and manage web content.

Abort trigger: The role is a CMS feature designer with AI as a peripheral enhancement.

Erica Deahl joined roughly five months ago as Senior Director of Product Design, which is the title the posting names as reporting manager. She has posted about AI helping teams express intent and about bridging design and code. Strongest likely owner, not publicly confirmed for this requisition. Locate her own LinkedIn profile before you write — the sourced link routes to a colleague's profile that carried her announcement.

Tier Playbook: Read Growth-stage platform playbook before outreach.

Battlecard status: Battlecard candidate.

Connection request (to Deahl): "Erica — the Agentic CMS Staff Designer role maps to my work on trust architecture for AI systems. I've shipped three AI products (live at junochen.com) and published a framework for human-agent handoffs. Your framing of AI bridging design and code is where I want to work."

Interview prep: Lead with the Trust essay and Agentic Labs. Ask: "Is the Agentic CMS designing what the AI creates, or designing the interface around AI-created content?" The answer tells you which construct this role is actually screening for.

DoorDash — Staff Product Designer, New Bets

Conditional thesis: Worth pursuing if the role closes at I6, the top of the $176.8K–$260K band, and Meals for Work carries genuine zero-to-one scope.

Abort trigger: Budgeted at I4/I5, or "New Bets" turns out to be a feature team inside an established product.

The posting publishes three internal levels (I4–I6), so seniority is unsettled. Qixing Zheng, Senior Product Design Manager for New Bets, has hired for this exact scope before and recently posted about AI-era design practice. Strongest scope-matched route.

Tier Playbook: Read Enterprise platform playbook before outreach.

Battlecard status: Battlecard candidate.

Connection request (to Zheng): "Qixing — the Staff Product Designer role on Meals for Work maps to my 0→1 background. I've built high-stakes products from zero at BCG DV (Thermo Fisher, Equinox+, Red Cross) and recently shipped enterprise AI from 0→1. Would love to learn more about the scope."

Interview prep: Lead with Equinox+ (0→MVP in three months) and Thermo Fisher. Ask about level in the first conversation: "The posting spans I4–I6 — what level is the team hiring for?" That answer decides whether this stays in your queue.

Watch

OpenAI — Product Design Lead, Growth — Codex

Expires in seven days. This posting hits day 43 on September 30, crossing the deprioritize threshold. Nothing public from Ian Silber or any OpenAI recruiter confirms whether the slate is still building. LinkedIn shows 200+ applicants and a display timestamp newer than the ATS publication date, though that could be platform redistribution rather than a refresh.

As noted in Issue #12, Silber is a function-level route, not the confirmed hiring manager. A recruiter is the better source for slate status.

Action: Apply through the ATS by September 30 if you haven't already. No response by October 3, move it to Deprioritize.

Deprioritize

Anthropic — Evals & Prompts. Stood down in Issue #11. The technical capability gate — production evaluation design, prompt engineering depth — is a qualification boundary your current portfolio can't clear. Paused until the portfolio evidence changes.

Brex. Killed in Issue #11. The acquisition destroyed the pre-IPO equity thesis. Removed.

Impiricus. Attractive AI-native healthcare company, but the comp floor sits below the $200K cash threshold. Removed unless the comp structure changes.

Stripe, Ramp, Rubrik, Samsara, Babylist. All have live ATS pages masking postings 43+ days old with no refresh signal. These are ATS artifacts, not opportunities. Take them out of your daily scan; fresh postings will re-enter through your parallel job alerts.

Window Status Changes

Upgraded: Figma, Motive, Siro, Handshake (new to Act Now). Gusto (Watch → Act Now on access-path clarity).

Expiring: OpenAI Growth–Codex crosses the 43-day threshold September 30. Apply by then or let it go.

Continuing holds: Anthropic Evals (paused), Brex (removed), Impiricus (removed).