One Problem, Two Surfaces
Most hiring committees are off today and tomorrow. Use the quiet to internalize this, because these two questions will surface in nearly every enterprise and growth-stage conversation you enter over the next several weeks.
"Does Alibaba translate to U.S. products?"
"Can you handle enterprise-scale complexity?"
Different in the room. Same question underneath.
The shared root is legibility. The interviewer cannot immediately read your experience as relevant to their context. One doubts the market. The other doubts the scale. Both resolve through the same structural pattern, and if you hold one posture anchored in the design problem you actually solved, you sound like someone who has done this before. Rehearse two separate pivots and you sound like someone managing objections. The difference is audible.
The Alibaba Correction
Resolve this factually. Do it in three sentences and move on.
Your published title is Head of Design & Research, North America. Your users were professional buyers running procurement on desktop, which represented 25% of traffic and 80% of transaction value. These were sourcing professionals evaluating suppliers across borders, committing significant inventory spend based on what a screen could tell them about a physical product they could not inspect.
Confidence: HIGH. Title and scope are on your published case study. This is factual correction, not interpretation.
When this surfaces, say:
"My role was Head of Design and Research for North America. The users were professional buyers running procurement on desktop, driving 80% of transaction value. The design problem was helping someone commit a significant purchase based on a screen, not a showroom."
Stop there. Do not narrate Alibaba's international expansion. Do not preemptively argue that B2B commerce in one context maps to B2B commerce in another. The role scope answers the question completely.
If the interviewer presses after hearing the factual correction, that tells you something about the company. Note it. You do not need to convince someone that North America is North America.
Where Both Questions Collapse
Both surface questions lead to one answer.
The design problem at Alibaba was verification at distance. A buyer evaluating a $500+ order cannot touch the product, visit the factory, or meet the supplier. The entire commitment happens through an interface. Your job was making that interface trustworthy enough that a professional would stake their company's inventory budget on it. Results: $50B+ GMV platform, +20% daily transactions, +2.2pt NPS.
The design problem at Thermo Fisher was verification at distance under regulatory constraint. A batch-release decision in pharmaceutical supply chains requires a regulatory signature before product ships. The person signing cannot be present at every partner site. Your platform, mySupply, created real-time visibility across 9 sites in three geographies so that the human gate could function with confidence. All six pharma partners committed. Full adoption, no holdouts. Results: $20M+ margin recovered annually, zero to live in twelve months, with the batch-release signature preserved as the one irreplaceable human gate in the workflow.
Same problem, different altitude. In both cases, a human being with real consequences on the line has to make a high-stakes commitment through a screen, without direct access to the physical reality behind it. In both cases, the design work was building the epistemic infrastructure, the trust layer that lets someone act on what they cannot directly verify.
Confidence: HIGH. Both cases are published with full metrics. The structural parallel is clean.
When the enterprise-complexity version surfaces, say:
"The hardest design problems I've worked on share a structure: someone has to commit to a high-consequence decision through a screen, without being able to directly verify what's behind it. At Alibaba that was procurement buyers staking inventory spend on supplier quality they couldn't inspect. At Thermo Fisher it was batch-release decisions where a regulatory signature gated whether pharmaceutical product shipped. Six out of six pharma partners committed. Both required designing the trust layer, the part that makes the transaction possible at all."
Read that aloud. It does three things at once. It answers the market-translation question by making the design problem universal. It answers the enterprise-complexity question by citing regulated, multi-geography, multi-stakeholder systems with full partner commitment. And it positions you as someone who thinks in structural patterns rather than company-specific features. That last part is what a hiring committee evaluating a Director+ candidate actually wants to hear, whether they know to ask for it or not.
What the Two-Pivot Version Sounds Like
The mechanical difference matters as much as the conceptual one.
A candidate treating these as two separate objections answers the Alibaba question with geographic facts and market-scope language. Fine. Then the complexity question arrives ten minutes later, and they pivot to an entirely different register: enterprise systems, multi-stakeholder coordination, regulatory environments. The interviewer hears two defensive moves. Two rehearsed blocks. The candidate sounds like someone who studied the likely objections and prepared answers for each one. Which is exactly what they did, and it reads that way.
A candidate holding the verification-at-distance frame answers the Alibaba question and the complexity question in the same breath, because they are describing one design problem that happened to span two companies. The interviewer hears a thesis. They hear someone whose understanding of their own work is structural, not situational. The second version carries no rehearsal residue. It sounds like the way you actually think about what you do. The first version gets you past the question. The second makes the question work for you.
What This Frame Unlocks
Once you establish "verification at distance," it becomes a lens the interviewer applies to their own product without you asking them to.
A hiring manager at a fintech hears it and maps to underwriting decisions made on data the underwriter did not collect. Someone at a health-tech company maps to clinical workflows where a provider acts on information they cannot independently verify. A supply-chain hiring manager maps to exactly what you built at Thermo Fisher. You are giving them the translation key. They do the mapping. You are deploying your background, and the interviewer can hear the difference.
The frame also shifts the evaluative terrain. The interviewer moves from testing whether your specific company experience is relevant to their specific company, to testing whether your structural pattern applies to their structural problem. That is a conversation you win, because the pattern does apply to any product where decisions carry weight and information is incomplete. Which describes most products worth leading design for.
Use with caution: This frame works when the target company's product involves consequential decisions. If you're talking to a company whose core product is a lightweight collaboration tool or a consumer social app, "high-consequence decisions under opacity" will sound heavy. For consumer or low-stakes-transaction products, lead with Alibaba's growth metrics (+20% transactions, +47% new visitors from search) and the craft-execution story. Match their altitude.
The Consulting Passage
Do not explain what BCG Digital Ventures was. Name what shipped.
Red Cross disaster relief: zero to national deployment in six months, replacing six legacy systems, $847K disbursed across active events, 1,689+ cases processed in the first two weeks. Equinox+: zero to MVP in three months, 4.8★ App Store rating at launch, 600K+ premium members. Allē: 30M+ members enrolled, 3.2× redemption rate, lapsed-member reactivation at 47%. These products shipped, scaled, and were adopted in production. The work outlasted the engagement. That is the consulting answer.
Confidence: MODERATE. This reframe lands with interviewers whose consulting skepticism is about durability and real-world consequence. Less effective when the bias is about depth of organizational investment or speed of execution. If you sense the latter, the speed dossier in this series addresses the consulting-speed reframe directly, with the Red Cross timeline as the anchor case. Use that version instead of doubling down here.
Artifact Check
Your homepage reads clean: "Design Leadership for High-Stakes Systems." Title tag, meta description, and hero all point the same direction. One residual signal worth noting: the hero aside still references your current Head of Product title. This is addressed in a separate piece in the series. For the purposes of this dossier, the relevant check is simpler.
If you're sending a portfolio link before a conversation, confirm the recipient can access the full case studies behind the gate. Open the link from a browser where you are not already authenticated. The Alibaba page has your exact title, the $50B+ GMV figure, and the transaction-value split. The Thermo Fisher page has the 6/6 partner commitment, the $20M+ margin recovery, and the batch-release gate language. If those pages aren't rendering for the recipient, your strongest evidence is invisible at the moment it matters most.
Pre-Interview Quick Reference
Scan this in the lobby. On the call five minutes before. In the car.
"How does Alibaba translate to what we do?" Lead with your title. Head of Design & Research, North America. Professional buyers, procurement, desktop, 80% of transaction value. Bridge to the design problem: verification at distance. Confidence: HIGH.
"Have you worked at enterprise scale?" Pair Alibaba ($50B+ GMV, 200K+ suppliers) with Thermo Fisher (6/6 pharma partners committed, 9 sites, 3 continents, $20M+ margin recovered, regulatory batch-release gate). Name the structural pattern: high-consequence decisions under opacity. Confidence: HIGH.
"How does consulting work translate?" Don't explain the model. Name what shipped: Red Cross national deployment in six months, Equinox+ at 4.8★ and 600K+ members, Allē at 30M+ members and 3.2× redemption. "The work outlasted the engagement." Confidence: MODERATE.
If they push on Alibaba after the correction: Signal received. That tells you about the company.
If the target company's product is low-consequence/consumer: Drop the verification-at-distance frame. Lead with Alibaba growth metrics (+20% transactions, +47% new visitors) and Equinox+ speed (zero to MVP, three months).
The sentence to hold walking in:
I design the trust layer for decisions that carry real weight, and I've done it across B2B procurement, pharmaceutical supply chains, disaster relief, and consumer health. The pattern holds. The stakes vary.
Tuesday and Wednesday are the first full business days after the holiday. Inboxes will be lighter than usual. If you have outreach queued, that's your window.
- Backdoor references are expanding: The Wall Street Journal reported that companies like Zapier now require hiring managers to conduct live reference conversations before extending offers, sometimes calling as many as ten references for a senior role, which means every counter-narrative you rehearse needs to survive repetition by someone who is not you.
- Player-coach is the posting: Headway's current Design Director, Provider Experience role explicitly asks for a leader who owns strategic design initiatives hands-on while leading AI-native provider EHR features and raising team output, confirming that the IC-versus-leader objection is a false binary the market has already moved past.
- Portfolio gate still leaks: The full case-study pages at junochen.com return complete HTML before client-side access logic redirects unauthenticated visitors, meaning a recruiter viewing page source or using a non-JavaScript browser sees everything, including gated content that should be private.
- AI governance is becoming design scope: NIST's AI Risk Management Framework positions trustworthiness as something to be incorporated into the design, development, use, and evaluation of AI systems, which strengthens the case that "human-system operating contract" is a design leadership credential, not a policy credential.