The recruiter who screens you and the design leader who hires you are running different evaluations. The recruiter classifies: does this person's trajectory match the pattern for this role? The buyer evaluates: does this person's judgment match the problem we're solving? The recruiter goes first. And the language that wins the buyer can get you filtered out by the recruiter, because the recruiter is not evaluating whether you can do the job — they're classifying whether you look like the kind of person who does.
That changes what counts as evidence at each layer, and it changes what you say first.
What the Recruiter Screen Actually Covers
Recruiter screens at the Director+ level cover a predictable surface. Atlassian publishes it explicitly: 30 minutes on background, skills, goals, career aspirations. Capital One describes a similar scope. GitLab adds "your work and approach to product design" but reserves strategic judgment, organizational influence, and cross-functional credibility for later design-led interviews.
Portfolio attribution, design judgment under ambiguity, systems thinking, whether you can lead a team through a hard problem — all assigned to the hiring manager interview and portfolio review. Atlassian's published process makes the handoff explicit. OpenAI's reported process gives the portfolio and ambiguous-problem assessment to the design hiring manager.
The recruiter gathers eligibility signals. The buyer evaluates capability.
What the recruiter actually filters on:
Title equivalence. Atlassian's own application guidance tells candidates to standardize non-equivalent titles by drawing a clear connection to the company's corresponding title. They are telling you the gate exists. "Head of Product at TinyFish" does not contain the word "design," and the recruiter will not do the translation for you.
Keyword and skill match. LinkedIn Recruiter filters by title, skills, years of experience, industry, tenure, and prior companies. Whether a specific company uses every available filter is unknowable from outside. The system makes pattern matching technically effortless, so the burden of translation falls entirely on you.
Career legibility. A recruiter processing 40+ candidates for a Director of Product Design role carries a mental model of what that career looks like: design IC, senior designer, design lead, design manager, director. Your path — consulting studio, B2B enterprise head of design, product-titled AI role — requires explanation that a 30-minute screen may not leave room for. Executive-search research confirms that search firms target by employer reputation and job title rather than accomplishments. Cross-functional breadth registers as valuable range or commitment ambiguity depending on who is reading it and how much time they have.
Your Three Friction Points
The product title. "Head of Product" in a keyword-filtered pipeline is a gap. In a 30-minute screen, it requires a sentence of translation you must deliver before the recruiter forms a category for you. Deliver it in the first two minutes: "I moved to product to build AI-natively from zero, shipped the agentic platform in three months, and returned to design to apply that depth to a specific vertical." That sentence explains the title, establishes AI credibility, and preempts the "why are you applying for a design role" question before it forms.
The consulting-studio origin. BCG Digital Ventures is not a household name the way Google or Figma are. A recruiter scanning for company pedigree may not recognize it. When you name BCG DV, attach the client outcome immediately: "At BCG Digital Ventures, I led the design of Thermo Fisher's digital supply chain — $20M+ margin recovered, six pharma partners, 100% adoption." The client name and the number do the recognition work that the studio name alone cannot.
The non-linear arc. Consulting, enterprise, startup, search. Each move made sense for the reason you made it. A recruiter reading a resume in 90 seconds sees four different contexts in thirteen years and may read instability rather than range. Your resume header should impose the through-line before the recruiter constructs their own: design leader who has built at enterprise scale (Alibaba, $50B+ GMV), in regulated verticals (Thermo Fisher, Red Cross), and in production AI (TinyFish, agentic platform 0→1).
How to Read Which Screen You're In
Every reviewed process includes background and experience in the recruiter screen. The question is what happens after the background pass.
Pattern-matching screen. The conversation stays at equivalence and eligibility. Title, years, industry relevance, compensation expectations, timeline, why this company. Follow-up questions probe whether your experience maps to the posting's keywords. You will hear some version of "how does your experience at [company] relate to this role" — a classification question, not an evaluation question.
Briefed screen. The recruiter asks at least one question that requires you to describe a design choice, not a career fact. OpenAI's reported screen includes "What is your proudest design project?" and whether you can push code. GitLab's screen includes "your work and approach to product design." Still surface-level compared to what the buyer will ask, but the recruiter has been given criteria beyond title match.
What to do with this read. In a pattern-matching screen, make the trajectory legible in the recruiter's existing categories. In a briefed screen, you have a narrow window to plant a signal that travels forward — something the recruiter can repeat in their debrief that is more specific than "strong background." One sentence about the Trust essay's five-handoffs framework, or the Agentic Labs apps being live production systems with real APIs. Give the recruiter something to carry into the room.
How the Buyer Tier Reshapes the Gate
The buyer's priorities determine what happens after the recruiter screen, but they also determine what the recruiter screen is calibrated to find. A recruiter briefed by an AI-native design leader is listening for different eligibility signals than one briefed by an enterprise transformation sponsor. Knowing the buyer behind the gate tells you which version of your eligibility to make visible at the gate itself.
AI-native startup (OpenAI, Anthropic, Midjourney)
The gate is thinner but more idiosyncratic. OpenAI has used dedicated product-design recruiters. Anthropic's public recruiting roles are specialized by domain — AI Research, Infrastructure, Security — and design may route through a broader product recruiter whose design literacy is uncertain. Midjourney's Design Lead role reports directly to the CDO; no recruiter process is publicly visible.
The recruiter may or may not understand design seniority, but they will screen for AI-native credibility. Your TinyFish bridge sentence is the eligibility signal here. Not optional.
Silber, OpenAI's head of design, says he evaluates curiosity, prototyping, composable primitives, a point of view about the medium. What Silber actually evaluates — based on the full pattern of his public criteria — is whether your curiosity has already produced thinking that maps to the problems OpenAI is working on right now. "Curious" is the stated filter. "Already thinking about this" is the actual one. The tell: an AI-native buyer who is interested engages the design problem you named in your outreach — pushes back on it, extends it, redirects it. One who is processing you procedurally asks about your team size and reporting structure. Anthropic adds a mission layer — a former recruiter advised candidates to explain why AI safety matters to them. Pass the gate with AI production credibility; win the buyer with the forward-looking artifacts and the Trust essay — proof that you've already been working on their problem.
Growth-stage platform (Gusto, Headway, Amplitude)
The gate is more structured. Gusto integrated Product and Design recruiting into one team, and a talent partner personally reviews profiles for senior design roles. More design context at the gate, but also more specific operational screening.
Gusto's CDO has published AI design principles around customer problems, user control, and visible escalation. That's the stated frame. The actual evaluation surface is production proximity: the design org has publicly restructured evaluation to require building and shipping — adding AI expectations to interviews, embedding code contributions into career frameworks, and requiring designers to ship pull requests. A candidate whose recent work lives entirely in frameworks or strategy documents will not clear that bar. The stated criterion is "AI-native thinking." The actual criterion is "have you built something that runs." The tell: the growth-stage buyer who is seriously evaluating asks what you shipped and how it works in production. The one filling a pipeline slot asks what your design process looks like. Your Agentic Labs apps — live, solo-built, real APIs — are the proof that survives both the gate and the buyer. Lead with the Trust essay as installable methodology; support with Alibaba's mandate-building proof.
Enterprise (Capital One, Atlassian, Salesforce)
The gate is the most formalized. Capital One maintains a Design Talent Acquisition team with recruiters who screen, advise hiring managers, and negotiate offers. Atlassian publishes a full design interview handbook that separates the recruiter conversation from every subsequent evaluation stage.
Standardize your title to their language. State years of experience and relevant industries. Attach outcomes to every role. The recruiter here is classifying your eligibility for a structured pipeline.
Capital One's AI-in-XD mandate says it wants operating models, workforce transformation, business cases, measurable value. The stated frame is transformation strategy. The actual evaluation — consistent across enterprise design leadership searches — is organizational navigation: can you listen before prescribing, speak in business language, build cross-functional credibility, and move a several-hundred-person org incrementally without breaking trust. The mandate is the design org itself, not a product. The tell: the enterprise buyer who cares about the answer asks how you changed something inside a large organization — how you dealt with resistance, built alignment, earned influence you weren't handed. The one running a checklist asks whether you've managed a team of a certain size. Lead with Alibaba's mandate-building proof and the Trust essay as the framework you'd install.
For the full buyer-tier decode — adoption vs. control tensions, competitive candidate archetypes, post-outreach timing — see Issue #6 and the quality-under-acceleration buyer in Issue #7.
Calibrating the First Message
When you write to a recruiter, lead with legibility. Translated titles, recognizable client names, numbers.
When you write to a hiring manager directly, lead with the design problem their company is solving and why your thinking maps to it.
When you don't know who reads the message first — and you often won't — write the first sentence for the buyer and the second sentence for the recruiter. The hook is the problem you've been working on. The next line is the proof you've shipped it, in language a recruiter can classify and pass forward.
- Gusto's code-shipping requirement: Gusto publicly reported moving every designer to ship pull requests and restructuring career frameworks around AI expectations, which means the recruiter screen for the Head of Design, Unified Service Platform is likely calibrated to filter for production proximity before the CDO ever sees the candidate.
- OpenAI's recruiter specialization gap: Bobby Morgan, who publicly recruited product designers for OpenAI, left for Abridge, leaving the current number of dedicated design recruiters at OpenAI uncertain and potentially changing how design-literate the initial screen is for the Growth–Codex role.
- Capital One's Design Talent Acquisition team: Capital One recently posted a recruiter role specifically within Design Talent Acquisition, confirming that the AI-in-XD Director search routes through a design-specialized pipeline rather than a general enterprise recruiting function.
- Anthropic's mission-screen layer: A former Anthropic recruiter publicly advised candidates to explain why AI safety matters to them, suggesting the recruiter gate at Anthropic tests mission alignment as an eligibility criterion before any design evaluation begins.