The product role at TinyFish was a real detour. You took it deliberately, shipped from it, and moved on. The dossier covers what to say when the question surfaces — commitment, capability, authority, and the follow-up signals that tell you each construct has cleared. This piece is about knowing which situation you're actually in so you use the right version at the right moment, or stay quiet when quiet is correct.
Four situations, each with a rule, a reason, and a confidence marker.
Situation 1 — Before anyone talks to you
This is screening risk. A recruiter forms a category judgment from your LinkedIn, resume, or portfolio before any conversation happens. If the category they land on is "product person," you never get the meeting. You can't correct a perception gap in a conversation that was never scheduled.
Confidence: high. The cost of inaction here is invisible — you never learn about the roles that screened you out.
LinkedIn. Your public LinkedIn surface currently centers TinyFish. The page title a recruiter sees is "Juno Chen - TinyFish." Your visible About text begins with "Building the infrastructure for human-AI collaboration in enterprise web automation as…" — present tense, product-company framing, no design leadership language in the publicly exposed portion. I can't see your full headline or complete About section from a signed-out view, but the artifact a recruiter encounters before clicking through does not read as design leadership.
Update your LinkedIn headline to lead with design leadership language before your next outreach. Something in the range of "Design Director | AI-native product design | Enterprise, 0-to-1" — so TinyFish appears in your experience section as one role among several, not as your professional identity. Your About section should open with the career spine. Issue #8's materials sequencing already recommended this. The public artifact suggests it hasn't happened yet.
Do this before you send another outreach message. The message and the profile will be read together, often within seconds of each other.
Resume. I haven't been able to verify the current state of your resume — no version is posted publicly or linked from junochen.com. Before you send it anywhere, check three things:
- The header leads with a design leadership framing, not "Head of Product" or "TinyFish"
- TinyFish appears in past tense with a one-line bridge explanation, not as the lead role
- BCG Digital Ventures projects are attributed as Product Design Director work, which is what they were
A five-minute edit that prevents a screening-stage misread.
Portfolio at junochen.com. The portfolio already shows design leadership work. The rule here is simpler: don't change the portfolio to accommodate this objection. The portfolio is your evidence. Its job is to be there when someone checks, and it does that. If a reviewer visits junochen.com after reading your resume and sees design leadership case studies, the title question resolves on its own. But if they never visit because your resume created the wrong category, the portfolio doesn't get a chance to work.
Situation 2 — First message or first thirty seconds
You're writing a first message to a recruiter, hiring manager, or mutual connection, or you're in the opening minutes of a first call. The question: address the Head of Product title before anyone asks, or leave it alone?
Confidence: moderate. The right call depends on what the recipient already knows about you, which you can estimate but not confirm.
When your written materials already lead with design leadership (per Situation 1): Don't preempt the question in outreach. Your materials have set the category. Raising the title proactively in a cold message introduces a concern the reader may not have had. The general framework applies here: don't respond to a concern that isn't active.
When your LinkedIn still shows TinyFish prominently and you're sending written outreach: The message has to do the category work your profile isn't doing. In a cover letter or cold email to a role that asks for design leadership, open with the career spine — not the bridge, the spine:
"I've led design at enterprise scale — Head of Design and Research at Alibaba.com, Product Design Director at BCG Digital Ventures across Thermo Fisher, Red Cross, Equinox+, and Allē."
The bridge can follow in one sentence if the role specifically involves AI or 0-to-1 builds: "I took a product role at TinyFish to build an AI platform from zero, shipped it in three months, and returned to design." If the role doesn't touch AI, the bridge doesn't belong in the first message. Let them find TinyFish on your LinkedIn and ask about it — by then they've already categorized you from the email.
Fix the profile first if you can. If you can't fix it before a time-sensitive outreach, the written message is your only category-setting surface.
When you're on a first call and the recruiter is reading your LinkedIn in real time: They're scanning your profile while you talk. If TinyFish is prominent, they will ask. Set the category in your opening thirty seconds before they file you elsewhere:
"My background is design leadership — Alibaba, BCG Digital Ventures, a set of 0-to-1 builds. I took a product role at TinyFish specifically to build with AI from the ground up, shipped a platform in three months, and came back to design. The portfolio at junochen.com shows the design work."
Category statement, two sentences of bridge, one redirect to evidence. Then stop. Let them ask what they want to ask.
Situation 3 — When the interviewer raises it
Someone across the screen asks about the Head of Product title. Maybe directly: "I noticed you were Head of Product at TinyFish — tell me about that." Maybe obliquely: "How do you think about the line between product and design?" Maybe as a proxy for something they haven't named yet.
Confidence: high on the response structure, moderate on reading which construct is active.
The dossier covers three constructs — commitment ("are you actually a design leader or did you switch?"), capability ("can you still do design leadership work?"), and authority ("will you overstep into product territory?"). The activation rule here is about sequencing.
If you've already been invited to interview, don't volunteer the bridge narrative before the interviewer signals interest in it. If they're looking at your portfolio and asking about the Alibaba org design work, they've already categorized you correctly. Introducing TinyFish at that moment interrupts a positive evaluation with a concern they weren't having.
Confidence: use with caution. There's a gray zone where you're twenty minutes into a conversation, the interviewer hasn't raised TinyFish, but you sense it's coming — a slight pause on your resume, a glance at something off-screen. The instinct to get ahead of it is strong. Resist unless you have a concrete signal: they've pulled up your LinkedIn, they've mentioned the title, they've asked a question that only makes sense if they're looking at TinyFish. Anticipate the question, but don't answer it until it arrives.
When the question comes, concede the fact in one sentence before any reframe: "TinyFish was a product role — I took it deliberately to build an AI platform from zero." Then bridge: "I shipped it in three months and came back to design because design leadership is what I want to do and what my track record is in." Then point to the specific portfolio work that matches the role you're discussing.
Read the next question to identify which construct is active. The three constructs sound different in practice:
- Commitment sounds like future-direction questions: "Where do you see yourself in two years?" or "Would you want to go back to product?" or a second pass at why you left TinyFish after you've already answered once. They're testing whether you'll stay.
- Capability sounds like recency questions: "What's the most recent design leadership work you've done?" or "How have you kept your design practice current?" They're checking whether the product detour created a skills gap.
- Authority sounds like collaboration questions: "How would you work with our Head of Product?" or "Where does design's authority end in your view?" They're worried you'll overreach.
If the interviewer moves to the role itself — scope, team, product challenges — the construct has cleared. If they circle back from a different angle, identify which of the three they're still testing and address that one directly.
Your bridge narrative should never run longer than two sentences before you redirect to evidence. A longer explanation reads as a longer defense.
Situation 4 — When the question is the answer
Sometimes the Head of Product question isn't about a gap in your background. The interviewer is telling you what the company actually wants.
Confidence: moderate, but the pattern is consistent enough to flag.
You may enter a conversation thinking you're in Situation 3 — explaining a perceived gap — and realize partway through that you're in Situation 4. The signal: the interviewer's energy around TinyFish shifts from something to be accounted for to something they want more of. They stop asking why you left product and start asking how you did product. They lean into the prioritization decisions, the roadmap authority, the stakeholder alignment. Their follow-ups pull toward product ownership, not design leadership.
I've seen this in searches where a company posts a design leadership title but fills the job description with product-ownership language — roadmap authority, feature prioritization, stakeholder alignment on what to build rather than how to build it. When the interviewer keeps returning to the Head of Product title with curiosity rather than concern — "That's really interesting that you did product — how did you think about prioritization?" — they may be telling you they want product judgment housed under a design title.
When you notice this, stop defending the transition and start evaluating the role.
The diagnostic: Is the interviewer treating the product experience as something to be explained away, or as the most interesting thing on your resume? If it's the latter, and their follow-up questions consistently pull toward product authority (roadmap ownership, feature scoping, go-to-market input) rather than design authority (craft quality, org building, research integration, design system strategy), you're likely looking at a role where design stays downstream and the title is cosmetic.
If by the end of the second conversation the interviewer has spent more time exploring your product authority than your design leadership, and the role's described mandate does not include org building, craft bar-setting, or design-function ownership, this is a product role wearing a design title. You can take it if you want a product role. But if you're building a design leadership track record, this reads as a second product detour, and the bridge narrative gets harder to tell the third time.
One question to accelerate this evaluation:
"In this role, does design own the experience vision, or does design execute on a product-defined vision?"
Ask it early enough to act on the answer. Watch for the hesitation before the words — that gap often tells you more than whatever follows it.
-
Candor timing for career-changers: A 2023 experiment with 81 professional recruiters found that former entrepreneurs returning to conventional employment did not consistently benefit from immediately addressing their prior role — supporting the activation-rule distinction between having a coherent explanation ready and volunteering it indiscriminately.
-
What interviewers actually test: Atlassian's design interview handbook separates management-candidate portfolio reviews from IC reviews, probing how the candidate led the team and shaped the result rather than individual design choices — which means the same portfolio walkthrough needs different emphasis depending on which construct the panel is evaluating.
-
Contribution clarity under pressure: CZI's product design interview guide explicitly asks candidates to distinguish their own contribution from teammates' work and scores leadership, collaboration, and measured impact as separate signals — a useful preview of how structured panels will probe the BCG Digital Ventures cases.
-
Disclosure can backfire competitively: A peer-reviewed experiment found that realistic job previews could reduce applicants' willingness to disclose, particularly when applicants perceived high competition — a reminder that the decision to preempt or wait is shaped by how competitive the search feels, not just by the strength of your answer.