How to Evaluate a Product Designer's Portfolio
A portfolio is a set of claims. Your job is to check which claims the designer can support, which they can explain, and which they cannot. Polished screens prove taste. They do not prove that the designer defined the problem, made the tradeoffs or shipped the work.
Read each case for the problem first
Find the sentence that describes the user problem and the business constraint. If it is missing, or if it describes only the solution, you cannot judge the work. A good case states who the user was, what they were trying to do, what went wrong and what the team knew at the start.
Check ownership
Ask which parts the designer did themselves. Look for verbs that show decisions: 'I defined', 'I chose', 'I reversed'. Be careful with 'we', which can hide a small contribution inside a large team. A portfolio that never separates the designer's work from the team's work is hard to evaluate.
Compare the claimed role with the scope. A solo designer on a product with a large team is possible, but the case should explain how the work was divided and how decisions were made.
Look for the decision, not the result
Results matter, but they depend on many factors outside design. A good case explains the decision and why it was made, then reports the outcome with the baseline and measurement period. Treat unexplained percentages with caution, especially when the baseline is missing or the period is not stated.
A checklist for each case
| Question | What a strong answer shows |
|---|---|
| What was the user problem? | Specific user, specific task |
| What did the designer own? | Clear decisions, named role |
| What constraints applied? | Regulation, platform, language, timeline |
| What was considered and rejected? | Alternatives with reasons |
| How was success measured? | Baseline, metric, period, method |
| What would change next time? | Honest reflection on the work |
Test the portfolio with a conversation
Pick one case and ask the designer to explain it as if you were a new engineer joining the team. Ask what they would do differently and what they would not change. Their answers show whether they understand the work or only remember the visuals.
Ask about a project they could not finish, or one that did not perform. Most portfolios contain no failures, which is a sign the designer chose only the safest work to show. A candid account of a miss is useful evidence.
Watch for red flags
- Every case looks the same, with the same structure and no variety in the problems
- Metrics without a baseline or a time period
- Client logos used without a description of the designer's role
- Mockups presented as shipped products without a link or a store listing
- No mention of accessibility, edge cases or the states engineers needed
Use the portfolio to plan the next step
The best way to evaluate a portfolio is to use it to design the interview. Choose two cases that fit your current problem, prepare three questions for each, and ask for a short critique of one of your own screens. The portfolio then becomes the start of a working conversation, not a judgement from images alone.
Next step
Get help improving conversion
Send me the page or flow that loses people. I will tell you where the friction is and what to change first.
Open the conversion page