Product Design & UX · Chapter 5 of 5
The design loop and the portfolio
The portfolio review decides it, and it is judged on reasoning rather than on visuals.
| Round | What it tests | Prepare |
|---|---|---|
| Recruiter | Level and fit | A one-line description of the kind of problem you like |
| Portfolio review | Reasoning, not craft | Two or three cases, each with the constraint and the trade-off |
| Design exercise | How you work under ambiguity | Practise talking while designing |
| Cross-functional | Whether engineering and product will enjoy working with you | A disagreement with an engineer, resolved well |
| Behavioural | Feedback, iteration, failure | A design that shipped and did not work |
What a strong portfolio case contains
- The problem and who had it, before any screens.
- The constraint — technical, legal, timeline. Design without constraints is decoration, and interviewers are listening for it.
- What you rejected and why. The alternatives you did not ship are where the reasoning is visible.
- What happened after it shipped, including if it did not work. Metrics are named in 41% of postings for a reason.
- What you would do differently, specifically.
The most common portfolio failure
A beautiful case study that never states the problem, never names a constraint, and never says what happened afterwards. It demonstrates craft and leaves the interviewer unable to assess judgement — which is the thing they are hiring for.
Three cases with reasoning beat ten with visuals, every time.