Classification
"Are you a hands-on designer or a leader?"
This objection is a hybrid — part perception gap, part evidence gap. Your portfolio shows IC craft and leadership side by side, and evaluators who scan quickly can't tell which version of you they'd be hiring. The forward-looking visual design artifacts at junochen.com that would close the IC craft-depth question before you walk into the room are specified and in progress but not yet published.
What exists now: Equinox+ shows you personally owning information architecture, cross-brand navigation, and design-system architecture while leading a small team under launch pressure as Product Design Director at BCG Digital Ventures. Alibaba shows you identifying a professional-buyer mismatch, building the internal case, and leading the homepage and search redesign as Head of Design and Research. These are real proof that IC judgment and leadership coexist in your practice.
What's missing: a current, inspectable artifact that demonstrates present-tense craft thinking in AI-product work. Something an evaluator can open and study before the conversation starts. That artifact is in development. It is not live. If asked, say so.
The perception gap means you route the evaluator to existing evidence. The evidence gap means you build the missing artifact. A hybrid means you do both while using the conversation itself as a diagnostic instrument.
Why this objection has traction
Your background operates in two registers. Alibaba is a leadership story: mandate creation, organizational redesign, executive stakeholder work. Equinox+ is a craft story: you were personally in the IA, the navigation model, the late scope call. Both are true, and both are yours. But an evaluator scanning your portfolio in three minutes sees someone who might be either thing, and they need to know which one shows up on day one.
That's a fair question. The answer is both — but "both" is a claim that requires specific proof matched to the specific role, not a general assertion. The diagnostic below tells you whether the role actually wants both. The evidence routing tells you which proof to lead with when it does.
The diagnostic question
The surface question sounds binary. It means different things depending on who's asking and what their organization actually needs. Your job is to figure out which version you're hearing before you answer it.
Hold this question during prep and, when you can, ask a version of it in conversation:
"Where does the team currently need personal craft judgment on hard problems, and where does it need leadership exercised through other people?"
The answer separates roles where your IC+manager profile is a genuine advantage from roles where "hands-on" is a euphemism for doing the work of three missing hires.
The Four Scorecards piece mapped four IC+manager shapes and their posting signals. What follows is the activation layer: how to read specific postings and interview language to determine which shape you're facing, and what to do with that read.
Signals that "hands-on" means craft authority
Good-fit indicators. The company wants a leader whose personal design judgment operates at the hardest decision points while the team handles the broader surface area.
The posting names an existing team and separately names bounded personal contribution. Kindred's Head of Product Design posting describes leading a five-person design and research team, running feedback and career systems, setting design strategy — then says the Head should "ship work yourself when it counts." The personal making is bounded to consequential projects. Amplitude's Head of Product Design does the same at larger scale: a 15-person team, autonomous pods, and the Head pairs with designers on "the hardest UX puzzles" rather than owning any surface end to end. Both postings reject a pure-IC model and an executive who only delegates.
The consequence vocabulary is about quality judgment, not coverage. Look for language about raising the craft bar, pairing on ambiguous problems, making the call on hard interaction decisions. Compare that to language about "owning" surfaces, "covering" product areas, or "handling" design needs. The first describes authority applied selectively. The second describes capacity distributed across too few people.
The posting names leadership mechanisms that let judgment travel through others. Feedback systems, design-system governance, career development, hiring plans, cross-functional representation. These are the channels through which a leader's craft standards operate at scale without the leader personally producing every artifact. When a posting names these alongside personal contribution, it's describing a player-coach role where both modes are real. When a posting names personal contribution but none of these mechanisms, the "leadership" part of the title may be aspirational.
Signals that "hands-on" means understaffing
Bad-fit indicators, or at minimum signals that require direct verification before you invest further.
The posting says or implies you are the design function. Fin's Head of Design is explicit: the candidate will be the "only full-time designer," operating as a "one-person design function" covering product UI, the design system, marketing assets, and brand touchpoints "without specialized support." Some people thrive in this. But the diagnostic question has a clear answer here: the team needs personal craft judgment everywhere, because there is no team. Your leadership experience has no surface to operate on.
"Cross-functional collaboration" appears repeatedly with no mention of design authority or reporting structure. When a posting uses "cross-functional" three or more times but never names who design reports to, whether design has a seat in product decisions, or what authority the design leader holds in priority disputes — the pattern typically means design currently lacks organizational standing and the company hopes a new hire can fight for it. Compare that to Kindred's posting, which names cross-functional work alongside a defined five-person team, explicit strategy ownership, and distinct people-leadership responsibilities. One describes collaboration from a position of authority. The other describes collaboration as a substitute for it. That can be the right fight for the right person. You should know it's a fight before you walk in.
The role spans product, brand, marketing, and systems with no indication of specialist support or planned hires. Breadth without depth signals capacity substitution. A Head of Design who covers product UI, marketing assets, brand touchpoints, and design-system maintenance is doing four jobs, not exercising senior craft judgment at ambiguous decision points.
How to activate the reframe
When the diagnostic signals a good-fit scenario, here's how to handle the surface question. The response architecture from Issue #9 applies: concede the narrow fact, contest the inference, stop.
Surface question: "Are you more of a hands-on designer or a manager at this point?"
Recommended response: "Both, and I think that's what this role needs. At Alibaba I was Head of Design and Research — I identified the professional-buyer gap, built the case internally, and led the redesign across homepage, search, and product detail. At BCG Digital Ventures on Equinox+, I was personally in the IA, the navigation architecture, and a late scope decision while leading the design team through launch. The pattern is: I lead through other people on the broad surface and do the craft work myself at the decision points where senior judgment changes the outcome."
Then stop. Read their reaction.
If the follow-up moves to specifics — what was the scope decision, how did you structure the team, what did the IA look like — the concern has cleared. They're evaluating craft depth. You're in a good conversation.
If the follow-up restates the original question in different words — "but would you be comfortable rolling up your sleeves and doing the design work yourself?" — the concern hasn't cleared. Two possibilities: they didn't hear the evidence, or "hands-on" means something in their organization that your answer didn't address. Ask directly: "Can you tell me more about what the day-to-day design work looks like for this role? I want to make sure I understand where the leader is personally in the work versus where the team carries it." Their answer is your diagnostic.
If the follow-up is about whether you'd be comfortable only doing design — no team, no strategy, no organizational work — the role may be an elevated IC with a leadership title, or the interviewer is testing whether you'll accept a narrower scope than your background suggests. Either way, you now have information you didn't have before the question was asked.
Which proof to lead with
The Four Scorecards piece mapped evidence to each IC+manager shape. Compressed for the reframe:
Player-coach roles (Kindred, OpenAI Codex Growth): Lead with Equinox+. It's the cleanest proof of personal craft judgment exercised alongside team leadership under real constraints. The American Red Cross and Thermo Fisher projects at BCG Digital Ventures add high-stakes delivery complexity.
Craft-led growth director roles (Amplitude): Lead with Alibaba. Mandate creation and design direction at enterprise scale, with the craft bar set through organizational leadership rather than personal production on every surface.
Technical AI builder-leader roles: The Agentic Labs projects (Brand Pulse, Retail Velocity, Carrier IQ) demonstrate AI-product thinking. The forward-looking artifact, when published, will close the current-craft-depth question for this shape. Until it ships, acknowledge the gap honestly: your recent work at TinyFish gave you direct experience with AI product development, and the artifact that makes that thinking inspectable is in progress. Don't oversell what isn't published. Don't apologize for building it.
Exit condition
When a role's published requirements center on scaling a large design organization and managing director-level reports, this exceeds what your background evidences. No reframe fixes it.
Vanta's Head of Design — an approximately 40-person organization led through design directors — is the clearest current example. As covered in Issue #9, this is a qualification mismatch. Spend your time on the roles where the diagnostic signals a match.
Pre-interview quick reference
Scan this the morning of.
Diagnostic question: Where does this team need my personal craft judgment on hard problems, and where does it need leadership through other people?
If asked "Are you hands-on or a leader?": "Both. At Alibaba I led the mandate and the redesign as Head of Design and Research. At BCG Digital Ventures on Equinox+ I was in the IA and the navigation architecture while leading the team through launch. I lead broadly and do the craft work myself at the decision points where it matters."
Read the follow-up:
- They ask specifics about the work → concern cleared, they're evaluating depth
- They restate the question → ask what day-to-day design work looks like for this role
- "Would you be comfortable just doing design?" → the role may be narrower than the title; you now have intelligence
If asked about current craft work: The forward-looking artifact is in development and not yet published. Name it honestly. Don't fill the gap with claims you can't back with a URL.
Signals to watch during the conversation:
- They name specific problems where they need senior judgment → good fit
- They describe coverage gaps across multiple surfaces → capacity substitution risk
- They mention an existing team with distinct responsibilities → leadership mechanisms exist
- They can't describe where the leader's personal work ends and the team's begins → the role isn't defined yet
Exit: If the role requires managing design directors or scaling a 40+ person org, it's outside your current evidence. Don't reframe. Move on.
- Amplitude's pod autonomy model: Their Head of Product Design posting describes a 15-person team organized into autonomous pods where the leader pairs on hard problems rather than owning any surface end to end, which is a distinct operating system from the other player-coach roles tracked here.
- Atlassian's split interview construct: Atlassian's design interview process runs separate portfolio reviews for IC craft and management-candidate leadership, which means the "hands-on or leader" question may never surface as a single question there because the process already bifurcates it.
- CZI's contribution-separation protocol: CZI's product design interview guide explicitly asks candidates to distinguish their own contribution from teammates' work, making authorship clarity on the Equinox+ and Alibaba cases a prerequisite rather than a nice-to-have.
- OpenAI's hybrid-role precedent: The Codex Growth design-lead posting says OpenAI is open to both experienced managers and senior ICs who demonstrate mentorship, leadership, and team-level impact, which means the hybrid profile is an explicit hiring criterion there rather than something to defend.