A design portfolio review day evaluates five to eight candidates in a structured session with a consistent rubric, a cross-functional panel, and a debrief that compares candidates against the role requirements rather than each other. Each candidate gets a 45-minute slot: 15 minutes presenting a case study, 20 minutes of questions using the three-question framework (what did you start with, what changed and why, what would you do differently), and 10 minutes of panel notes. The format produces better hiring decisions than scattered individual interviews because the panel sees every candidate in the same context.
Scattered design interviews across three weeks with different interviewers and no shared rubric produce hiring decisions based on who remembers their candidate best, not who assessed most rigorously.
A portfolio review day solves this by evaluating all shortlisted candidates in a structured session with a consistent rubric and a cross-functional panel. Here is how to run one.
When to Use This Format
A review day works best when you have five to eight shortlisted candidates for a product design role and want to evaluate them consistently. It is most valuable for mid to senior IC hires where portfolio quality and design thinking are the primary signals. For leadership hires, a deeper individual process is usually better.
The Panel
Three to four people: the hiring manager, a senior designer, an engineer who works with design, and optionally the product manager. The cross-functional panel prevents hiring based on visual taste alone and ensures engineering collaboration and product thinking are evaluated.
The Slot: 45 Minutes per Candidate
- Candidate presents one case study (15 min). They choose the project; you ask them to cover the problem, the process, the decisions, and what shipped.
- Panel questions using the three-question framework (20 min). What did you start with and what was your initial assumption? What changed during the project and why? What would you do differently? These questions cut through polish. The full rationale is in the portfolio evaluation guide.
- Panel notes in silence (10 min). Each panelist scores independently before discussion to prevent anchoring.
The Rubric
| Dimension | What to look for | Score 1-5 |
|---|---|---|
| Problem definition | Did they understand and reframe the problem before solving it? | |
| Process evidence | Did the process include research, iteration, and constraint handling? | |
| Decision quality | Were design decisions explained with reasoning, not just taste? | |
| Engineering awareness | Did they show awareness of technical constraints and collaboration? | |
| Self-awareness | Did they reflect honestly on what worked and what did not? |
Score independently, then debrief as a panel. Compare candidates against the rubric, not against each other. The design hiring practice uses this rubric for every evaluation.
The Debrief
After all candidates, the panel debriefs with scores visible. Discuss disagreements, not agreements, because the disagreements reveal where the rubric was interpreted differently. The hiring decision should be anchored on the rubric, not on who presented most charismatically. The product designers in India pool is evaluated against this exact framework when Talhive runs design searches.
