The buyer determines which version of your background leads. Not the company tier. Not the role level. A founder-CEO at an AI startup and a founder-CEO at a growth-stage platform share more evaluation patterns with each other than a founder-CEO and a VP Design at the same company.
"Same Anxiety, Different Room" mapped which pillar leads for which buyer. This version adds one axis: trust sensitivity. How likely is this buyer to inspect your portfolio boundaries, and what breaks if they do?
Probability of inspection is irrelevant. Cost is everything.
Quick-Reference Matrix
| Buyer | Lead | Support | Reserve | Trust Sensitivity |
|---|---|---|---|---|
| CPO | Enterprise Trust (Alibaba mandate arc) | 0→1 Builds (Thermo Fisher) | Agentic Labs demos | Medium — catches framing drift, not source code |
| VP Product | 0→1 Builds (Thermo Fisher, Allē) | Enterprise Trust (Alibaba scale) | Agentic Labs demos | Medium-High — clicks deeper, cross-references claims |
| VP / Head of Design | Enterprise Trust + Trust essay (full walk-through) | Agentic Labs (range) | TinyFish detail | High — portfolio construction is a craft artifact |
| Recruiter | 0→1 Builds (metrics) | Enterprise Trust (title + scale) | Agentic AI nuance | Low on source; High on access friction |
| Eng Leader (AI-native) | Agentic AI (TinyFish context + Trust essay + demos) | Thermo Fisher (systems) | Alibaba consumer metrics | Critical — will probe implementation; client-side trust violation is fatal |
Before You Use This Map
These are not optional. Do them once, before any outreach touches any buyer in this matrix.
- Check the browser title and meta tags. Your homepage headline reads "Design Leadership for High-Stakes Systems." Confirm the browser tab
<title>tag matches. If any surface element still reads below the level you're claiming in conversation, every buyer in this matrix sees the mismatch before they see your work. - Remove or server-side gate Essay 02. The
what-do-you-count.htmlpage delivers full HTML before the password check runs. Client-side overlay, no server enforcement. Any technically literate buyer receives the full text without entering a password. (Prior coverage.) - Lock Agentic Labs framing. Use identical language everywhere: "live demos built with real APIs and live agents across enterprise verticals." Not "shipped products." Not "TinyFish products." Nowhere.
- Verify every portfolio link weekly. A recruiter who hits a broken password gate does not try again.
CPO
Who this is. Chief Product Officer or SVP Product. Final-round or offer-stage. Controls headcount, level, reporting line.
What they're actually evaluating. Whether you reduce their cognitive load. CPOs own design outcomes but don't want to make design decisions. The portfolio review is a proxy for a single judgment: can I hand you the function and stop thinking about it? High confidence, sourced from SVPG product-leadership model and confirmed across multiple CPO search patterns.
Lead with Alibaba's mandate story. The sequence matters more than the metrics. You named a structural gap nobody had articulated (25% of traffic = 80% of transaction value, platform built for consumers not procurement). Built the research case from 32 interviews. Secured executive mandate. Then delivered. That sequence proves you generate your own brief. A CPO who sees that stops worrying about whether they'll need to manage you.
Support with Thermo Fisher ($20M+ margin, 83% IRR). Business-fluency proof. The CPO doesn't need to translate your impact for their CFO.
Cut or hold. Agentic Labs demos are too granular for this room. Use TinyFish as a one-sentence currency signal only. If they're at an AI-native company, the intelligence-layer frame does more work than demo details: "When an AI surfaces an output, what does it take for a human to trust it and act?"
IC+manager tilt. Manager. Show the mandate-building arc and cross-functional sprint leadership. Craft judgment surfaces through Alibaba's design decisions (removing the EIN gate, inline tier pricing), not through pixel-level walkthrough.
Trust sensitivity. Medium. Moderate confidence. A CPO will not view-source your site. But they will notice if any surface element, browser tab, meta title, LinkedIn headline, still reads below the level you're claiming in conversation. They pattern-match on coherence. The deeper risk: a technical stakeholder in the loop clicks through Essay 02, the client-side gate contradiction surfaces in the debrief, and you never learn why the process went cold.
Landmine. "Why did you leave design for product?" Deliver this in under 20 seconds. Moved to product to build AI-natively from zero. Shipped 3 products in 3 months. Returning for vertical domain impact and creative work. Hesitation here costs more than a weak answer.
VP Product
Who this is. VP or Senior Director of Product. Mid-process, often cross-functional panel. Controls whether design gets roadmap input or receives roadmap assignments.
What they're actually evaluating. Whether you make their product better without slowing their team down. SVPG's product-leadership model frames this buyer around value, viability, execution, and stakeholder alignment. They sit closer to execution than the CPO. They want design decisions that accelerated shipping, not design decisions that added process. Moderate confidence, inferred from cross-functional panel patterns at growth-stage companies, with SVPG as the closest published framework.
Lead with Thermo Fisher and Allē. Both show design driving product outcomes on a timeline. $20M+ margin in 12 months. 3.2× redemption, $42 CAC. Thermo Fisher's 5-module architecture proves you think in systems that ship. Red Cross reinforces the high-stakes 0→1 pattern if the conversation goes there: $847K disbursed, 6 systems consolidated to 1, national deployment in 6 months.
Support with Alibaba for scale. 25M+ sessions, cross-functional sprint model.
Cut or hold. Agentic Labs demos unless this VP owns an AI product line. If they do, shift the lead to the Trust essay's five handoffs and walk through Carrier IQ.
IC+manager tilt. IC-adjacent. This buyer wants product judgment. Walk through a decision you made that changed the product direction, not a team you built.
Trust sensitivity. Medium-high. Moderate confidence. VP Products click through portfolios more thoroughly than CPOs. They will notice if Agentic Labs demos are framed as "shipped products" on the site but described as "enterprise demos" in conversation. Keep the framing identical across every surface. One inconsistency, and the rest of your claims inherit the doubt.
Landmine. "How do you handle disagreements with product?" Thermo Fisher is the answer. You ran 32 warehouse interviews that surfaced 5 failure modes nobody on the product side had mapped. The research changed the roadmap. Frame it that way: you made the roadmap smarter, and the product team recognized it because the evidence was undeniable.
VP / Head of Design
Who this is. The design executive you'd report to, or the peer-level design leader evaluating whether you raise the bar. Early or mid-process. Controls craft assessment and cultural fit recommendation.
What they're actually evaluating. Two judgments running simultaneously. "Is this person's craft judgment as good as mine?" and "Will this person elevate the function or just execute?" Atlassian's design interview framework separates Product Thinking from Craft Excellence. Adobe's design-leader guidance adds a third dimension: did design generate new projects or only execute someone else's vision? High confidence, sourced from multiple published evaluation frameworks.
Lead with Alibaba's design mechanism. Walk through the specific decisions: why you removed the EIN gate, why trust signals at card level in search (34% of sessions sorted by Response Rate in month one), why inline tier pricing on PDP. Then connect to the Trust essay. The essay and the portfolio validate each other because Alibaba is explicitly named in the essay body. This buyer will notice that structural advantage. Most candidates have a portfolio and a blog. Yours are the same document.
This is the buyer who gets the full Trust essay walk-through. §01 (TinyFish cold start fix) → §02 (Carrier IQ, Thermo Fisher consistency) → §03 (Agentic Labs demos as five-handoffs evidence) → §04 (Alibaba trust ladder at enterprise scale). CPOs get §04 only. Engineering leaders get §01 and §03. This buyer gets the architecture.
Support with Agentic Labs demos as technical range evidence. The cross-vertical pattern shows systems-level design thinking. Frame precisely: "I built these to test the five handoffs framework across different domains." Solo-build framing needs the follow-on loaded and ready: "The team evidence is Alibaba and Thermo Fisher. The solo builds prove I can work in the medium myself, which is how I maintain craft judgment as a leader."
Cut or hold. TinyFish operational detail. This buyer cares about design output. Use TinyFish only as the bridge sentence.
IC+manager tilt. Match the role. Report-to role: tilt manager, show Alibaba's team leadership and Thermo Fisher's function-building. Peer or Staff IC role: tilt craft, show design decisions and the essay's framework.
Trust sensitivity. High. High confidence. This buyer evaluates portfolio construction as a craft artifact. Typography, density, communication quality, how you approach software as a medium. A design leader whose portfolio has inconsistent framing between site elements and conversation is making a craft error in the medium they claim to master. They won't tell you that's why you didn't advance. You'll just get the "we went another direction" email.
Landmine. "These Agentic Labs projects look like solo work." Don't get defensive. Research prototypes for a design problem nobody has solved yet. Team leadership evidence lives in the enterprise cases. Say it that directly.
Recruiter / Search Partner
Who this is. Internal recruiter, external search partner, sourcing specialist. First human gate. Evaluates in 60–90 seconds on the first pass.
What they're actually evaluating. "Can I defend this candidate to the hiring manager in one paragraph?" They need role/level clarity, impact metrics, and zero friction accessing your work. High confidence, sourced from practitioner recruiter interviews.
Lead with 0→1 builds. Thermo Fisher ($20M+ margin, 100% adoption) and Allē (3.2× redemption, $42 CAC) compress into recruiter-friendly bullets. These numbers survive the telephone game from recruiter to hiring manager to panel without distortion.
Support with Alibaba for title and scale. "Head of Design and Research, North America" at a $50B+ GMV platform is a level signal that requires no explanation.
Cut or hold. Trust essay, five handoffs, Agentic Labs framework language. Too conceptual for this gate. Save it for the rooms where it wins.
IC+manager tilt. Match the posting language. "Staff Product Designer" = lead with craft and outcomes. "Director" or "Head of" = lead with team scope and business impact. Recruiters screen against the posting, not against a nuanced understanding of what the role actually needs.
Trust sensitivity. Low on source inspection. High on access friction. High confidence on this split. A recruiter will not view-source your portfolio. But a broken link, a stalled password prompt, a slow-loading page — they move on. With Essay 02, the danger isn't discovery of the client-side gate. It's that they click, hit a password wall, and open the next tab. You never know it happened.
Landmine. "Your current title is Head of Product — are you sure you want a design role?" Three sentences max. Moved to product to build AI-natively. Shipped 3 products in 3 months. Returning for vertical domain impact and creative work. If the recruiter needs more than that, the answer isn't working.
Engineering Leader (AI-Native)
Who this is. VP Engineering, Staff+ engineer, or technical co-founder at Anthropic, OpenAI, Brex, Stripe, or similar. Cross-functional panel or triad interview. At AI-native companies, this person often holds a veto.
What they're actually evaluating. Whether you understand how the system actually works, or whether they'll spend half their time translating. Brex's AI design roles ask designers to delegate real work to agents and ship working demos. Anthropic's engineering roles expect engineers to own UX quality including latency and reliability. These companies don't separate "design thinking" from "technical thinking." The engineering leader is evaluating whether you operate in the same problem space or adjacent to it. High confidence, sourced from multiple AI-native role descriptions and triad interview patterns.
Lead with the Trust essay's five handoffs, then Agentic Labs demos as evidence. The handoffs (intent-setting, in-progress visibility, output review, decision gate, loop feedback) map directly to the control surfaces engineering leaders care about: agent traces, auditability, attribution, evals. Use TinyFish context heavily here: "I work with LangSmith traces daily. I know where signals break down between what an agent did and what a user experienced." Practitioner language, not design language. The Carrier IQ origin story from the essay opens the door:
"The first agent I built lied to me. Cheerfully."
That sentence proves you've built, not just designed. It earns you the next five minutes.
Support with Thermo Fisher's system architecture. Five modules, one irreplaceable human gate for batch QA regulatory release. Connects directly to the trust framework and proves you understand where automation must stop.
Cut or hold. Alibaba's consumer metrics (+7% DAU, +47% new visitors). Valid outcomes, but they read as marketing metrics to an engineering audience. Wrong vocabulary for this room.
IC+manager tilt. IC hard. This buyer wants your hands in the work.
Trust sensitivity. Critical. High confidence, sourced from developer hiring culture, security standards, and portfolio-as-product evaluation patterns. This is the buyer most likely to inspect source and evaluate your portfolio as a shipped product. Developer hiring culture includes view-source as a screening behavior. A client-side JavaScript password overlay on Essay 02 is, to this buyer, a textbook access-control violation: full HTML delivered before authentication, visual-only gating, no server-side enforcement. For a candidate whose entire thesis is "trust is the new interface," that contradiction is not recoverable in the room. The asymmetry is total. Low probability, career-grade cost.
Remove the Essay 02 link from the public site or implement server-side gating. Frame Agentic Labs demos as "live demos built with real APIs and live agents" — never "products I shipped." This buyer will ask follow-up questions that expose the difference.
Landmine. "Did you build this or design this?" Both. The Agentic Labs demos are hands-on builds with real APIs. TinyFish is production product work. But do not overstate: "I built the UX, the interaction logic, and the agent orchestration for the demos. The production infrastructure at TinyFish is engineering-led and I own product and design." Precision here is respect. Engineering leaders can smell overreach from across the table.
- Brex's agentic design language: Their Staff Product Designer, AI posting explicitly names delegation, in-flight supervision, output review, and trust in automation touching money as the core design work — nearly a 1:1 map to the five handoffs.
- Atlassian's triad interview format: Their design interview handbook describes a cross-functional panel where engineering and product counterparts evaluate trade-off reasoning, which is the clearest published model for how the Engineering Leader card plays out in practice.
- Gusto's AI-native design org: Their recent article documents how the design team rebuilt its operating model around AI tooling and MCP-connected design systems within a single quarter — relevant if a VP/Head of Design buyer asks how you'd transform a team's workflow.
- Figma's 2026 hiring data: Their research shows 73% of hiring managers now expect AI-tool proficiency and 56% report increasing demand for senior design hires, which confirms that the IC+manager tilt calibration matters more than ever at Director+ level.