The portfolio review is the loop. The work itself is assumed to be good — what is assessed is the reasoning, the constraints you were under, and the alternatives you rejected and why.
Design loops centre on the portfolio review, and the work is not what is being assessed — the reasoning behind it is. Expect to justify decisions you made years ago to someone who will ask what you rejected.
Practising this out loud matters more here than almost anywhere, because a portfolio you know intimately is very easy to narrate badly under time pressure.
Each round is run by the interviewer built for it, with its own scoring axes — not one generic interviewer asked to change subject.
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Six you can expect, in the register interviewers actually use. Answer them out loud before you read the next section — reading a question and answering one are different skills, and only the second is marked.
The gap between these two is most of your score, and it is easier to see than to be told.
“Walk me through this project. What was the constraint you were designing against?”
A guided tour of the final screens. The work is assumed to be good — the review is not about whether it looks right.
The constraint first — the deadline, the legacy system, the stakeholder, the technical limit — then two directions you tried, why you killed one, and what the launched version cost you. Reasoning under constraint is the entire rubric.
The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.
For Product Designer, a general round runs with Leila — customer insight, prioritization, product judgment, and execution trade-offs. It is the fastest way to find out which round you actually need to work on. The first session is free.
Practise a Product Designer interview →Before you practise, it is worth reading how the common rounds are marked: tell me about yourself, behavioral questions and STAR, and system design.