1. The Objection
"You were Head of Product at TinyFish — why are you looking at design roles?"
Every tier, usually inside the first ten minutes. Recruiters ask it flatly. Hiring managers get at it sideways, by asking you to walk through your most recent role in more detail than the role warrants. The design leader on the panel is listening for which vocabulary you fall into once you stop performing.
2. What They're Actually Asking
They are predicting whether you will leave design again. That is the whole of it. They can see the portfolio; they know you can design. What they cannot see is whether the next interesting product problem pulls you out of the function a second time. And every additional sentence you spend establishing that TinyFish was strategic makes that prediction worse, because someone who has settled a question does not argue it at length. The eight-claim version of this answer — deliberate strategic move, commercial credibility, revenue scope, AI-native build, shipped in three months, agent traces, governance, returned with frontier depth — is a closing argument for a decision you made two years ago, and it gets heard as one.
3. The Strongest Case Against You
- Your homepage places TinyFish first under selected work, described in design-pattern language (verification, oversight, trust in agents) despite the NDA label. The evaluator has already read TinyFish as your lead design case before you open your mouth, and it came from a product role you are about to explain away.
- Your most recent title is Head of Product. Category-sequence research shows employers penalize candidates who move between occupational categories, and no published study establishes that a short departure clears the penalty. A 2026 Swiss labor-market study found the penalty attenuated only where four conditions held at once: prior experience in the target occupation, a credential in it, movement from a similar occupation, and no more than one year in the intervening role. Duration by itself restored nothing.
- The return-to-design narrative asks the evaluator to trust a stated intention. Stated intentions are the weakest form of evidence a hiring process accepts.
4. The Grain of Truth
You did leave design for product. The category penalty is real and not clearly time-bounded. The doubt is a rational inference from your profile, not a misread.
5. Classification — Hybrid
Reclassified from the pure perception gap assigned in Issue #8. Two things changed. The homepage now leads selected work with TinyFish and describes it in design-pattern terms, which is a screening-level problem verbal framing cannot reach. And the category-penalty research gives no clean basis for assuming a brief departure resets the evaluator's category assignment.
Perception gap component: Your portfolio holds unambiguous design leadership evidence — Alibaba (Head of Design and Research, North America) and four shipped products as Product Design Director at BCG Digital Ventures.
Evidence gap component: The homepage's current TinyFish placement contradicts the positioning strategy. Build Queue item: Reorder selected work so a published design case leads; strip design-pattern language from the TinyFish NDA card. Status: not started. Until this ships, the homepage argues against the verbal answer.
6. The Reframe
Here is the version you are probably rehearsing:
"I made a deliberate move to product because I wanted to build AI-natively from zero. I gained commercial credibility and revenue scope. I shipped the agentic platform in three months. I worked daily with agent traces, auditability, attribution, reversibility, and governance. I built real technical depth in enterprise AI. And I returned to design because I want to apply that depth to a specific vertical domain and I missed the creative impact of design leadership."
Six sentences, eight claims, all true. Stacked together they sound like someone still auditing whether the move was worth it.
The budget version: state the move, name the speed, give the reason you came back, stop. Then route to the one piece of evidence that answers whatever competency the interviewer is actually screening for.
Evaluators average rather than add, and mildly favorable claims dilute stronger ones rather than stacking with them. The eight-claim version mixes what an evaluator can verify (shipped in three months, returned to design) with what they cannot (governance challenges, commercial credibility, revenue scope). The unverifiable half adds no weight. It adds reasons to wonder what you are covering.
No one has tested a one-sentence TinyFish answer against the eight-claim version in a live interview loop. The claim-budget method is consistent with the evidence, not validated by it. Confidence: moderate. The direction is clear enough to act on, and the alternative carries a known cost: it reads as defensive.
Tier Notes:
- AI-native companies: After the one sentence, route to your forward-looking design artifacts or the Trust essay. They want current design thinking, not a product retrospective.
- Enterprise platforms: Route to Alibaba. The scale and the Head of Design and Research title settle the commitment question without your having to argue it.
- Growth-stage: Route to the BCG DV 0-to-1 builds — Equinox+ to MVP in three months, Red Cross to national deployment in six, both as Product Design Director at BCG Digital Ventures. Shipping record carries more here than anything the TinyFish line does.
7. What to Say
"I moved to product to build an AI platform from zero — shipped it in three months. I came back to design because I want to apply that technical depth to [their domain]. Here's what I've been building since."
Then open one portfolio case. If they want more on TinyFish, they will ask, and a question from them is a better outcome than more explanation from you.
8. What Not to Say
- "I've always been a designer at heart." Frames the product role as something you endured rather than chose, and undercuts the claim that TinyFish gave you real capability.
- "I gained commercial credibility / revenue ownership / strategic scope." Unverifiable from outside the company. Sounds like you are selling the detour to yourself.
- "It was always the plan to come back." Retrospective rationalization. Nobody believes a two-year career plan executed on schedule.
9. Early Signals
- The interviewer asks you to walk through your most recent role with unusual specificity about scope, reporting structure, or why you left. They are assembling the commitment case before they ask the question directly.
- A design leader on the panel asks what you are "most excited to get back to." The phrase get back to tells you they have already categorized you as someone who left.
Objection: "You were Head of Product — why design roles?"
Classification: Hybrid (reclassified from perception gap, Issue #8)
Real fear: She'll leave design again.
Lead with: One sentence on TinyFish (moved to product, shipped in 3 months, came back), then the strongest portfolio case for this audience.
Say: "I moved to product to build an AI platform from zero — shipped it in three months. I came back to design because I want to apply that depth to [their domain]. Here's what I've been building since."
Avoid: Listing everything you gained at TinyFish. The list is the problem.
Build Queue item: Reorder junochen.com selected work so a design case leads; strip design-pattern language from TinyFish NDA card. Status: not started.
- Category penalties and return movers: A 2026 Swiss labor-market study found that return movers who combined prior occupation experience, a credential, a similar departure field, and no more than one year away showed no statistically discernible contact penalty — the closest evidence that short departures can attenuate the cost.
- Presenter-evaluator gap on claim density: Weaver, Garcia, and Schwarz found across seven studies that presenters systematically include all favorable information while evaluators average it, meaning mildly favorable additions can reduce the overall impression rather than strengthen it.
- When defensive responses actually help: A simulated-interview experiment found that apologies, justifications, and excuses all improved ratings over silence when a competence concern had already surfaced — but the study tested response type, not whether volunteering the concern unprompted helps or hurts.
- Homepage routing contradicts positioning: The September 12 site audit found TinyFish placed first under selected work with design-pattern language despite its NDA label, while the approved Agentic Labs cases require more effort to reach — a structural problem that no verbal answer can override at the screening stage.