Phase 1 — The Moment
Gusto's design org completed an AI-native transformation by June 1, 2026. Every designer ships pull requests. The design systems team renamed itself "Builder Enablement." The Head of Design, USP posting went live July 22 — the first design leadership hire after the transformation landed. Post-transformation mandate hire.
Read the negation language. The posting tells you what this role is NOT before it tells you what it is. "Outputs that should not be sent." "Graceful failure." "Intelligent escalation." That much space devoted to what shouldn't happen is a confession. The USP sits behind Gus, Cofounder, Assisted Payroll Prep, and the ChatGPT and Claude/Slack integrations. Every AI product Gusto ships routes through this platform when something breaks. The mandate: own the boundary where AI confidence ends and human judgment begins.
Three designers. One platform. Inside an 80-person design org. Manager-level team size, not a manager-level mandate. Full assessment below.
The quartet structure matters more than the team size. The posting gives you peer-to-peer authority with PM, Engineering, and Data. "Highest-leverage hands-on design work" plus standard-setting responsibility for AI-native service design across the platform. IC+manager hybrid scoped to the single highest-stakes surface in Gusto's product.
Expansion signal is legible. Cofounder launched June 2. Claude/Slack shipped April 2026. Assisted Payroll Prep debuted at the Spring Showcase. Each new AI surface generates failure modes that route through USP. The team grows if the AI bet works. It stays at 3 if it doesn't.
One craft question to resolve early. The designers-to-builders transformation means design reviews may happen in code, not Figma. Amy frames this as elevation ("builders, not pixel-pushers"). The operational reality could mean craft critique gets compressed into PR review. Have an answer ready: "I'm excited about designers shipping code. How does the team protect craft quality and design critique in a PR-first workflow?"
My read: mandate-building opportunity, not a scope trap. But the risk that it stays scoped to 3 is real. Ask about expansion plans in the first conversation. A vague answer is a yellow flag.
Buyer. Amy Thibodeau is Gusto's Chief Design Officer and Head of Core Experiences (AI Platform, Design Systems, Reporting, Mobile and Comms). She authored the AI principles post that names the exact design questions this role answers: agent visibility, intelligent escalation, preserved agency. She sponsored the designers-to-builders transformation. An unverified directory listing shows Kelly Griggs as Head of Design for Growth, CX Platform, AI, Payments & Risk, and Service Design — a title cluster that overlaps USP territory. Kelly may be the direct hiring manager. I cannot confirm the reporting line from public sources. Outreach goes to Amy. Her public record gives the strongest hook material, and she's the executive most visibly connected to the mandate. If Kelly owns the hire, Amy routes it.
Comp.
| Location | Base Range | Notes |
|---|---|---|
| Denver / Remote | $204K–$238K | Clears $200K threshold |
| SF / Seattle / NYC | $240K–$280K | Clears $250K threshold |
Plus RSUs. Gusto's total rewards page describes a "Cash-First Mindset." Late-stage pre-IPO equity adds upside. Score: 2 (remote) to 3 (metro).
Warm path. None found. No mutual connections, no shared groups. Amy's AI principles post (June 4, 2026) is the best cold-to-current bridge. It's 50 days old, outside the 4-day recency window, but it names the exact design questions the posting answers. Reference it as the intellectual anchor, not as breaking news.
Window. Posting is 2 days old (posted July 22, today July 24). Maximum freshness. First-week outreach lands before the pipeline fills. Growth-stage platform searches run 6–10 weeks from posting. You have 5–7 weeks of full advantage, but week one is when your message gets the most uncontested attention.
Urgency verdict: Act Now.
Phase 2 — Portfolio Mapping
The posting independently arrived at the Trust essay's vocabulary. "Outputs that should not be sent" is the Decision Gate handoff. "Intelligent escalation" is the In-Progress handoff. "Preserved agency" is the trust ladder. They built this language from the product side without knowing your framework exists. That convergence is the strongest positioning asset in this search. No other candidate walks in with a published framework that mirrors the buyer's own words.
Narrative fit: A business owner runs payroll. The system flags an anomaly. The owner must decide: trust the flag, override it, escalate. That's the Decision Gate with someone's employees' paychecks on the other side. Your Trust essay names this boundary. Carrier IQ proves you've designed it where wrong outputs carry regulatory consequences. Alibaba proves you've built trust architecture at enterprise scale where the stakes are six months of inventory spend. TinyFish proves you're doing it in production right now, tracing agent failures daily. The combination is specific to you.
- Trust essay leads. Five handoffs map directly to USP's design surface.
- Carrier IQ supports. InsurTech quote automation in a regulated industry. Wrong coverage selection isn't a design preference — it's a legal liability. Demonstrates all five handoffs.
- Alibaba supports. $50B+ GMV platform, +20% daily transactions, +2.2pt NPS. Structural trust gap diagnosis, mandate-building, measurable outcomes at enterprise scale.
- TinyFish bridges. Head of Product, enterprise web agent platform (Series A). Three products in three months. Agent traces, auditability, governance in production daily. Currency, not portfolio proof.
One objection. "Why would someone with this background take a 3-person team?" Seniority-fit anxiety, overqualified variant. Hard because the team size is genuinely small relative to Alibaba's scope. Counter: The USP is the trust layer for every AI product Gusto ships. The Trust essay and Carrier IQ prove this specific design problem, not team size, is what you've been building toward. The mandate quality matches the trajectory. Lead with that.
Positioning differentiator. The only candidate with a published trust framework whose vocabulary independently matches the posting's own language.
Phase 3 — The Outreach Package
First Contact Message
To: Amy Thibodeau · Via: LinkedIn · Subject: The output that should not be sent
Amy — your AI principles post asks the question I've spent the last year answering from the design side: what do you show a business owner about what an agent is doing behind the scenes, and how do you design intelligent escalation when something gets handed back to a human?
I published a framework for this called "Trust Is the New Interface," mapping five handoffs between AI systems and human judgment. The framework came from designing Carrier IQ at Agentic Labs — automated insurance quoting where a wrong coverage selection has regulatory consequences — and from my current work as Head of Product at TinyFish, where I deploy enterprise web agents in production and trace every failure mode between what an agent did and what a user experienced.
Your Head of Design, USP posting describes the design problem I've been building toward. Particularly the line about "outputs that should not be sent." I'd welcome 20 minutes to discuss how the five handoffs map to Gusto's service layer.
Juno Chen
Cover Letter
The hardest design problem in Gusto's Unified Service Platform is what happens at the boundary where a business owner decides whether to trust what the system just produced — an anomaly flagged by Assisted Payroll Prep, a compliance recommendation from Cofounder, an escalation path when Gus reaches the edge of its confidence. Each of these is a trust decision with real financial consequences for someone who doesn't have a back-office team to catch mistakes.
I've been building toward this problem from several directions. At Agentic Labs, I designed Carrier IQ — InsurTech quote automation where wrong coverage selections carry regulatory consequences — building all five handoffs between agent action and human judgment: intent-setting, in-progress visibility, output review, decision gates, and feedback loops. The framework is published as "Trust Is the New Interface" at junochen.com. At Alibaba.com, I led the B2B platform redesign as Head of Design and Research, architecting trust signals across a $50B+ GMV platform where a buyer commits six months of inventory on the strength of a screen (+20% daily transactions, +2.2pt NPS).
I'm currently Head of Product at TinyFish, an enterprise web agent platform (Series A), where I shipped three products in three months and work daily with agent traces, auditability, and governance in production. I moved to product to build AI-natively from zero. I'm returning to design because I want to apply that technical depth to a specific, high-stakes domain — and your posting's language about "outputs that should not be sent" and "graceful failure" describes exactly the design surface I want to own.
Portfolio and trust framework at junochen.com.
Resume Emphasis Guidance
- Lead with: Agentic Labs, Carrier IQ specifically. Regulated agentic automation, all five trust handoffs. Direct analog to USP's AI-human handoff mandate.
- Second: Alibaba.com. Head of Design and Research, enterprise trust architecture, structural gap diagnosis, measurable outcomes. Proves mandate-building at scale.
- Third: Thermo Fisher mySupply. 0→1 in regulated enterprise, exception-first design. Maps to USP's exception-handling surface.
- Highlight separately: "Trust Is the New Interface" essay. Give it its own line. This is the vocabulary convergence asset.
- TinyFish in header: "Head of Product, TinyFish (enterprise web agent platform, Series A)." One line: shipped 3 products in 3 months, agent traces and governance in production daily.
- De-emphasize: Equinox+ (consumer, low relevance). Move Red Cross and Allē below the fold. Strong cases, wrong buyer.
Engagement Intelligence
Ask:
- How does the USP team's mandate intersect with the other AI product teams (Gus, Cofounder, Assisted Payroll Prep)? Are those teams USP's customers, or does USP own the end-to-end service experience?
- Does the Head of Design for USP have a seat in the AI product strategy quartet, or does the role report through a layer before reaching Amy?
- What does team expansion look like if the AI bet continues to accelerate? (A vague answer here is the yellow flag on scope.)
Don't say: Don't lead with the Trust essay as a framework pitch. Lead with Gusto's specific products and let the framework surface as the answer to their named problems. Don't question the designers-to-builders transformation. It's Amy's signature initiative.
The posting's negation language is the real brief. Most candidates will read it as a list of responsibilities. Read it as a list of failures the current system has already produced. That reframe changes what you say in the room.
Phase 4 — Window Summary
| Action | Deadline | What degrades without it |
|---|---|---|
| Send first contact to Amy Thibodeau | Monday July 27 | First-week advantage. Pipeline fills by week 2. |
| Submit application via Greenhouse with tailored cover letter | Monday July 27 | Application timestamp matters for ATS sorting. Send same day as outreach. |
| If no response, follow up with one new signal hook | Monday August 4 | After day 8, the search has likely moved to active screening. |
Post-Outreach Signals
- Response within 3–5 business days = normal for growth-stage platforms.
- Silence past 7 business days = likely in process with other candidates. One follow-up at day 8, then redirect energy.
- Recruiter screen scheduled on first contact = fast-moving search. Prioritize prep immediately. Prepare the junochen.com walkthrough framed around the Trust essay's five handoffs mapped to Gusto's specific AI products (Gus, Cofounder, Assisted Payroll Prep).
- If asked for portfolio walkthrough: Open on Carrier IQ, not Alibaba. The buyer is evaluating AI trust design judgment, not enterprise scale. Alibaba is the credibility anchor, not the lead.
| July 27 |
|---|
- Gusto's Cofounder product surface: The Cofounder launch post names 20+ pre-built automations with approval gates and permission controls, which maps directly to the Decision Gate handoff and could sharpen your portfolio walkthrough framing.
- Amy's compliance design language: Her Gusto Embedded compliance discussion frames trust as "what, when, and why" for small businesses, a vocabulary pattern worth mirroring if the conversation moves beyond AI into Gusto's broader design philosophy.
- Kelly Griggs reporting line: The unverified org directory listing Kelly as Head of Design for CX Platform, AI, and Service Design is the strongest public clue to the USP reporting structure, but needs confirmation in the first conversation.
- Dual CPO ambiguity: Gusto's company news lists both Tomer London as Co-Founder & CPO and Chris Cosgrove as Chief Product Officer, which could affect where USP sits in the product org and who the product-side buyer actually is.