Portfolio site verified July 9, 2026. Homepage title reads "Design Leadership for High-Stakes Systems." Alibaba, Thermo Fisher, Red Cross, and Allē teasers carry mandate-forward titles with metrics. Still open: Equinox+ teaser title remains generic ("Equinox+ · Teaser · Juno Chen") while every other case leads with scope and outcomes. Agentic Labs section says "Three live" but the homepage lists four entries.
"What Do You Count" essay card is visible on the homepage and the URL returns full TinyFish pricing HTML before the JavaScript password overlay fires. Any browser, any unfurl bot, any technically literate evaluator gets the content without a password. Remove the homepage link today. Server-side 401 if the URL must persist.
The organizing logic: your lead case answers the buyer's anxiety. Your supporting case neutralizes the objection that the lead case creates. Every strong portfolio presentation generates a predictable follow-on concern. If you only prepare the lead, you win the first five minutes and lose the next fifty.
Quick-Reference Matrix
| Buyer Type | Hiring Anxiety | Lead Case | Predictable Objection | Supporting Case | System-Credibility Read |
|---|---|---|---|---|---|
| Frontier AI | "Original AI thinking, or old UX on new surfaces?" | Trust essay + Agentic Labs | "Has she shipped AI at production scale?" | Thermo Fisher (agentic vision, $20M+) + Alibaba ($50B GMV) | Labs count mismatch undermines precision signal |
| Regulated Platform | "Can she ship fast where errors cause real harm?" | Red Cross + Thermo Fisher | "Enterprise background = too slow" | Equinox+ (0→MVP, 3 mo) + Allē (3.2× redemption, $42 CAC) | P0: Private essay HTML leak is a boundary-control failure |
| Enterprise | "Can she win a mandate without positional authority?" | Alibaba (gap → mandate → 3 sprints → +20% transactions) | "Can she build a team, not just do the work?" | Allē (3 designers, dual-surface) + Thermo Fisher (6 partners, 9 sites) | Equinox+ generic title breaks the senior-leadership read |
| Enterprise AI Org Transformation | "Can she change how our org works with AI, not just how she works?" | Trust essay (as org framework) + Agentic Labs | "Has she restructured a design org around AI?" | Alibaba (named gap → changed operations) + Thermo Fisher (9-site operating model) | Labs count inconsistency weakens org-standards credibility |
Frontier AI
Who this is. Founder-CEO or VP Product at Anthropic, OpenAI, Suno. Typically a founder screen, then a senior IC design panel. The founder evaluates product judgment. The panel evaluates whether your technical fluency is real or performed.
Buyer's hiring anxiety. Whether you've formed a defensible position on human-AI interaction that survived contact with production. (High confidence — consistent across multiple current postings and official guidance.) Anthropic's design postings specify production ownership and AI-powered tooling with real adoption. Their candidate guidance explicitly distinguishes AI-assisted preparation from AI-generated answers substituting for experience. Snap's Director of Product Design says AI makes it easy to build things that look acceptable, so she asks candidates why they built something and what substance sits behind it. The fear: polished AI demos with no rationale underneath.
Lead case. Trust essay first, Agentic Labs second. The essay names their problem before they articulate it: five handoffs, the trust ladder (Watch → Verify → Delegate), the line "accuracy is what the model achieves, consistency is what the design delivers." Brand Pulse, Retail Velocity, and Carrier IQ are live working systems, not concept prototypes. Lead with the framework. Show the Labs as proof you've built against it.
Predictable objection. "Solo builds. Has she shipped AI at production scale with a team and real users?"
Supporting case. Thermo Fisher. The case already closes with an agentic vision: five continuous agents, one irreplaceable human gate for batch QA regulatory release. The production reality is inarguable: 6 pharma partners, 9 sites, $20M+ margin, 100% adoption. Alibaba's agentic sourcing vision reinforces the throughline. You've been designing for system-mediated decisions across your entire career. The domain vocabulary is new. The design problem is fifteen years old.
System-credibility layer. The Labs section says "Three live" while listing four entries. A frontier AI buyer will catch the count mismatch. It reads as imprecision in the exact domain where you need to signal rigor. Fix the count or fix the inventory.
IC+manager frame. Tilt IC-heavy. Show the Trust essay's framework architecture and design decisions inside the Labs. This buyer wants proof you think at the artifact level. Team-building narrative comes only if asked.
Landmine. "Why are you in a product role right now?" One sentence: "I went where the hardest version of the problem was. The published work is where the design thinking lives."
Reserve. Allē and Equinox+. Don't surface unless they ask about consumer product range or team-building evidence.
Regulated Platform
Who this is. CPO or VP Product as hiring manager at Headway, Ramp, Gusto. VP Design as peer evaluator in later rounds. The hiring manager evaluates tempo. The design peer evaluates craft bar and team instinct.
Buyer's hiring anxiety. Speed under consequence. (High confidence — directly stated in current postings.) Gusto's design manager posting asks for shipping quality UX directly to customers while using AI to shorten feedback loops. A wrong answer in payroll or healthcare means a regulatory finding, or a person who didn't get paid. The anxiety: you'll import enterprise-speed process into their growth-stage tempo.
Lead case. Red Cross. Six systems collapsed into one, deployed nationally in six months, under federal oversight, with untrained volunteers as primary users. $847K disbursed, 1,689 cases in two weeks. There was no second deployment window.
Predictable objection. "Government and nonprofit. Can she move at startup speed?"
Supporting case. Equinox+ proves raw velocity: 0→MVP in 3 months, 4.8★. Allē proves business-metric ownership with a small team: 3.2× redemption, $42 CAC (down from $92 industry average), dual-surface redesign with 3 designers. Together they dissolve the "too slow" frame.
System-credibility layer. The private essay is your highest-priority problem with this buyer type specifically. Regulated platform companies evaluate boundary control as a proxy for operational judgment. Your portfolio currently delivers full TinyFish pricing strategy HTML to any browser before the JavaScript overlay runs. View-source, Slack unfurl bots, and any technically literate evaluator receive the content without entering a password. P0. Remove the homepage link. Server-side 401 if the URL must persist.
IC+manager frame. Balanced. Show craft judgment through Red Cross design decisions ("complexity in the system, not the interface"). Show team leverage through Allē (3 designers, two surfaces, shipped simultaneously from one strategic premise). The VP Design peer in round two will specifically test whether you elevate a team or absorb the work yourself.
Landmine. "Your background looks enterprise-heavy. How do you operate without that infrastructure?" Reframe: "Red Cross had no infrastructure. No design system, no research ops, no existing patterns. I built the operating model and the product at the same time. That's the job at your stage."
Reserve. Alibaba and the Trust essay. Don't lead with enterprise scale or AI frameworks here. Surface only if they ask about platform complexity or AI strategy.
Enterprise
Who this is. VP Design as hiring manager. Cross-functional panel of engineering and PM leaders at Salesforce, Atlassian, Adobe. The VP Design evaluates whether you can operate inside org complexity without losing design quality. The cross-functional panel evaluates whether you'll be a partner or a bottleneck.
Buyer's hiring anxiety. Mandate creation without positional authority. (Moderate confidence — inferred from consistent evaluation patterns across enterprise design searches, not confirmed by a current posting in this pass.) Enterprise design leaders build influence by naming problems nobody else has articulated and proving the solution works. The anxiety: hiring someone who needs the org to be set up for them before they can move.
Lead case. Alibaba. Full arc. Named the structural gap (25% of traffic generating 80% of transaction value on a platform built for consumers, not procurement buyers). Built the research case from 32 interviews, gaze tracking, and a Baymard audit. Secured the executive mandate. Led three cross-functional sprints. Outcomes: +20% daily transactions, -47% buyer security concerns, +2.2pt NPS. Diagnosis → mandate → execution → measurement.
Predictable objection. "Impressive individual work. Can she build and scale a team?"
Supporting case. Allē: team of 3 designers, two simultaneous surfaces (consumer iOS and provider backoffice), shipped from one strategic premise. Thermo Fisher adds multi-stakeholder complexity: 6 pharma partners, 9 sites across EU/NA/AU, 12 months.
System-credibility layer. The Equinox+ teaser title ("Equinox+ · Teaser · Juno Chen") is the weak link. Every other case teaser carries a mandate-forward title with scope and metrics. Equinox+ reads as unfinished. An enterprise VP Design scanning your site registers the inconsistency even if they can't name why. The body content is strong (600K+ members, 5 brands, 0→MVP). Match the title to the pattern.
IC+manager frame. Tilt manager-heavy. Lead with how you built the research case and secured the mandate at Alibaba, not with interaction design decisions. Show the Allē team structure. The cross-functional panel wants to know you'll make their lives easier.
Landmine. "Your most recent role is Head of Product. Are you still a design leader?" Reframe: "The portfolio shows where my judgment lives. The product title shows I operate wherever the problem requires it."
Reserve. Trust essay and Agentic Labs. Don't lead with AI frameworks for a traditional enterprise design leadership role. Surface only if the conversation turns to AI strategy or future org direction.
Enterprise AI Org Transformation
Who this is. CPO, CHRO, or VP Design evaluating for a transformation mandate at companies with large existing design orgs. The angle shifts by evaluator: a CHRO reads for change-management evidence and org-design vocabulary; a VP Design reads for craft credibility and whether you'll raise the bar; a CPO reads for cross-functional operating model change. Capital One's Senior Director posting asks for AI-enabled discovery tools and automated research workflows across a 10-person team. Gusto explicitly distinguishes personal AI adoption from leading a team through an AI workflow transition. Read those postings carefully. The verbs tell you what they're buying.
Buyer's hiring anxiety. Every candidate applying can use AI tools personally. That's table stakes. The buyer needs someone who changes standards, rituals, quality gates, and decision patterns across a design organization. (High confidence — Gusto and Capital One postings state this distinction directly.) The question on their side of the table: "Will this person change how the org works?"
Lead case. Trust essay, positioned as organizational framework. The five handoffs (Intent-Setting → In-Progress → Output Review → Decision Gate → Loop Feedback) are a change-management architecture. The trust ladder (Watch → Verify → Delegate) describes how an entire org learns to work with AI systems. Frame it that way before you show it. Then show Agentic Labs as proof you've built against the framework.
Predictable objection. "She has a framework and solo builds. Has she actually restructured a design org around AI workflows?"
Supporting case. Alibaba is the restructuring proof. You named a structural gap, changed what the org prioritized, built a new research practice from scratch, and created cross-functional sprint rituals that didn't exist before. Thermo Fisher reinforces: you built the operating system across 9 sites and 6 partners. The pattern is consistent. You change how organizations work. The outputs follow.
System-credibility layer. The Trust essay is public and well-titled. Good. The Labs inventory inconsistency ("Three live," four listed) weakens the precision signal a buyer evaluating org-wide AI standards needs to see. Clean the count.
IC+manager frame. Tilt manager-heavy, and the proof looks different from the Enterprise card. Here the manager evidence is "I changed how a team operates." Alibaba's mandate-creation arc is your strongest org-change evidence. The Trust essay proves you've thought about this at the systems level: org-wide adoption patterns, quality gates, decision architecture.
Landmine. "This framework reads as theory. Walk me through where it broke and what you changed." The Trust essay's Thermo Fisher connection is your answer: the decision-gate handoff was designed for a pharma regulatory release where the wrong automation would have cost $20M+ in margin. The framework came out of a system where getting the human-agent boundary wrong had a price tag you could quantify. Name the specific handoff, name the failure mode it prevented, name what you revised after the first deployment cycle.
Reserve. Equinox+ and Allē. Consumer product velocity and loyalty platform metrics don't advance the transformation narrative. Surface only if they question breadth of product experience.
-
Gusto's AI org distinction: Their current payroll design manager posting explicitly separates personal AI adoption from leading a team through an AI workflow transition, which is the clearest public language any target company has used to describe the Enterprise AI Org Transformation anxiety.
-
Anthropic's candidate AI guidance: Their published guidance on collaborating with Claude during hiring draws a hard line between AI-assisted preparation and AI-generated answers substituting for experience, which tells you exactly how their panels will evaluate your Agentic Labs.
-
NIST's critical infrastructure profile: The April 2026 concept note for a Trustworthy AI in Critical Infrastructure profile reinforces that enterprise AI evaluation is moving toward lifecycle risk management and governance vocabulary, not standalone model enthusiasm.
-
Suno's scale signal: Their Head of Product Design posting reveals 100M+ users, 200 employees, and a $5.4B valuation after a $400M Series D, which means the org-building mandate is real and imminent, not aspirational.