Nine objections. Your background triggers all of them reliably, and you've been drafting answers.
You'll need those answers. But the decision that comes first is which kind of answer each objection requires, and getting that wrong costs more than showing up unprepared. Reframe an objection that actually needs a built artifact, and the evaluator watches you narrate around a hole they can already see. Concede a point your cases already cover, and you've handed back ground you were holding. The expensive error is the third one: pursuing a role past a structural mismatch, where nothing you say changes the outcome and the weeks are gone regardless.
What follows is the routing logic. Four categories, a boundary test for each so you can classify in real time rather than only on a pre-read, all nine objections sorted, and a reference table at the end.
Four categories, four boundary tests
Perception gap. The evidence is in your portfolio. The evaluator hasn't connected it to their concern, because of sequence, language, or the simple fact that they skimmed the case that answers it.
Boundary test: Can I point to a specific, existing artifact that answers this?
Route: Reframe. Different lead case, different language, earlier in the conversation. Nothing gets built; existing proof gets made visible.
Evidence gap. You have the experience. Your portfolio lacks the inspectable proof of it. No public artifact documents the thing.
Boundary test: Can I name a specific artifact I could start building today that would close this, and do I have the experience it would document?
Route: Build it. Use a verbal bridge until it ships, and name what you're building so the evaluator knows you've diagnosed the same gap they have. The bridge has a shelf life.
Experience gap. You haven't done the thing. No reframe changes that, and no artifact can document experience that isn't there.
Boundary test: Have I actually done this?
Route: Say so. Pair the acknowledgment with the closest compensating strength that is genuinely relevant to the scale the role operates at. Then adjust the pipeline. Which roles make the gap irrelevant, which make it fatal, and where is your search time going.
Fit boundary. The role requires something on entry that you cannot provide. The correct move is to stop.
Boundary test: If I gave the best possible answer to this objection, would the structural condition still be unmet?
Route: Off the pipeline. Redirect the hours.
Hybrid. Some objections sit across two categories, usually perception plus evidence. Your portfolio holds relevant proof, but the proof stops short of what the evaluator is testing.
Boundary test: Can I point to an existing artifact, and does that artifact fall short of the specific thing being tested?
Route: Both sides. Reframe what you have and name the artifact closing the remainder. Handle only the perception side and the evaluator leaves still waiting.
The two misclassifications that cost the most
Reading an evidence gap as a perception gap. This is the common one. You refine the narrative, try a new angle, lead with a different case, and the evaluator keeps waiting on proof that doesn't exist. The diagnostic is repetition: you've reframed the same objection across multiple conversations and it lands identically each time. That's a missing artifact, not missing language. The objection-spending piece made the related point about a third pass on the same stipulation signaling a construct being tested. If two reframes haven't moved it, reclassify.
Reading a fit boundary as an experience gap. You acknowledge, you compensate, you keep pursuing. But the requirement is written as a minimum, and minimums don't respond to compensating strengths. What you lose is not the role, which was never available. What you lose is the time you'd have spent on roles where your profile is strong.
Your site is still serving a restricted document
The TinyFish pricing essay remains publicly readable. The page delivers the full document before the client-side password check runs, so anyone with the link has the text. This has been flagged since Issue #7 and is unresolved.
It matters past itself. You make trust and governance claims elsewhere in the portfolio, and a restricted document that isn't actually restricted contradicts them at the infrastructure level, in front of exactly the evaluators most likely to check. Three fixes close it: strip the payload from the public response, enforce authorization server-side, or pull the link from the homepage. Until one ships, this condition discounts every adjacent objection you're trying to answer. High confidence.
The nine, classified
1. Head of Product title
Grain of truth: Your most recent title at TinyFish was Head of Product. An evaluator scanning the resume registers "product" and wonders whether design is behind you.
Classification: Perception gap. Your homepage already puts TinyFish in past tense and frames the move as going into product to learn how AI decision-making actually worked, then coming back to design.
Route: Get the frame out before the title surfaces. What you went to learn, what you brought back, why it makes you a stronger design leader now. TinyFish is context for your current positioning. Never portfolio proof. High confidence.
2. Portfolio-site framing and evidence governance
Grain of truth: The restricted essay is publicly delivered, as above. UAT Sentinel sits on the homepage without a confirmed reuse-permission decision.
Classification: Evidence gap. The missing artifact is a working evidence boundary: access control that functions, a resolved permission state. These are your two highest-priority portfolio repairs. High confidence.
3. AI-native credibility
Grain of truth: You haven't worked inside a frontier-model organization. Your approved portfolio shows substantial AI control machinery, but it doesn't yet contain one complete record of a disputed output producing a governed correction that changed system behavior on a verified later run.
Classification: Hybrid. On the perception side, the Labs, the Trust essay, and your TinyFish production context demonstrate AI fluency most design-leader candidates can't match. On the evidence side, the correction-lineage record — one correction traced through a system change to a verified improvement on comparable inputs — is specified and unshipped.
Route: Lead with the decision moment your work supports rather than the technology underneath it. Build the correction-lineage record. You've been running the verbal bridge for several cycles now, and the more evaluators who've heard a version of it, the less it buys you. Moderate confidence on the perception side, since it depends on the evaluator's own AI literacy. High confidence on the evidence gap.
4. BCG Digital Ventures consulting background
Grain of truth: The work came out of a venture-building consultancy. Evaluators from product companies may read the cases as outside recommendations rather than shipped products.
Classification: Perception gap. The Thermo Fisher, Red Cross, Equinox+, and Allē cases show zero-to-live product building, national deployment, and production operation, attributed to you as Product Design Director at BCG Digital Ventures.
Route: Lead with timelines and deployment scale. Red Cross national in six months. Thermo Fisher zero-to-live in twelve. If the concern moves to long-tail ownership, name the venture-building model honestly: you built and launched, the operating organization took it from there. High confidence.
5. Alibaba cross-market scope
Grain of truth: The brand prompts an assumption about Chinese domestic consumer e-commerce.
Classification: Perception gap. The portfolio identifies the role accurately: Head of Design and Research for Alibaba.com North America, a cross-border B2B buyer platform.
Route: Say it early, then move. "Alibaba.com North America, cross-border B2B, not the Chinese consumer marketplace." One sentence. High confidence.
6. IC+manager hybrid
Grain of truth: Your public record mixes leadership claims with solo-built AI work. The Labs on their own don't establish people leadership or management systems. The enterprise cases on their own don't establish current hands-on making.
Classification: Hybrid. Leadership proof lives in the enterprise cases, current technical fluency in the Labs. What's thinner than your headline range implies is inspectable management-system depth: how you ran reviews, how you held quality at distance, how you structured teams.
Route: Sequence by the scorecard shape the role is actually evaluating. Player-coach roles get the Labs first, enterprise team context second. Craft-director roles get the enterprise cases first, with the Labs following as evidence you still make things. A management-process case closes the evidence side. Moderate confidence.
7. Large-org scaling
Grain of truth: Your published record doesn't show managers reporting to managers, a design function of 20 to 50, or repeated annual planning and performance cycles. You haven't operated at that scale.
Classification: Experience gap, which converts to a fit boundary wherever multi-layer org leadership is a stated minimum. In your current pipeline, Vanta's Head of Design requires five-plus years leading large design organizations with director-level reports. That one is a fit boundary. The other checked roles describe player-coach or small-team leadership with no such gate.
Route: Acknowledge it plainly. Compensate with what matters at the scale the role really runs at: hiring judgment, quality standards, hands-on craft leadership. Roles that state multi-layer org stewardship as a minimum come off the list. High confidence.
8. Big-company speed
Grain of truth: Your most recent title was at a startup, and evaluators at larger organizations wonder about pace.
Classification: Perception gap. The BCG Digital Ventures work already documents speed inside complex, regulated environments. Red Cross national in six months. Equinox+ MVP in three. Thermo Fisher zero-to-live in twelve.
Route: Lead with the timelines. The proof is there; the only question is whether the evaluator has connected it to the concern they're carrying. High confidence.
9. Technical-builder and process evidence
Grain of truth: Your running Lab applications show that things work. They don't show how the things were built: code history, prompt provenance, rejected iterations, a complete production-correction loop.
Classification: Evidence gap. What's missing is an inspectable process or correction-lineage record. This overlaps with the evidence side of #3, and the correction-lineage artifact partially closes both. High confidence.
What the distribution says
Across the nine:
- Four perception gaps: Head of Product title, BCG DV background, Alibaba cross-market, big-company speed
- Two evidence gaps: portfolio governance, technical-builder process
- Two hybrids: AI-native credibility, IC+manager
- One experience gap that becomes a fit boundary at specific roles: large-org scaling
The perception majority is the good news. For the four objections you'll hit most often, the evidence already exists. The work is sequencing and language — getting existing proof to land before the objection has time to form. That costs preparation hours, not build hours.
The evidence gaps are the real workload. Two standalone, plus the evidence component inside each hybrid, gives you four distinct gaps. The correction-lineage artifact covers two of them. The governance fix covers one and removes a condition that's quietly discounting trust claims across the whole portfolio. A management-process case covers the fourth. Three builds, four gaps.
The experience gap you cannot build out of. You manage it by targeting. Vanta is the only confirmed fit boundary in the checked pipeline right now. Run the boundary test on each new role as it surfaces: is multi-layer org leadership stated as a minimum? If yes, the time goes somewhere else.
Routing reference
Pull this up before any conversation.
| Objection | Category | Route |
|---|---|---|
| Head of Product title | Perception gap | Reframe: lead with what you learned, why you returned to design. TinyFish is context, never proof. |
| Portfolio governance | Evidence gap | Fix: remove public payload or enforce server-side auth. Resolve UAT Sentinel permission. |
| AI-native credibility | Hybrid | Reframe: lead with decision moment, not AI tech. Build: correction-lineage artifact. |
| BCG DV background | Perception gap | Reframe: lead with timelines and deployment scale. Acknowledge venture-building model. |
| Alibaba cross-market | Perception gap | Correct: "Alibaba.com North America, cross-border B2B." One sentence, move on. |
| IC+manager hybrid | Hybrid | Reframe: sequence cases by scorecard shape. Build: management-process case. |
| Large-org scaling | Experience gap / fit boundary | Acknowledge. Compensate with small-team strengths. Disqualify roles requiring multi-layer org as minimum. |
| Big-company speed | Perception gap | Reframe: lead with enterprise timelines from BCG DV cases. |
| Technical-builder process | Evidence gap | Build: inspectable process record or correction-lineage case. |
- OpenAI's player-coach model: Their Growth design leadership role explicitly accepts experienced managers or senior ICs who demonstrate mentorship and team-level impact, which weakens the rigid manager-versus-IC binary that most objection prep assumes.
- Backchannel reference trends: June 2026 reporting summarized by Becker's Hospital Review found employers increasing off-list reference checks as AI-polished application materials made formal submissions harder to differentiate — making claim consistency across portfolio, interviews, and references a cross-cutting dependency.
- NIST on deployed-AI monitoring gaps: A March 2026 NIST report on monitoring challenges identifies human-AI feedback loops, drift detection, and the balance between automated and human-validated oversight as unresolved problems — the same territory the missing correction-lineage artifact would need to make inspectable.
- Capital One's AI-in-XD framing: Their Director posting for AI in Experience Design places organization-wide AI-process scaling under preferred qualifications rather than minimum requirements, separating transformation leadership from the multi-layer org gate that creates a fit boundary elsewhere.