Every Director+ search will test whether you are hands-on or a leader. But companies encode that test differently depending on what they are actually buying, and the title on the posting is an unreliable guide. I count four distinct role configurations across your target list, each running a different scorecard and requiring different evidence from your portfolio. For some of them, your background has limits that no reframe can fix.
Tier shifts the vocabulary — an AI-native company and an enterprise platform use different language for the same capabilities. But the shape determines the scorecard. A player-coach and a multilayer executive at the same company are grading different things entirely. Classify the shape first, adjust for tier second.
How to classify
Three instruments, in order of reliability.
1. Adjacency. Who does the role report to, and what's around it? Reporting to a CEO or founder with a small product team: likely player-coach. Reporting to a CPO with 7–15 designers already in place: likely growth director. Reporting to VP Engineering or CTO with explicit build/prototype/ship language: likely technical builder-leader. Reporting to a CDO or SVP Product with director-level reports beneath: likely multilayer executive.
2. Consequence vocabulary. Read what the posting says breaks and who absorbs it. Personal design quality and shipping velocity point to player-coach. Team retention, hiring pipelines, systems, and product-area ownership point to growth director. Production implementation, code, tools, and AI-assisted making point to technical builder-leader. Organizational design, workforce planning, budget, and executive alignment point to multilayer executive.
3. The first question they ask you. More reliable than the posting. "How involved were you in the design work?" — making doubt. You are facing a player-coach or builder-leader evaluation. "What structure did you create?" — growth-director question. "How did you develop your managers?" — multilayer-executive question.
When the posting says one thing and the first question tests another, trust the question. The posting was written weeks ago, possibly by someone who doesn't understand the role. The question was chosen by the person who will evaluate your answer.
Shape 1 — Small-team player-coach
You lead 2–5 designers while continuing to ship design work yourself. You are the most senior design person in the building. You report to someone who is not a design leader. Current examples: Gusto, Padlet, Aspora (60% leadership, 40% hands-on).
Posting signals. "Player-coach." Personal shipping language. Small or unstated team size. Future-tense hiring ("as the team grows"). Direct founder or executive reporting line. No mention of managers-of-managers or workforce planning.
Your evidence — high confidence. This is your strongest shape. Lead with Equinox+: four designers, two hired during the project, design-system creation, roadmap authority, your own product decisions visible on the page. Follow with Red Cross: seven-person cross-functional team, zero-to-one program, national deployment in six months. Allē adds a third instance of small-team leadership with direct product ownership.
Tier shifts what you pair with these cases. At AI-native companies, add verbal TinyFish context and reference the labs — the panel weights your ability to make in AI-native environments alongside team leadership. At enterprise platforms, Equinox+ and Red Cross carry the argument on their own through operational scale and consequential delivery; the labs are supplementary.
When you walk through Equinox+ verbally, promote the hiring and constraint-management evidence that sits lower on the page. The panel already sees the artifacts. What they need to hear is how you built the team and made scope calls under pressure.
When they ask "How involved were you in the design work?" — "At Equinox+, I made the information-architecture and cross-brand navigation decisions myself while leading four designers. Two of those I hired mid-project as scope expanded across five brands. I can show you which decisions were mine and which I directed."
Where it's thin. Your cases show teams you led, but not sustained people-management systems — performance cycles, career-ladder architecture, documented feedback mechanisms. For most player-coach roles this doesn't matter — they are buying a maker who can also lead. But if follow-up questions shift toward manager development or organizational operating rhythms, you have crossed into a different shape.
When they ask "How do you develop designers on your team?" — describe what you actually did: project sequencing, pairing on decisions, feedback in the work. Then redirect: "It sounds like the organizational scope here may be broader than the posting suggested — can you tell me more about the team structure you're building toward?" This surfaces whether you're actually in Shape 1 or have been reclassified.
Interview detection. The panel is typically small: CEO or founder, a product or engineering lead, possibly one design interviewer. The first question usually tests your personal design judgment — what you decided, why, what happened. If the second question asks how you guided the team, you're confirmed. If it jumps to organizational structure, manager development, or workforce planning, you've been reclassified mid-process. Verify early with the recruiter: "How many designers are on the team today, and does anyone currently manage other designers?"
Lead with Equinox+, support with Red Cross and Allē. Emphasize hiring during delivery, constraint-driven scope decisions, personal design judgment alongside team direction. AI-native tier: pair with labs and TinyFish verbal context. Enterprise tier: lead with Equinox+ and Red Cross operational scale. Confidence: High. Break condition: the role requires managers-of-managers experience or mature organizational infrastructure — if so, this is Shape 4 mislabeled.
Shape 2 — Craft-led growth director
You lead 7–15 designers. You build the team, create systems and standards, own a product area or portfolio, and stay close enough to quality to hold the bar. You may manage senior ICs but not other managers. Current examples: Amplitude, Maven Clinic (15 designers, career paths, hiring, quality), Joko.
Posting signals. "Build and grow the team." "Career paths." "Design systems." "Portfolio coherence." "Stay close to the work." Ownership of a product area or suite. Team sizes in the 7–15 range. Senior IC management is explicit, but managers-of-managers are not required. Ramp partially fits here — product-area ownership with team leadership — though its language also pushes into builder-leader territory with agent-building and pull-request requirements.
Your evidence — moderate confidence. Lead with Equinox+ for hiring and design-system creation. Add Alibaba for mandate creation — you identified the gap, built the research case, and secured the redesign. Add Thermo Fisher for consequential product architecture under operational constraints.
Across these three cases you demonstrate assembling a team, hiring during delivery, creating a design system, building a mandate from research, influencing a roadmap, and making product-architecture decisions with measurable business outcomes. That covers most of what this shape evaluates.
Tier matters. At growth-stage companies, the test is whether you can build from nothing — lead with Alibaba's mandate creation and Equinox+'s function-building arc. At enterprise platforms, the test is whether you can navigate existing organizational complexity while raising the bar — lead with Thermo Fisher's partner coordination and Equinox+'s multi-brand architecture.
When they ask "What structure did you create?" — "At Equinox+, I inherited a team of two and grew it to four designers and a researcher as scope expanded across five brands. I built the tokenized design system that let us scale across brand worlds, sequenced the roadmap, and made the call on which brands to launch first when engineering capacity forced a constraint."
Where it's thin. As I covered in the infrastructure objection dossier, your portfolio does not document career ladders, recurring critique systems, performance management, or design-operations ownership. For growth-director roles where the company wants you to build these systems, this is a framing problem — you can describe what you intend to create and why. For roles where these are treated as prerequisites you should have already demonstrated, the gap is real and no reframe closes it.
When they ask "What career frameworks have you built?" — "I've developed designers through project sequencing, direct mentorship, and hiring decisions, but I haven't formalized a career ladder as a published framework. At a team of this size, I'd build that in the first quarter — I have a clear view of what the levels need to test." This is honest and forward-looking. It works when the company is hiring you to create the infrastructure. It does not work when the company expects the infrastructure to already exist in your track record.
Interview detection. The panel asks what structure you created, how you grew senior talent, and where your own product judgment changed the outcome. Panel composition typically includes the product executive, design leadership, product management, and engineering — because the role assigns cross-functional product direction alongside team growth. If follow-ups move to compensation philosophy, workforce planning, and subordinate-manager development, the panel has started testing for Shape 4.
Lead with Equinox+ (hiring + systems), support with Alibaba (mandate creation) and Thermo Fisher (consequential architecture). Growth-stage tier: lead with mandate creation and building from scratch. Enterprise tier: lead with partner coordination and multi-brand complexity. Confidence: Moderate. Strong for mandate creation and team building; thin for mature organizational infrastructure. Break condition: career ladders, performance systems, or sustained manager development are treated as already-proven prerequisites.
Shape 3 — Technical AI builder-leader
You lead a team and personally build — prototyping, implementing, shipping into a production codebase, working with AI-assisted toolchains. This shape has sharpened in the past year as companies began expecting design leaders to write code or work directly in production environments. Current examples: Realtor.com (designs, builds, and ships components from Figma into production through an AI-assisted toolchain), Kognity (hands-on prototyping, AI-enabled practice, less explicit about code ownership).
Posting signals. "Build." "Prototype." "Implement." "Production codebase." "Ship production work." Named tools (Claude, Cursor, Figma-to-code). Design-to-code continuity as an explicit responsibility. Important distinction: generic "AI fluency" without artifact or implementation requirements does not establish this shape. Many growth-director postings mention AI without requiring you to build anything yourself.
Your evidence — moderate confidence, with conditions. Lead with Carrier IQ, Retail Velocity, and Brand Pulse. These establish that you can personally construct agentic interfaces, orchestrate multi-agent systems, and design evidence-oriented control surfaces. TinyFish adds verbal credibility for current-role AI production experience — use it to describe what you're doing now, but do not present it as a case study or portfolio evidence.
At AI-native companies, the labs carry strong currency. Production agent-interface exposure is still scarce and the product scope matches what these companies are writing into design roles. At enterprise platforms, AI fluency buys initial attention but consequence literacy is the actual test — lead with Thermo Fisher's operational constraints, then bring in the labs as technical capability evidence.
Where the evidence breaks. The labs prove velocity and interface judgment. They do not publish production adoption, customer outcomes, formal evaluation sets, regression gates, or a documented failure-to-correction-to-release cycle. For roles like Realtor.com's, where the posting explicitly requires production-code participation and shipped implementation, this gap is structural. You can describe your process verbally, but the public evidence doesn't close the loop.
When they ask "Show me what you shipped into production" — describe what you're building at TinyFish: the production context, the agent orchestration, what you've learned about model behavior in live systems. Then: "The labs on my site show the interaction design and orchestration thinking. The production implementation is happening now at TinyFish — I can walk you through the architecture and what we've learned, but I can't publish that work." That's the verbal bridge TinyFish provides. It works when the panel accepts current-role context as credible evidence. It does not close the gap when they need to see shipped artifacts on the page.
Interview detection. The probe family is artifact-specific: what you personally built, which tools and code path you used, what shipped, what failed, how implementation or model behavior changed the design. A technical design or engineering evaluator on the panel is a strong signal you're in this shape. If the panel never asks about your personal build process and focuses instead on team structure or organizational systems, you're being evaluated for a different shape regardless of what the posting said.
Lead with Carrier IQ, then Retail Velocity or Brand Pulse; support with Thermo Fisher and Alibaba for conceptual control models only. Emphasize what you personally built, how agent orchestration shaped the interface, and what TinyFish has taught you about production AI (verbal only). Confidence: Moderate at companies where prototyping and design judgment are the test; use with caution where production-code ownership and evaluation infrastructure are explicit requirements. Break condition: the role requires a documented production-code trail, formal evaluation infrastructure, or a longitudinal failure-to-release record.
Shape 4 — Multilayer executive
Managers report to you. You own organizational design, budget, headcount, workforce planning, compensation, and executive alignment. You run the design function through other leaders. Current examples: Vanta (approximately 40 people including design directors, five years scaling large orgs required), Bentley Systems (global multilayer organization, budget, headcount, organizational design), Freshworks (five years managing managers required).
Posting signals. "Managing managers." "Design directors" as reports. "Workforce planning." "Compensation." "Budget." "Headcount." "Organizational design." Global portfolio governance. Executive forums. Note: a large team without explicit manager layers or organizational-system duties may still be a growth-director role. And as I wrote in Issue #6, headcount alone doesn't determine the shape — Salesforce's Director of Web and Brand Design leads only eight people but owns manager leadership, workforce planning, compensation, and organizational design.
Your evidence — absent. No public case in your portfolio establishes the operating history these roles require. Alibaba can establish strategic mandate creation at enterprise scale, but it does not document director reports, managers-of-managers, workforce planning, compensation decisions, or sustained stewardship of a large design organization. The gap is structural, and no reframe closes it.
If a role's entry requirement is previously demonstrated managers-of-managers experience, do not pursue it. Substituting stakeholder complexity, enterprise scale, or small-team delivery for reporting-line depth will not survive the debrief. The panel will notice the absence, and attempting to bridge it creates strain that damages credibility across the rest of your candidacy.
When to reconsider. If a company posts multilayer-executive language but the first interview question asks about your personal design decisions or the team you built, the actual evaluation may be running a growth-director scorecard. Classify based on what they test. But verify before you invest. Ask the recruiter directly: "How many managers currently report to this role, and what organizational infrastructure already exists?" If the answer is two or more managers with their own reports, this is Shape 4 and the evidence gap applies. If the answer is "we're building toward that," you may be looking at Shape 2 with aspirational language.
No lead case establishes the required evidence. Confidence: Low. This shape does not fit your current portfolio. Deprioritize. If one interests you for other reasons, verify the actual evaluation scope before investing preparation time.
Holding the shape
The costliest mistake is oscillating between shapes within a single process. If one interviewer writes down "player-coach who ships great work" and another writes down "strategic leader building an organization," the debrief has two candidates and zero consensus. The room resolves that by advancing the person everyone could describe in one sentence.
Classify the shape before the first conversation. Hold it. If the interview reveals you classified wrong, reclassify cleanly between rounds — not mid-sentence. Your evidence supports Shape 1 with high confidence, Shape 2 with moderate confidence, Shape 3 with conditions. That covers most of your target list. Shape 4 does not fit today, and knowing that early saves you weeks you'd otherwise spend preparing for a scorecard your portfolio can't pass.
- Ramp's builder-leader drift: Ramp's current Director posting now describes building tools and agents and shipping pull requests alongside team leadership, which means it straddles Shapes 2 and 3 in ways the original posting did not — worth watching whether the interview process resolves toward one shape or tests both.
- Jasper's disappearing role: The old Jasper Director permalink still renders, but the role is absent from Jasper's current job board, making it useful as a specimen of strict builder-leader language rather than an active target.
- Salesforce's eight-person exception: Salesforce's Director of Web and Brand Design leads only eight people but owns manager leadership, workforce planning, compensation, and organizational design — a reminder that headcount alone does not sort the shape and the operating-system test matters more.
- Adobe's opening diagnostic: Adobe's design-leadership interview guide recommends asking how many people were on the team, what roles they held, and whose work the candidate was directly responsible for — a published version of the first-question diagnostic that confirms the classification instruments described here.