Fixing the "Head of Product" Problem Before It Kills the Right Room

The Settled Sentence

Say this version. Out loud, in interviews, in networking conversations, without hedging:

"TinyFish was four people. The role that owned product strategy, commercial direction, and design was Head of Product. The scope was wider than any design-only title I've held."

That's the whole reframe. TinyFish explains the title. The portfolio proves the design leader. Everything below builds the reasoning beneath that sentence and gives you specific things to fix so the system sees what the humans in the room will see.

Do not say these versions. You will be tempted toward them under pressure. Recognize the drift and stop it:

• "Well, it's complicated — TinyFish was really small and we didn't have a separate design team, so the title was kind of..." — This sounds like you're apologizing for the company. It invites the interviewer to conclude TinyFish wasn't serious enough to matter.
• "I know it says Head of Product, but I was really doing design the whole time." — This sounds like you're asking permission to redefine your own role. It hands the interviewer the frame that the title is the truth and your explanation is the spin.
• "I didn't leave design." — Defensive. It answers a question nobody asked out loud and makes them wonder why you felt the need to say it.

The settled sentence works because it states a fact about the company's size, names what the role actually contained, and reframes scope as expansion. No apology, no hedge, no argument.

Why You're Invisible and How to Fix It

That ambient anxiety — am I even showing up in searches? — is a diagnosable signal problem with specific mechanics, and those mechanics are addressable.

How recruiter searches actually work

LinkedIn Recruiter exposes 40+ advanced filters including job title as an explicit filter surface. When a recruiter at Headway or Ramp searches for their next design leader, the first filter they typically set is title: "Head of Design" OR "VP Design" OR "Design Director" OR "Director of Product Design."

Your current title matches none of those strings.

On the ATS side, the problem is equally concrete. Greenhouse's talent filtering requires exact keyword matches: a searched keyword must exactly match the keyword in the application for the candidate to appear. If a reviewer marks "Head of Design" as a required keyword, an application containing only "Head of Product" does not surface. Greenhouse's Boolean search supports AND, OR, NOT, and exact-phrase matching with quotation marks. A recruiter running ("Head of Design" OR "VP Design" OR "Design Director") AND "product design" will never find a profile whose only title-level signal is "Head of Product."

Worse: a recruiter running ("Head of Product" NOT "Head of Design") is actively filtering you into a product-leadership pool and out of the design one.

The recovery mechanism requires your action

Greenhouse's full-text search indexes the entire resume and application, not just the title field. LinkedIn uses semantic signals including skills, structured attributes, headlines, and past positions in ranking. Keywords elsewhere in your profile and application materials can compensate for the title mismatch. But only if those keywords are actually present.

What to fix on LinkedIn

Headline. LinkedIn's headline is a flexible descriptive field that does not have to match your current title. Change it to something like:

This puts "Design Leader" into the headline, which LinkedIn's search systems index. It names the current role honestly. And it immediately contextualizes the title with the Alibaba credential, which is the single strongest design-leadership signal on your profile.

About section. Load it with the equivalence markers that recruiter searches trigger on: design leadership, product design, AI product design, trust architecture, regulated systems, design-org transformation, agentic workflow, enterprise platform. These are not decoration. They are search infrastructure. Every one of these terms represents a Boolean string a recruiter might run, and your profile either contains them or it doesn't. A sample opening:

That integrates seven equivalence markers without reading like a keyword dump. Adapt the specifics, but keep the density.

Skills section. Add: Design Leadership, Product Design, Design Strategy, AI Product Design, Enterprise Design, Design Systems, User Research, Design Management. LinkedIn Recruiter exposes skills as an explicit filter. If these aren't listed, you're invisible to any recruiter who filters by skill before reading profiles.

Experience description for TinyFish. Keep the title as "Head of Product." LinkedIn's policies require accurate, non-misleading work experience, and changing the title to something the company doesn't use crosses that line. Instead, front-load the description with design-leadership language: Led product strategy, design, and commercial direction for an AI-native platform. Owned end-to-end design decisions across product, brand, and go-to-market. The description is full-text searchable. The title stays accurate. Let the description carry the keyword load.

Confidence level on these fixes: High. The headline adjustment is well within LinkedIn's stated flexibility. The skills and About-section changes are standard optimization. The experience-description approach keeps the title accurate while solving the keyword gap.

What to fix in applications

When applying through an ATS like Greenhouse, your resume's full text is the recovery surface. The title field will say "Head of Product" and you cannot change that without lying. Everything else is yours to optimize.

Resume summary line. Place it directly below your name, before the experience section:

This puts "design leader" and "Head of Design" into the full-text index within the first fifty words. Greenhouse's full-text search shows a snippet under the candidate name, and this summary is what appears in that snippet.

Current-title field. If the ATS has a dedicated "current title" field separate from the resume upload, enter "Head of Product, TinyFish" exactly as it is. Do not improvise. The resume summary and experience descriptions carry the design-leadership keywords. The title field carries the truth.

Cover letter or "anything else" field. If the application includes one, use the first sentence to bridge:

This ensures the keyword "design leader" appears in one more searchable field.

Skills or tags fields. Populate with the same equivalence markers: design leadership, product design, AI product design, trust architecture, regulated systems. Greenhouse's talent filtering searches these. Leave them blank and you're relying entirely on the resume upload to carry the keyword load.

Confidence level: High. Greenhouse's documentation confirms that full-text search covers the entire application, and that keywords in resume body, skills, and notes all contribute to discoverability. This is accurate representation. You're ensuring the system can find what's actually true about your background.

What to Do When the Question Lands

The system fixes solve discoverability. They do not solve the moment in a conversation when someone looks at your resume, pauses on "Head of Product," and asks: So did you leave design?

Or the version that's worse because it's quieter. The version you ask yourself.

The grain of truth

It is a detour. The title does require explanation. A hiring manager scanning your LinkedIn will see "Head of Product" and, for a fraction of a second, categorize you as a product leader. That fraction of a second is real and you cannot pretend it away. Anyone who tells you "titles don't matter at this level" has never watched a hiring committee spend fifteen minutes debating whether a candidate's most recent title signals the right identity for the role.

So acknowledge it. The settled sentence does this: the scope was wider. Concession and reframe in the same breath.

What they're actually asking

When someone asks about the title, they are rarely asking only about the title. The compound fear is: Did she leave design because she couldn't advance in design? Is she coming back because product didn't work out? Will she be rusty on craft?

You must address the compound. Answering only the surface question leaves the hidden fears intact.

The settled sentence handles the first fear (scope expansion). The portfolio handles the second (she never left design; the work at TinyFish included design decisions at every level). The craft question resolves through the portfolio cases themselves, which demonstrate design judgment applied to complex systems.

Redirect to the evidence

The moment you've said the settled sentence, move to the portfolio. Here's what you have and what each piece proves:

Alibaba: Head of Design and Research, North America. Title-grade proof. You held the design leadership title at a company whose scale nobody questions. Confidence: high.

Agentic Labs systems work. Proof that your design thinking operates at the frontier. For AI-native companies, this is the lead edge. It shows you've designed for probabilistic systems, agentic workflows, and the trust problems every AI product team is currently struggling with. Pair with the trust essay if published. Confidence: high.

Red Cross. Federal oversight, national deployment, six-month timeline. Proof that you ship under consequence. Confidence: high.

Thermo Fisher. Twelve months, six pharma partners, nine sites, multi-role architecture. Enterprise-complexity proof. Confidence: high.

Equinox+. Three months, zero to MVP, five brands, 600K+ premium members. Speed proof. Confidence: high.

Allē. Loyalty and engagement design for Allergan's consumer platform. Deploy when the audience is consumer-facing. Hold when the conversation is enterprise or AI-native. Confidence: moderate.

Which evidence to lead with, by audience tier

Audience	Lead with	Follow with	Hold (and why)
AI-native (Abridge, Maven)	Agentic Labs + trust essay	Thermo Fisher (regulated AI)	Equinox+: speed-under-no-consequence doesn't differentiate here; they have that already
Growth-stage (Headway, Ramp, Gusto)	Red Cross (constraint dissolution)	Equinox+ (speed proof)	Alibaba: a growth-stage founder hearing "Alibaba" first anchors on "big-company operator" and spends the rest of the conversation looking for evidence that confirms it
Enterprise (Salesforce, Adobe)	Alibaba (scale + title)	Thermo Fisher (multi-stakeholder)	Agentic Labs: impressive but may read as too early-stage for an enterprise hiring committee's comfort

Lead with the evidence that matches the buyer's anxiety. An AI-native company doesn't need to hear about Alibaba first. They need to hear that you've designed for systems where outputs are probabilistic and trust is the product. A growth-stage company doesn't need the enterprise story first. They need to know you can ship under constraint without the constraint becoming process.

The reference-safety test

WSJ reporting from June 2026 documented companies like Zapier requiring up to ten live reference conversations for senior roles. When a former colleague gets that call and the question comes up, the answer they give should be a natural echo of the settled sentence: TinyFish was tiny, she owned everything, the title was just what fit.

If the people who worked with you would say that unprompted, the reframe is true. If they'd hesitate, the reframe needs work.

The internal version

The hardest audience for this reframe is you. Title shame is real. It's common among senior leaders who've taken scope-expanding roles at smaller companies, and it's corrosive because it shows up as micro-hesitations that interviewers read as low confidence. A half-second pause before saying "Head of Product" tells a panel more than any portfolio case can undo.

The fix is evidentiary. Read your own portfolio cases at junochen.com. Count the design decisions, the systems you shaped, the users affected. Then ask whether a person who did that work needs to apologize for the title on the business card.

The title is a four-person-company artifact. The portfolio is fifteen years of design leadership applied to systems where the stakes were real and the outcomes were measurable. Say the settled sentence, pivot to the evidence, and let the work close.