Objection Dossier — AI-Native Credibility
Every AI-native company on your list will ask some version of this: have you actually designed for model behavior in production? You haven't, not inside a lab with a shipping model, and the reframe has to start there. This dossier covers what the interviewer fears underneath the question, exactly where your evidence stops, and how trust-and-consequence design becomes the strongest honest case you can make. Tier notes for Anthropic, OpenAI, Brex, Ramp, and Gusto — the objection lands differently at each.
Objection Dossier — AI-Native Credibility
Every AI-native company on your list will ask some version of this: have you actually designed for model behavior in production? You haven't, not inside a lab with a shipping model, and the reframe has to start there. This dossier covers what the interviewer fears underneath the question, exactly where your evidence stops, and how trust-and-consequence design becomes the strongest honest case you can make. Tier notes for Anthropic, OpenAI, Brex, Ramp, and Gusto — the objection lands differently at each.
Less Objection Than Evidence
When a structural concern surfaces — consulting background, Head of Product title, AI depth — the instinct is to keep explaining until the doubt feels resolved. At Director+ level that instinct works against you. Every extra sentence inside the objection teaches the evaluator to weight it higher. These four principles govern how long to stay in the answer and when to pivot to demonstrating the capability the role actually scores. They run as a chain, each one constraining the next. Read it once deeply, then re-scan in three minutes before any room where a known concern is likely to come up.
Less Objection Than Evidence
When a structural concern surfaces — consulting background, Head of Product title, AI depth — the instinct is to keep explaining until the doubt feels resolved. At Director+ level that instinct works against you. Every extra sentence inside the objection teaches the evaluator to weight it higher. These four principles govern how long to stay in the answer and when to pivot to demonstrating the capability the role actually scores. They run as a chain, each one constraining the next. Read it once deeply, then re-scan in three minutes before any room where a known concern is likely to come up.
Why She Left Design, Why She's Coming Back, and What Their Reaction Tells Her
Every company on your list will ask two questions: why you left design for a product title, and why you want back in. The reframes are below, grounded in your portfolio and the TinyFish chapter. But the point of this dossier is the diagnostic layer after each one. The interviewer's follow-up — the specific words they choose after you answer — tells you whether this company's design seat carries real authority or reports into a product org that treats design as execution. You should leave each conversation knowing whether you answered well and whether the company passed your test.
Four Scorecards Behind the IC+Manager Split
The IC+manager question shows up in every Director+ search. But it encodes four distinct role configurations — player-coach, growth director, technical builder-leader, multilayer executive — each running a different scorecard against different evidence. Your portfolio is strong for some of these and absent for others. This dossier classifies all four, maps your published cases to each shape with confidence ratings, and provides detection signals for figuring out which scorecard a company is actually running — since titles and job descriptions are unreliable indicators, and misclassifying costs more than any single weak answer.
Five Artifacts to Fix Before Someone Finds Them
Your private pricing essay is still publicly served. Google may still be showing "Product Designer" as your site title. UAT Sentinel is listed on the homepage but sits outside your approved portfolio boundary. Five artifacts, ordered by how likely a decision-maker encounters them before you get to speak. For each: what it currently shows, why it costs you, the concrete fix, how to verify the fix landed, and a prepared response if someone already saw the broken version. Two of these need to be fixed today.
The Scaling Gap — Which Parts You Can Answer, Which You Can't, and When to Walk Away
"Have you scaled a design team?" is the objection that comes up most and resists reframing most. This piece doesn't try to reframe it. It breaks "scaling experience" into ten distinct sub-capabilities, maps each against Juno's published portfolio evidence, and classifies every one as answerable, manageable, or disqualifying — including three sub-capabilities with no public evidence at all. Then it connects the classification to specific role shapes, with named postings, so you can sort before you spend.