Last validated: June 30, 2026
Surface question they'll ask: "Can she build long-term, or does she parachute in and leave?"
What they actually fear: Decks, not products. Polished short engagements with no ownership of what happens after the presentation ends.
Your fastest correction: "BCG Digital Ventures was venture-building, not advisory consulting. I was embedded as a founding-team product design director shipping 0→1 products — three of which are still live in production today, one nationally deployed for federal disaster relief. I can show you the adoption numbers."
Most hiring panels reconvene the week of July 7th after the holiday break. If you have conversations scheduled for that window, this is your prep week. Read the full dossier once now. Use the quick reference at the bottom before you walk into the room.
The category error you need to correct immediately
The interviewer hears "BCG" and maps you onto advisory consulting. Fly in, assess, produce a deck, fly out. That model exists at BCG. BCGDV operated differently.
BCG Digital Ventures was a venture-building studio. You were on the founding team building products. Product Design Director with direct reports, shipping code, standing up design systems, staying through launch and adoption. The engagement model was closer to an embedded startup than a consulting engagement, with one critical difference: you did this repeatedly across regulated, high-complexity domains.
Say it once, say it plainly, and move to evidence. The longer you spend explaining the BCGDV model, the more it sounds like you're apologizing for your background instead of deploying it.
What your target companies actually screen for
Before the evidence, establish the standard. "Shipped products" alone is too vague. The companies you're targeting have told you exactly what they want in their postings. Read their language.
Ramp's posting uses the heading "Actually shipping and demonstrating real impact" and specifies that the director "owns problems end to end." That language is designed to filter out the consulting stereotype. Concept-stage work without ownership of outcomes fails this screen. Your work passes it.
OpenAI's posting asks for "designing and shipping at scale" and someone who can "ship fast while elevating craft and quality." Speed plus craft. That is a BCGDV-shaped proof point.
Headway's posting goes furthest. Designers are expected to "stay involved through launch and iteration directly in code." Player-coach who owns strategic design initiatives hands-on. The anti-consulting filter, stated explicitly.
The proof standard across all three: shipped, adopted, and demonstrably impactful. Your evidence needs to answer at that level.
Four products. Still live. Still adopted.
Shipping is table stakes at this level. The harder test is whether what you shipped survived contact with real users and real operations after you were no longer in the room. Durability is the proof.
| Product | Status (June 2026) | Strongest metric | Lead with it when… |
|---|---|---|---|
| Equinox+ | Live, v11.35.0, 4.7 ★ (41K ratings) | 0→MVP in 90 days, live 6 years | Durability is the test |
| Allē | Live, v8.26.0, 4.87 ★ (13.6K ratings) | 3.2× redemption, CAC $92→$42 | Metrics and behavioral impact |
| Thermo Fisher mySupply | mysupply.patheon.com live | 100% partner adoption, $20M margin, 83% IRR | Enterprise scale, regulated complexity |
| Red Cross | Current status unverifiable | $847K disbursed, 1,689 cases in first 2 weeks | Federal oversight, legacy consolidation |
Thermo Fisher mySupply
A 0→1 supply chain platform for pharmaceutical manufacturing partners. Twelve-month build. Six pharma partners, nine sites, EU + NA + AU.
100% partner adoption. All six companies adopted the platform. $20M margin opportunity identified and validated. 83% IRR. The platform URL at mysupply.patheon.com still returns a live page today.
Enterprise pharma does not adopt supply chain tooling as a favor to a consulting team. Six-of-six adoption in a regulated, multi-geography environment means the product solved a real operational problem well enough that partners chose to change their workflows. That kind of adoption requires a product, a deliverable won't get you there.
American Red Cross Disaster Relief Platform
A nationally deployed caseworker platform replacing six legacy systems with one. Six-month build under federal oversight. You were Product Design Director and GM.
$847K disbursed and 1,689 cases opened in the first two weeks of deployment. National deployment inside a single disaster response cycle. Six legacy systems consolidated to one.
Honest caveat: this is an internal operational system. I cannot independently confirm it remains the active platform in 2026. What I can confirm is that it was deployed nationally, processed real disaster-relief funds under federal oversight, and replaced six systems the Red Cross had been unable to consolidate previously. If asked, say: "It was deployed nationally and processing real funds within weeks. Whether the Red Cross has since iterated on it, I can't say from outside, but the deployment and adoption were real and documented."
When to deploy this case: Lead with Red Cross when the conversation is about regulated complexity, federal-oversight environments, or consolidating legacy systems under pressure. De-emphasize it when durability is the specific test being applied. Your other three products carry that weight with verifiable current evidence.
Equinox+
The Equinox+ iOS and Android app. 0→MVP in 90 days across five brands. 600K+ premium members.
The app is live in the App Store today, version 11.35.0, updated June 23, 2026. Current rating: 4.7 with 41,230 ratings. Continuously updated for six years since your work shipped the initial product.
This is your strongest single answer to the parachute objection. A product you designed the foundation for in 2020 is still live, still above 4.7, still being actively developed. The architecture held. The product outlasted your involvement by half a decade.
Allē (Allergan Aesthetics)
A dual-surface loyalty platform for 30M+ members and 40K+ provider practices. iOS consumer app and provider web platform.
3.2× redemption rate increase. 47% lapsed member reactivation. CAC dropped from $92 to $42. The app is live in the App Store today, version 8.26.0, updated June 17, 2026. Current rating: 4.87 with 13,627 ratings.
Allē is your cleanest metrics story. The loyalty mechanics you designed drove measurable behavioral change that only compounds over time. A loyalty platform that reactivates 47% of lapsed members is a system built for long-term retention, and the numbers prove it worked. Those compounding behavioral effects are still running years after the engagement ended, which is precisely the kind of evidence that makes the consulting objection collapse under its own weight.
Where this objection has real substance
If a company specifically values multi-year internal org scaling at a single company, that is a genuine gap in your background. A structural difference, and one you should name before they do.
Growing a design team from 3 to 20 over several years inside one organization. Navigating headcount politics across budget cycles. Building promotion frameworks. Managing out underperformers over time, not over months. These capabilities accumulate through sustained tenure, and your BCGDV engagements, even at 12 months, do not fully replicate them.
What to say in the room:
"My BCGDV work gave me depth in standing up teams fast and shipping under pressure, but I haven't yet had the experience of scaling a single design org over multiple years. That's one of the reasons I'm looking for this kind of role now. What I bring instead is the ability to build team structure and design operations from zero, which is a different skill than inheriting and growing an existing org."
Pair it with TinyFish context verbally: your current role as Head of Product gives you sustained ownership, commercial accountability, and the experience of living with product decisions over time. This is the compensating signal. Do not put it in portfolio materials. Use it in conversation.
Which targets weight this factor most:
| Target | What their posting signals | Confidence that evidence resolves this |
|---|---|---|
| OpenAI | "5+ years managing and growing high-performing teams of 5–10 designers." Screens for sustained team-scaling tenure. The consulting objection compounds here. | Low |
| Headway | Player-coach model. De-emphasizes large-org scaling in favor of hands-on craft leadership. | High |
| Ramp | Cares about what you've built, not your training background. Ownership and impact over org tenure. | High |
Tier-specific risk
Enterprise companies with long design-org tenures. Salesforce, Google, Microsoft. The hiring panels often include people who have been in their roles for five-plus years and unconsciously benchmark candidates against their own tenure patterns. Your BCGDV background triggers the objection almost automatically. Lead with Allē and Thermo Fisher (enterprise scale, regulated complexity). Be prepared to spend real time on the structural correction. Risk level: high.
AI-native startups and high-velocity product companies. Ramp, Headway, most Series B–D companies building new product categories. These organizations are staffed by people who have moved between companies every two to three years themselves. The consulting pattern does not read as foreign because their own career patterns look similar. Lead with Equinox+ (0→MVP in 90 days, still live six years later) and the Allē metrics. Risk level: low.
Growth-stage companies building their first real design org. They want someone who will stay and build, but they also need someone who can stand up structure from nothing. That is precisely what your BCGDV experience trained you to do. Acknowledge the tenure gap, lead with the "building from zero" angle, use TinyFish verbally as evidence of sustained commitment. Risk level: medium.
Response phrasing for live conversations
These need to sound like a confident senior operator. If the phrasing sounds rehearsed, it backfires.
If asked directly about the consulting pattern:
"Fair question. Two things. First, BCGDV was venture-building, not advisory. I was the founding product design director on products that are still live today. Equinox+ just updated last week. Allē has 30 million members. These aren't concept decks. Second, the reason I'm in this conversation is that I want exactly what you're describing. I've built from zero repeatedly. Now I want to build from zero and stay."
This is your safest, most versatile response. Works in nearly every room because it corrects the category error and signals intent without overreaching. Use it as your default.
If it surfaces indirectly through a team-building question:
"I've stood up design teams multiple times in compressed timelines, which teaches you to hire well and build culture fast because you don't have the luxury of slow ramp. What I haven't done yet is scale a single team over multiple years, and I'm honest about that. What I'd bring is the ability to set up the right foundations quickly, which matters most in the first twelve to eighteen months."
Slightly higher risk. The "which matters most in the first twelve to eighteen months" clause works when the company is genuinely early-stage or building a new function. If the panel is hiring to scale an existing 10-person team, that framing can land wrong. Read the room before deploying the last sentence. If in doubt, end at "I'm honest about that" and let them ask the follow-up.
If a panel member pushes on ownership after departure:
"The best test of ownership is whether the product survives without you. Equinox+ has been continuously developed for six years since I shipped the foundation. Allē's loyalty mechanics drove 3.2× redemption and they're still running. I'd rather show you products that outlasted my involvement than tell you about a product I stayed on for five years that got sunset."
Your sharpest line. It reframes the entire evaluation. Use it when the room needs a reframe. If the panel is already skeptical and pushing, this lands. If they're asking a routine question and you escalate to this, it reads as defensive. Save it for the moment that earns it.
Quick Reference
Scan this before you walk in.
- The category error: BCGDV = venture-building with founding-team participation. Advisory consulting was a separate model. Say it once, move to evidence.
- The proof standard your targets use: Shipped, adopted, demonstrably impactful. Ramp: "what you've built." OpenAI: "designing and shipping at scale." Headway: "stay involved through launch and iteration."
- Strongest durability evidence: Equinox+ (live, updated June 23, 2026, 4.7 rating, six years running). Allē (live, updated June 17, 2026, 4.87 rating, 30M+ members).
- Strongest metrics evidence: Allē (3.2× redemption, 47% reactivation, CAC $92→$42). Thermo Fisher (100% partner adoption, $20M margin opportunity, 83% IRR).
- Red Cross: Use when the conversation is about regulated complexity or federal oversight. Don't lead with it when durability is the specific test. Current operational status unverifiable from outside.
- The real gap you must acknowledge: Multi-year single-org team scaling. Pair with "building from zero" as compensating strength. Use TinyFish tenure verbally as current evidence of sustained commitment.
- Highest-risk targets: Enterprise companies screening for long design-org tenure. OpenAI's 5+ year team-management requirement compounds the issue. Confidence in reframe: low.
- Lowest-risk targets: Ramp, Headway, AI-native startups where speed-to-ship and shipped evidence matter more than tenure pattern. Confidence in evidence: high.
- Your sharpest line: "I'd rather show you products that outlasted my involvement than tell you about a product I stayed on for five years that got sunset." Deploy when the room needs a reframe. Too sharp for routine questions.
- Default response: The "fair question, two things" version. Works in nearly every room.
Last validated: June 30, 2026. Product live-status checks current as of this date. Revalidate Thermo Fisher mySupply and Red Cross platform status before citing durability in conversations after July 15. Revalidate posting links for Ramp, OpenAI, and Headway before citing their language in conversations. Postings close and language changes without notice.
- Headway's second Director posting: Their Core Insurance & Design Systems role asks for team scaling, hiring, and design systems ownership, which weights the consulting objection differently than the Provider Experience posting analyzed here.
- OpenAI's "multiple altitudes" language: Their Product Design Manager posting asks for comfort spanning design details to system architecture and long-term strategy, which maps to a separate IC+manager hybrid dossier worth building next.
- Portfolio artifact inconsistency: The live homepage at junochen.com now visibly says "Head of Design" in the description but still carries "Product Designer" in the browser title tag and lists TinyFish as Case 05, creating a mixed signal that compounds the consulting objection before you even get in the room.
- Anthropic's design-engineer model: Their Education Labs posting frames the role as "part researcher, part product builder, part interaction designer" and measures success by user capability rather than engagement, which suggests a different proof standard entirely for AI-lab conversations.