The Head of Product Question — One Title, Three Fears, Three Exits
Every interviewer who sees "Head of Product" on your most recent line is estimating the same risk, but they are not all worried about the same failure. One thinks you'll leave design again. Another thinks the craft has gone stale. A third thinks you'll reach into product's lane and create friction they'll have to manage. The answer that resolves one of those fears can deepen the other two, which is why a single rehearsed response to this question tends to make it worse. This dossier splits the title question into its three constructs, maps the published evidence that answers each, and gives you the language for whichever version you're actually hearing.
The Head of Product Question — One Title, Three Fears, Three Exits
Every interviewer who sees "Head of Product" on your most recent line is estimating the same risk, but they are not all worried about the same failure. One thinks you'll leave design again. Another thinks the craft has gone stale. A third thinks you'll reach into product's lane and create friction they'll have to manage. The answer that resolves one of those fears can deepen the other two, which is why a single rehearsed response to this question tends to make it worse. This dossier splits the title question into its three constructs, maps the published evidence that answers each, and gives you the language for whichever version you're actually hearing.
Concede the Fact, Contest the Inference
Every predictable objection to your background contains a fact and an inference. The product title is the fact. "She left design" is the inference. This piece gives you a method for separating them: concede the fact in one sentence, redirect to evidence that answers what the interviewer is actually evaluating, and stop. It also covers when to fix the source artifact instead of preparing a verbal response, how to tell whether a concern even matters for a given role, and when a concern that survives your best answer is telling you the role is wrong. The dossiers build out the specific evidence branches. This is the system they plug into.
Concede the Fact, Contest the Inference
Every predictable objection to your background contains a fact and an inference. The product title is the fact. "She left design" is the inference. This piece gives you a method for separating them: concede the fact in one sentence, redirect to evidence that answers what the interviewer is actually evaluating, and stop. It also covers when to fix the source artifact instead of preparing a verbal response, how to tell whether a concern even matters for a given role, and when a concern that survives your best answer is telling you the role is wrong. The dossiers build out the specific evidence branches. This is the system they plug into.
"She's Never Worked at a Frontier Lab"
Most companies hiring for AI design leadership will notice you haven't worked at OpenAI, Anthropic, or DeepMind. Some will say it out loud. This dossier classifies the objection as hybrid — part perception gap you can close with positioning, part evidence gap you cannot close until the correction-loop artifact ships. Three constructs, each benchmarked against current posting language from OpenAI, Gusto, Headway, and Render, each with a confidence level and a recommended response you can say out loud without sounding defensive.
You Built It, Transferred It, and It's Still Running
Every evaluator who sees "BCG Digital Ventures" assumes the same thing — you designed a concept, handed it off, and left. The evidence says otherwise, but they stop reading before they reach it. This dossier takes one project — Thermo Fisher mySupply, built as Product Design Director at BCG Digital Ventures — and uses it to answer the three things the consulting objection actually questions: whether the product survived, whether your decisions stuck, and whether you operated inside real organizational complexity or delivered from outside it. Confidence level: high. The product is still publicly operational five and a half years later.
Leadership Scale Without a 40-Person Org Chart
You have not stewarded a 40-person design org. One of your six current targets will screen you out on it. The other five evaluate for something different — craft depth, player-coach leadership, organizational influence without formal authority — and your record matches what they actually need. This dossier sorts which is which, maps your published evidence to the three constructs that matter for strong-fit roles, and gives you response language for live conversations, including when to stop reframing and acknowledge the mismatch.
What They Actually Mean When They Ask If You Can Code
"Can you code?" is three different questions wearing the same words. A startup CTO is asking about dependency. A design VP is asking about judgment near implementation. A recruiter is checking a box. This dossier classifies the objection as a hybrid — part perception gap, part evidence gap — and routes each version to the specific evidence from Juno's background that answers it. It also names the hard filter: when the question actually does mean "are you an engineer," and what to say when it does.