# Design Critique Interviews: How to Review a Product You Didn't Build
Product designers are often asked to critique an app on the spot: "Open an app you use daily and tell us what you'd change." It tests taste, but even more it tests structure and empathy for constraints.
## A structure that keeps you focused
1. **Name the user and the job.** "A commuter buying a single ticket in under 30 seconds."
2. **Walk the main flow.** Narrate each screen briefly; don't critique everything at once.
3. **Separate observations from judgments.** "The pay button sits below the fold" (observation) vs "that probably slows first-time buyers" (hypothesis).
4. **Prioritise.** Pick the two issues with the biggest impact on the job, not ten small nitpicks.
5. **Propose and trade off.** Sketch a fix and say what it might cost: engineering effort, business goals, accessibility.
## What interviewers listen for
- Respect for the team that built it — assume there were reasons.
- Evidence thinking: "I'd check drop-off between screen 2 and 3 to confirm."
- Accessibility awareness: contrast, tap targets, screen-reader labels.
## Prepare two apps in advance
Choose one you love and one you find frustrating, and rehearse a 10-minute critique of each. Practising aloud matters more than notes; an AI mock interviewer like [Linkjob.ai](https://www.linkjob.ai/) can play the panel and ask follow-ups (I'm part of the team behind it).