Product design portfolios have become a genre of performance. Final screens are polished, narratives are edited, and messy process moments are invisible. Here is how to evaluate what is actually underneath.
What Portfolios Show and What They Hide
| Portfolio shows | Portfolio hides |
|---|---|
| Visual quality and craft | Design decisions made under constraints |
| Final deliverable | How many iterations it took and why |
| The scope as presented | What was cut and why |
| The design alone | How the designer worked with PMs and engineers |
| Polished narrative | What went wrong and what they learned |
Question 1: What Did You Start With?
Ask the designer to walk back to the beginning of any case study. What was the problem as first stated? What did they think it was before they did research? A designer who can articulate clearly how their understanding of the problem changed during the project is showing you real design process. One who goes straight from brief to solution skipped the thinking.
Question 2: What Changed and Why?
Design work produces iterations. What decision changed most significantly from the first version to the final one? Why? A designer with genuine process will have a clear, specific answer: a user research insight, a technical constraint, a business decision that shifted the scope. A designer who says 'we refined the visual direction' is describing polish, not design.
Question 3: What Would You Do Differently?
The answer to this question is perhaps the highest-signal in a designer interview. Strong designers have clear, honest opinions about what their work missed or what they would approach differently with hindsight. A designer who says the project turned out well is either not reflective enough or not honest enough. Both are problems.
The design hiring practice uses these questions in every evaluation, alongside a live design exercise for senior hires and thorough reference checks with engineers who worked with the designer. Product designers in India are evaluated on the same rubric.
What to Look For Instead of Polish
- Shipped product evidence: can you find the feature in the real product?
- Engineering collaboration stories: how did the design change when engineering pushed back?
- Decisions under constraint: what got cut and why?
- Failure honesty: what did not work?
Running a design search and want the evaluation framework?
Tell us the role and the seniority. We will share the rubric and the three questions we use.
Book a Discovery Call →Portfolio evaluation is a skill that most non-design hiring managers underestimate. A strong visual impression is easy to achieve with the right tools and enough time; genuine design thinking is not. The design hiring practice evaluates candidates on process evidence and engineering credibility, not portfolio finish, and the hit rate on hires that stick is significantly higher as a result.
Evaluating designer portfolios and want the framework?
Send us the role and we will return the evaluation rubric within a week.
Book a Consultation →