The four rounds of a product design loop
Almost every product designer loop is some combination of four formats. Knowing which one you are in tells you which muscle to flex.
- Portfolio review — walk through two or three case studies and defend your decisions.
- App critique — evaluate an existing product and articulate what works, what does not, and why.
- Design / whiteboard challenge — solve an open-ended design prompt live or as a take-home.
- Behavioral & collaboration — how you work with PMs and engineers, take feedback, and handle disagreement.
The portfolio review: tell the thinking, not the pixels
The portfolio review is usually the highest-weighted round, and the most common failure is narrating screens instead of decisions. Interviewers already see the visuals — what they want is the reasoning: the problem, the constraints, the alternatives you considered, why you chose what you chose, and what the outcome was.
Structure each case study as a story: the problem and who had it, your role and constraints, the process (research, exploration, iteration), the decisions and their rationale, and the impact. Be honest about trade-offs and what you would do differently. Two deep, well-told case studies beat five shallow walkthroughs.
- Lead with the problem and the user, not the final screens.
- Show the alternatives you rejected and why — decisions need contrast.
- Be specific about your role versus the team's on collaborative work.
- Close with outcome and learnings, quantified where you honestly can.
The app critique: structured judgment
A critique round asks you to evaluate a product — sometimes theirs, sometimes a well-known app. It tests whether you have a point of view grounded in principles rather than taste. The trap is listing random likes and dislikes with no structure.
Anchor the critique on the user and their goals: who is this for, what are they trying to do, and where does the experience help or get in the way? Move from the high-level flow down to specific interactions, cite usability and accessibility principles, and prioritize — what is the one change that would most improve the experience? A prioritized, principled critique is the signal.
- Start from the user and their primary jobs, not surface aesthetics.
- Work top-down: flow and information architecture before pixel details.
- Ground observations in principles (usability heuristics, accessibility, hierarchy).
- Prioritize your recommendations instead of listing everything at once.
The design challenge: process over polish
The whiteboard or take-home challenge gives you an open-ended prompt ("design a way for people to split a bill," "redesign the onboarding"). Whether live or async, you are graded on process and reasoning far more than on a polished final artifact — especially in a live session.
Use a frame: clarify the goal and constraints, define the target user and their pain, generate several divergent directions before converging, sketch the chosen flow, and state how you would measure success and what you would test next. In a live challenge, think out loud and involve the interviewer — treating it as a collaboration signals how you actually work.
- Clarify the problem and success criteria before sketching anything.
- Diverge before you converge — show a few directions, then pick one with rationale.
- Think out loud and treat a live challenge as a collaboration.
- End with how you would validate the design (what you would test, which metric).
The behavioral and collaboration round
Designers ship through other people, so collaboration signal carries real weight. Prepare stories about a hard piece of feedback you incorporated, a disagreement with a PM or engineer you worked through, a project where you had to cut scope, and a time your first direction was wrong.
Use situation-task-action-result, lead with the outcome, and be genuine about what you learned. Interviewers can tell a rehearsed story from a real one — choose moments you actually grew from.
How to prepare
Invest most in your portfolio narrative — it is the round that most decides the outcome — and practice telling each case study out loud until the thinking is crisp. Then rehearse critiques and design challenges on a timer so the frames are automatic under pressure.
- Rehearse two case studies out loud until the decisions (not the screens) lead.
- Practice critiquing one app a day with a structured, prioritized point of view.
- Do timed design challenges and narrate your process throughout.
- Prepare collaboration-focused behavioral stories and run full mock interviews.