The Head of Design, USP role posted two days ago. Pipeline is thin. The buyer left a trail of published writing that tells you exactly how she evaluates. First week of a senior design posting is when the hiring manager reads inbound directly. By week two, the recruiter pipeline delivers screened candidates and the committee anchors on whoever's already in process.
Event recovery
2021: Amy Thibodeau joined Gusto as Head of Design and Research. Previous: Shopify, where she led a 130-person cross-functional team, launched Polaris, built Platform UX, founded Design Ops.
January 2022: Designer Fund profiled Gusto's design org at roughly 60 designers. Amy was already titled Chief Design Officer. Her Gusto author page still says "Head of Design and Research," so either the promotion happened within a year of joining or different sources use different titles. The signal is the same either way: design holds executive authority at Gusto and has since at least early 2022. The priorities she named that year: design systems, IC leadership, research practice, product-strategy influence. Infrastructure work, all of it.
December 2025: Amy held a design-team onsite. She wanted every designer to ship a pull request. The transformation essay calls this the first real signal. Before December, there were "false starts."
January 2026: Katie Kovalcin and a design system engineer built Workbench MCP and Gusto Sandbox. This is the tooling layer that made AI-native design workflows possible inside Gusto's codebase.
February 2026: Amy announced at a design all-hands that every designer should transform their way of working by June 1. Static Figma files should no longer be the default. Not a suggestion. A deadline.
March 24, 2026: Katie and engineers began building Cofounder at an onsite. A researcher started concept testing the prototype the same day. Katie personally shipped roughly 150 PRs over the next 11 weeks.
March 27, 2026: Gusto posted an Application Systems Engineering Manager role whose content names Unified Service Platform and places the Payoffs team inside it. Earliest primary evidence that USP existed as a named org.
May 7, 2026: Gusto posted a Senior Manager, Agentic Strategy & Operations inside Customer Experience. Tied to Service Transformation and scaling Gus, Gusto's AI assistant. The posting says the function is "still being defined." Shared language with the later USP design role: AI governance, escalation, trust, human judgment, service quality.
June 4, 2026: Amy published "How we build with AI at Gusto" under her own byline. Four principles. The test she named:
"Does a business owner trying to run payroll on a Thursday afternoon actually need this AI-powered solution?"
She asked, explicitly, how Gusto should show what an AI agent is doing, design intelligent escalation when something is handed back to a human, and preserve agency when automation makes consequential decisions.
June 10, 2026: Katie Kovalcin published "Evolving from designers to builders." Katie wrote it. Amy is the protagonist. The essay names Amy as CDO, mandate setter, working-group member, and sponsor of the transformation. It documents the shift from traditional design org to AI-native one within a single quarter. The design system team repositioned as "Builder Enablement." Gusto began building AI into performance expectations, interviewing plans, and career frameworks.
July 22, 2026: Gusto posted Head of Design, Unified Service Platform. The role leads three existing designers (product design and conversation design), sits peer-to-peer with PM, Engineering, and Data leaders on the "USP quartet," and owns design for AI-driven support, multi-channel service, and human expertise when AI is not enough. The posting says Design at Gusto is over 80 people.
July 23, 2026: The posting was updated. One-day revision, not a search restart.
The gap in the record
No public source names the executive who owns USP. The posting doesn't name a hiring manager or reporting line. Gusto's CPO title has a conflict across sources: Chris Cosgrove's author page identifies him as Chief Product Officer, while The Org's unverified page lists Tomer London as Co-Founder & Chief Product Officer. I cannot resolve this from available evidence.
More telling: no public source names a prior Head of Design for USP. No departed USP design leader appears anywhere in the record. The engineering and service-transformation roles posted months earlier reference USP, but neither references an existing design lead. Three designers were already working inside USP. They did not have a dedicated Head of Design.
New seat, not a backfill.
The pattern
AI principles (June 4) → transformation essay (June 10) → Head of Design posting (July 22). These two publications are the evaluation rubric for the hire, not background context.
Amy's AI principles post asks the exact questions the USP Head of Design will need to answer: How do you show what an AI agent is doing? How do you design escalation when something gets handed back to a human? How do you preserve agency when automation makes consequential decisions about payroll, benefits, and tax compliance? The transformation essay establishes that Gusto's design org already operates as builders shipping code. The posting then asks for a leader who can work inside that operating model while owning the surface where AI wrongness hits hardest: real businesses, real money, real consequences.
A buyer who publishes the thesis before posting the role is running a recognition screen. Does this candidate's framework map to ours, or will they arrive with a competing model we'd have to reconcile? Amy ran this same play at Shopify. Built the infrastructure first (Polaris, Platform UX, Design Ops), then extended into the harder product problems. She has done this sequence before. She'll recognize alignment faster than a first-time CDO would.
The vision is settled. The hire is for execution alignment.
In an earlier piece, I classified Gusto under CPO/VP Product evaluation and described the design problem as "AI wrongness, exception movement between systems and teams." That framing assumed the buyer was a product executive evaluating whether design could reduce cognitive load. The June publications overturned it. Amy is a CDO who already transformed her 80-person org, already published the AI principles, and is now hiring for the specific surface where those principles get tested hardest. Different buyer type, different evaluation lens. She's asking whether you can operate inside the model she already built, and she'll know within the first five minutes of reading your materials whether your framework maps to hers.
Prediction
Amy Thibodeau is the buyer or the primary gatekeeper. She authored the AI principles, sponsored the transformation, leads Core Experiences (which includes AI Platform and Design Systems), and is the named CDO across every available source. Even if USP formally reports through a CPO or CX executive, the design evaluation runs through Amy. The posting's language about AI-native design, builder culture, and the trust problems of AI-driven service is her language, published under her name six weeks before the role went live.
High on Amy as gatekeeper, moderate on Amy as direct hiring manager. What would have to be true for this to be wrong: USP sits entirely outside Amy's org, under a CX or product executive who independently owns the design hire. The Agentic Strategy & Operations role sitting in Customer Experience, not Design, suggests some cross-functional ownership. But the posting is tagged to Design, the role leads designers, and the design thesis it describes is Amy's published thesis.
The mandate is formed, not forming. The June 1 transformation deadline has passed. The design org already shifted to AI-native workflows. The AI principles are published. The USP Head of Design is being hired to execute inside a system that already exists.
Mirror the framework. Do not arrive with a competing one.
What this means for your outreach
Contact Amy Thibodeau directly. LinkedIn. She has a public profile and a clear publishing footprint. Her Shopify background and design-community visibility make semi-warm paths likely. Check your mutual connections before going cold.
The hook is vocabulary convergence. Amy's AI principles post asks how to design intelligent escalation, preserve agency, and show what an agent is doing. Your Trust essay names these as the In-Progress handoff, the Decision Gate, and the Output Review. You didn't coordinate this language. You arrived at the same framework independently. That's the opening.
Lead with the Trust essay, not the portfolio. The portfolio proves you can execute. The Trust essay proves you already think the way Amy thinks. For a buyer with a formed thesis, framework alignment is the first screen. Craft evidence is the second.
The "designer to builder" bridge is your TinyFish narrative, reframed. Amy's thesis is that designers should become builders who ship code. You literally did that. You moved to Head of Product at an enterprise AI company and shipped three products in three months. The transition that usually requires explaining becomes proof of alignment with this specific buyer. Don't defend the move. Name it as the same instinct Amy acted on for her whole org.
Move before Monday. Senior design leadership postings at growth-stage companies draw heavy early interest, and the evaluation dynamics shift fast. In the first week, the hiring manager reads inbound directly. By week two, the recruiter pipeline is delivering screened candidates and the committee starts anchoring on whoever's already in process. Your positioning advantage is strongest before that anchoring begins. The Trust essay vocabulary match, the builder narrative, the agentic service design proof. All of it depreciates the moment someone else gets into the room first.
- Gusto's CPO identity conflict: Chris Cosgrove's Gusto author page names him Chief Product Officer, but The Org lists co-founder Tomer London in the same title — resolve before any outreach that references product-org ownership of USP.
- Agentic Strategy & Operations role: The Senior Manager posting inside Customer Experience says the function is "still being defined" and shares escalation/trust/governance language with the USP design role — watch whether this CX-side hire fills before or after the Head of Design, because the sequence reveals who actually owns the service-transformation mandate.
- Kelly Griggs as adjacent design leader: The Org's unverified page lists Kelly Griggs as Head of Design for Growth, CX Platform, AI, Payments & Risk, and Service Design — a scope that overlaps USP's territory enough that she may sit on the hiring panel or be the peer you'd need to map against.
- Gusto's design-role cluster timing: The Greenhouse API snapshot shows six open Design roles, but the five non-USP postings range from August 2025 to April 2026 in first-published dates — none are fresh, which reinforces that the USP Head of Design is a deliberate new seat, not part of a broader hiring wave.