Staff+ Product Design Interview Guide
All Terms You Need To Know
Process: Recruiter screen → portfolio review → onsite loop (design 1:1s, whiteboard, behavioral/"Googleyness") → team matching. You present your portfoliotwice.
What they're testing: Defending the Google brand promise while pushing new aesthetics. Whiteboards reward clarifying questions over fast, polished answers.
Common trap: Passing every round, then stalling in team matching — candidates call it harder than the interview itself.
Aggregator
IGotAnOffer — Google Product Designer interview
Source of the two-portfolio-round structure and the “defend the Google brand promise” language Google uses.
Aggregator
Exponent — Google Interaction Designer guide
Confirms 4–8 weeks excluding team matching, and that team matching can add months.
Firsthand
Blind — Google UX team matching threads
Candidates describing team matching taking 2–3 months, sometimes running before the onsite.
Process: Recruiter screen → two back-to-back 45-min rounds (past work + app critique) → onsite (panel portfolio, design challenge, behavioral).
What they're testing: L4 leads with craft and prototypes; L5 leads with scope and strategy influence. The app critique wants business fit, not UI polish.
Common trap: Giving the final panel the same case study depth as the screen — Meta expects you to sharpen it, not repeat it.
Aggregator
IGotAnOffer — Meta Product Designer interview
Two back-to-back 45-minute rounds: past work with the hiring manager, then app critique with a Meta designer.
Firsthand
Glassdoor — Meta Product Designer interview reports
Reported loop: pre-screen, portfolio presentation, then full loop with presentation, app crit, whiteboard, behavioral.
Firsthand
Blind — why Meta repeats the portfolio round
A Meta employee explains the repeat: first round is mid-senior designers, final round is managers and seniors.
Process: One 60-min designer round: short intro, then two projects walked through in real depth.
What they're testing: Howyou present counts as much as the work — rationale is treated as craft. Plus extreme detail and cross-device coherence.
Common trap: Broad but shallow. Apple prefers two projects you know inside-out over a wide portfolio skimmed fast.
Aggregator
Exponent — Apple Product Designer (UX) guide
The 60-minute designer round: 5–10 minute intro, then roughly two projects in depth.
Firsthand
Blind — Apple design interview process
Candidates report an hour on two or three projects, no whiteboard or app critique, and that craft and final experience matter more than wireframes.
Aggregator
Prepfully — Apple UX Designer guide
Corroborates the two-project walkthrough and the defend-your-decisions follow-up style.
Process: Recruiter → hiring manager → culture screen (against the memo) → function-specific portfolio round → sometimes a take-home. The loop isdecentralizedand varies by team.
What they're testing: Keeper Test thinking — would your manager fight to keep you? No down-leveling: you move forward or you don’t.
Common trap: Assuming a friend’s Netflix loop matches yours. Ask your recruiter what yours actually looks like.
Primary
Netflix — official Culture memo
The document interviewers score against, and the source of the Keeper Test and “dream team, not a family” framing.
Aggregator
IGotAnOffer — Netflix interview process
How the Keeper Test is applied to candidates, not just employees.
Aggregator
Testlify — Netflix hiring process breakdown
The separately-scored culture round: strong technical performance cannot offset a weak culture read.
Process: Every round maps to the 16 Leadership Principles, with a dedicated Bar Raiser guarding the hiring standard across the loop.
What they're testing: Stories, not just craft — Customer Obsession, Ownership, Invent and Simplify. Bring 5-10, since interviewers overlap on what they probe.
Common trap: Guessing which Principle a question targets. Also: impact under $1M, or stories older than 3-4 years.
Primary
Amazon — official UX interview prep
Amazon's own description of the UX loop: portfolio review, functional exercise, and Leadership Principles behavioral 1:1s.
Aggregator
IGotAnOffer — Amazon Bar Raiser interview
What the Bar Raiser is, why they sit outside the hiring team, and how they use the 16 Principles.
Aggregator
Exponent — Amazon UX Designer guide
Interviewers get questions drawn from two or three randomly assigned Principles — the reason to prepare a wide story bank.
Process: Design-specialist recruiter screen → onsite of 5-6 interviews across 5-6 hours, including a 45+15 min portfolio presentation and cross-functional 1:1s.
What they're testing: Teams run their own loops, but the portfolio round carries the most weight company-wide. Bring 2-3 projects you know cold.
Common trap: Under-preparing for the length of onsite day — stamina matters as much as a strong opener.
Aggregator
Exponent — Microsoft Product Designer guide
The 5–6 interview onsite across 5–6 hours, the 45+15 portfolio format, and team-by-team hiring autonomy.
Firsthand
Glassdoor — Microsoft Product Designer reports
Candidate accounts confirming portfolio-centric rounds and how much loop structure varies by team.
Process: Recruiter screen → portfolio phone screen (cuts 50-60% of candidates) → 4-5 round loop with cross-functional and Core Values rounds → hiring committee.
What they're testing: Real-time judgment: make a call, defend it, revise it under pushback. Expect to critique or redesign a live Airbnb screen.
Common trap: Treating the Core Values round as a formality — it can override strong technical performance.
Firsthand
Designer's firsthand Airbnb loop writeup
Round-by-round detail: 45-minute portfolio review with the hiring manager, 1-hour presentation to 6–8 people, no take-home.
Aggregator
OphyAI — Airbnb interview process
The design exercise on Airbnb's own product surface, and that the values round can override strong technical performance.
Aggregator
Interview Query — Airbnb hiring guide
Core Values as a distinct, heavily weighted round rather than a soft closer.
Process: Behavioral/culture round → product-sense round → aproduct concept presentationyou design and pitch live, with prep time.
What they're testing: Explaining one decision clearly to engineers, designers, and business stakeholders in the same room. Know Stripe’s actual product area.
Notable: Comp range is shared at the recruiter screen — unusually early transparency.
Aggregator
Prepfully — Stripe interview guide
The product concept presentation — prepared in advance, then pitched live.
Aggregator
Hacking the Case Interview — Stripe guide
Compensation range shared during the recruiter screen; overall 4–8 week process.
Firsthand
Blind — Stripe product design loop
Designer-specific sequence: portfolio review, portfolio presentation, whiteboard, design critique, behavioral 1:1s.
Process: Recruiter screen → portfolio presentation → live design or app critique → problem-solving → behavioral.Live critique over long take-homes.
What they're testing: Genuine affinity for Figma, measurable past impact, and reasoning through tradeoffs out loud instead of presenting a finished answer.
Common trap: Treating it as a generic design-tool interview — panels probe Figma’s product philosophy and community-led growth.
Aggregator
Hacking the Case Interview — Figma guide
The 4–5 round design loop, the preference for live critique over take-homes, and the ~25 day average.
Firsthand
Glassdoor — Figma interview reports
Five-round accounts and the prep deck Figma sends ahead of the presentation round.
Firsthand
Blind — designers comparing Figma and Stripe loops
Why the deep-dive rounds are the hard part: alternatives considered, and business impact of the work.
Process: Recruiter → hiring-manager portfolio review → 1-2 day design challenge → critique → cross-functional round → values round. The onsite alone is 5 rounds.
What they're testing: Breadth. Designers ship their own front-end (Codex), plus brand and copy. Level and team placement get set during the loop, from your strengths.
Common trap: A narrow, single-discipline portfolio when range is the thing being measured.
Aggregator
Exponent — OpenAI Product Designer guide
The five-round onsite, the 45-minute presentation to a panel of ten, and that level and product area are decided during the loop rather than before it.
Process: Discussion-driven rounds — UX process, interaction design, systems thinking, collaboration with Product and Research. Reflective, not presentation-heavy.
What they're testing: reasoning through ambiguity, justifying tradeoffs, designing for AI safety in real contexts. Calmer and more values-led than other labs.
Common trap: Over-rehearsing a slick narrative — they listen for real thinking about assumptions and edge cases.
Aggregator
Nora — Anthropic Product Designer guide
4–6 rounds over 3–5 weeks; hiring favours depth over polish, with discussion-driven rounds on tradeoffs and designing for safety.
Aggregator
IGotAnOffer — Anthropic PM interview
Nearest-neighbour evidence on how heavily Anthropic weights values and judgment relative to craft rounds.
How this guide was built
Every company card below carries its own source list — openWhere this came fromto see exactly which pages a claim came from and what each one contributed. Sources are tagged so you can weigh them yourself:
Company sources — Amazon's UX interview page, Netflix's culture memo. Treat as authoritative.
Named candidate writeups and Blind or Glassdoor reports. Specific and current, but one person's loop.
Named candidate writeups and Blind or Glassdoor reports. Specific and current, but one person's loop.
What this guide can't tell you: loops change quietly and vary by team, level, and region — several companies here explicitly run different processes per org. Round counts and timelines are typical, not guaranteed. Your recruiter is the only authoritative source foryourloop, and every company on this page will tell you the format if you ask.
How to Prepare Your Portfolio Presentation
Across all 11 companies above, the portfolio presentation is the single highest-weighted round. A few practices hold regardless of which company you're interviewing with:
Practice
Why it matters
Choose 2-3 projects, not 6+
Every company above explicitly rewards depth over breadth — you need to know your chosen projects inside and out, including numbers you didn't put on the slide
Lead with scope, not screens
Meta explicitly distinguishes L4 (leads with prototypes) from L5 (leads with scope and influence) candidates on this exact signal
Practice defending a decision under pushback
Airbnb tests this directly and explicitly; every other company's panel will informally probe the same thing via follow-up questions
Rehearse out loud, not just in your head
Apple and Figma both weigh delivery and rationale-articulation as core craft signals, not just "soft skills"
Know your story bank for behavioral rounds
Amazon and Stripe both run deep, multi-follow-up behavioral rounds — a 2-minute story is just the opening, not the whole answer
Before any of the above, make sure the underlying work clears the bar — see the Staff+ Portfolio Checklist → for the 16-point audit, and the Portfolio Directory → to study real examples from designers currently at every company listed above.
Frequently asked questions
Hardest is subjective, but by round count and duration, Google (4-6 rounds plus a separate team-matching phase) and OpenAI (5-6 rounds, 6-8 total screens) run the longest. Airbnb's single phone-screen round has the highest reported elimination rate (50-60%).
Not a different portfolio — the same strong case studies, re-framed. Emphasize scope and stakeholder influence for Meta/Google, prepare Leadership Principle stories for Amazon, and rehearse defending a decision live for Airbnb. The underlying work stays the same.
Less emphasis on a polished, rehearsed narrative and more on live reasoning through ambiguity — since many AI product patterns don't have established conventions yet. OpenAI also explicitly values breadth (some coding, some brand/copy work) over narrow specialization.
No. Most of the underlying scope-and-judgment criteria apply at any company hiring for Senior or Staff-level design roles — the FAANG-specific sections call out where that bar gets stricter.