Your homepage hero now says "Available · Design Leadership · AI-native platforms." TinyFish no longer appears as a case study card. Good. But the hero aside still reads "Currently: Head of Product, TinyFish" with a direct link to tinyfish.ai. That's the trigger. Any interviewer who reads your homepage will see a design leadership frame and a product title in the same viewport. The frame is strong. The title still invites the question. This dossier is for when it does.
1. The Objection
"I see you're currently Head of Product. Why are you looking at design leadership roles?"
Every tier asks this, but at different stages. Growth-stage companies (Ramp, Headway, Gusto) raise it in screening calls because they're pattern-matching for commitment. AI-native companies (OpenAI, Anthropic) surface it during portfolio reviews because they want to know which discipline owns your judgment. Enterprise (Salesforce, Atlassian, Adobe) hold it for final rounds because they need to place you in a reporting structure, and a product title creates slotting ambiguity.
2. What They're Actually Asking
The fear goes past the title. They're evaluating trajectory. A Head of Product who applies for Head of Design triggers a specific read: she tried product, it didn't work, and now she's retreating to the discipline she came from. If that's the story, the hire is a flight risk who will leave again when the next product opportunity surfaces. The deeper version is worse: that you don't actually want to build a design function, raise the craft bar, or fight for design's organizational seat. That your instincts are product instincts now, and the team will feel the difference within ninety days. This second fear kills candidacies because it's harder to articulate and therefore harder for you to address if you don't name it first.
3. The Strongest Case Against You
- Your homepage hero aside says "Currently: Head of Product, TinyFish" directly below a design leadership positioning statement. A skeptical interviewer reads this as someone narrating a transition they haven't completed yet.
- The Agentic Labs work reads as solo-built products. No design-org mandate is visible on the app pages. An interviewer scanning quickly sees a builder, not a leader.
- Your most recent title is the data point that anchors hardest. Five prior design leadership titles are historical. The current one says Product.
- None of the target companies' design leadership postings explicitly welcome product-leadership backgrounds. Ramp values business impact. OpenAI wants someone who shapes product direction. Headway wants a design leader who can influence organizational direction. All three describe product fluency as additive to design leadership, not as a qualifying credential on its own.
4. The Grain of Truth
Your current title is Head of Product, not Head of Design. No reframe eliminates that. Interviewers will read this as a departure from design. The gap worth worrying about is narrower: your most recent data point is the one interviewers anchor on, and that data point says Product. Alibaba at $50B+ GMV proves you've operated at scale in design. They believe you can do the work. The question is direction. Where are you headed, and is this role where you're building or where you're passing through?
5. The Reframe
Your portfolio answers this question before you open your mouth. Every published case study on junochen.com carries a design leadership title. Alibaba: Head of Design & Research, North America, $50B+ GMV platform, +20% daily transactions, +2.2pt NPS. Thermo Fisher: Product Design Director, $20M+ margin recovered, 100% partner adoption. Red Cross: Product Design Director / GM, $847K disbursed, six systems consolidated to one, national deployment. Equinox+ and Allē: Product Design Director on both, 0→1 builds with measurable business outcomes. Five published mandates, all design leadership, all verifiable right now. The product chapter layers commercial accountability onto that foundation.
What the product chapter gave you is the thing most design leaders lack and most hiring committees quietly wish they had: direct commercial accountability. Pricing decisions, revenue ownership, the ability to hold a strategy conversation in business language alongside experience metrics. The Ramp posting asks for "meaningful customer and business impact." OpenAI wants someone who can "shape product direction." Headway wants a leader who can "influence organizational direction through design thinking." These postings describe the exact judgment the product role sharpened. High confidence this reframe lands when you lead with Alibaba or Red Cross as proof of design leadership commitment, then frame the product title as commercial scope layered onto that foundation.
Tier Notes:
- AI-native (OpenAI, Anthropic, Suno): Product fluency is expected, not unusual. Lead with Agentic Labs to prove domain credibility, then use the product title as evidence you understand how AI products generate revenue. Lighter touch.
- Growth-stage (Ramp, Headway, Gusto): These companies need design leaders who partner with product as equals. The product title is your strongest differentiator in this tier. Lean into it.
- Enterprise (Salesforce, Atlassian, Adobe): Title linearity anchors harder here. Lead with Alibaba's Head of Design & Research title and the platform scale. The product detour needs one crisp sentence, not a narrative.
6. What to Say
"My published work is five design leadership mandates: Alibaba, Thermo Fisher, Red Cross, Equinox+, Allē. That's the foundation. The Head of Product role added commercial and pricing accountability to that base, because I wanted the business language to hold my own in strategy conversations alongside the experience ones. I never left design."
A note on reading the room: the line about wanting business language to hold your own in strategy conversations plays well with product-side interviewers and CPOs. If you're speaking with a VP Design or Head of Design who built the org you'd be joining, soften it. They may hear a critique of how design leaders generally operate. With that audience, try: "because I wanted to understand the commercial side of the decisions I was already shaping from the design side."
7. What Not to Say
- "I wanted to try product and realized I missed design." Confirms the flight-risk narrative. Frames design as a fallback. You want it framed as the constant.
- "The title is misleading — I was really doing design work." Sounds like an apology. Invites the follow-up: "So why did you accept it?" Also undermines your current employer.
- "I can do both." Generalist framing at Director+ level signals you don't know which seat you want. Pick design. Say design.
8. Early Signals
- The interviewer asks you to "walk through your career arc." Arc questions at this level are fishing for narrative coherence. They want to hear you explain the product chapter. Don't wait for the direct question. Open your arc answer with the frame: "I've spent thirteen years building design leadership mandates, and the most recent chapter added product and commercial scope to that foundation." If you wait until the chronological TinyFish moment to address it, the interviewer has already spent several minutes wondering.
- The interviewer references your homepage language or LinkedIn title before you do. They've done their research and the product title is already on the table. Treat it as an opening. Redirect to the five published mandates immediately.
Objection: "Why are you in product if you want design leadership?"
Real fear: She left design. Design is the fallback. She'll leave again.
Lead with: Alibaba — Head of Design & Research, North America, $50B+ GMV, +20% transactions. Five published design leadership mandates, all verifiable at junochen.com.
Say: "Five design leadership mandates are my foundation. The product title added commercial accountability. I never left design."
Avoid: "I wanted to try product" — confirms the flight-risk read.
Last validated: June 30, 2026
- Ramp's "end-to-end ownership" language: Their Director, Product Design posting explicitly asks for product judgment, business impact, and customer closeness alongside design craft, making it the growth-stage role where the product-title reframe lands hardest.
- OpenAI's "multiple altitudes" framing: Their Product Design Manager posting asks for comfort spanning design details to system architecture to long-term strategy, which maps directly to the IC+manager hybrid dossier coming next.
- Headway's player-coach split: Their two open design director roles reveal different buyer needs at the same company, with the Provider Experience posting asking for hands-on AI-native design while Core Insurance emphasizes team scaling and design systems.
- Anthropic's "part researcher, part builder" frame: Their Design Engineer, Education Labs posting measures success by whether users become more capable rather than by time-on-site, a signal worth tracking for how AI-native companies are redefining design evaluation criteria.