Hiring managers review design portfolios in five to ten minutes, often less for a first pass. They are not admiring your work; they are answering three questions: can this person think, can they execute, and can they explain their decisions? A portfolio of beautiful final screens answers only the second. This checklist covers what actually gets evaluated — with the reasoning per item, because the reasoning tells you how much effort each deserves.
Structure and selection
- Three to five case studies, not fifteen thumbnails. Reviewers judge you by your weakest visible piece. Curation is itself a design decision they are watching you make.
- Lead with the project most relevant to the job you want. Order is not chronological; it is argumentative. Your first case study gets triple the attention of your third.
- Show range across the set, depth within each. One research-heavy project, one visual-craft project, one shipped-under-constraints project beats five variations of the same dribbble-style shot.
- State your role explicitly on every project. On team projects, name exactly what was yours: I led the research and owned the checkout flow; visual design was {{Teammate role}}. Claiming a whole team project reads instantly as a red flag; precise credit reads as seniority.
- Include one messy middle. Rejected directions, an early version that failed testing, the whiteboard photo — evidence you iterate is evidence you can be worked with.
The case-study structure
Each case study should read as a story with a spine, scannable in two minutes:
- Context — {{Company type}}, {{your role}}, {{timeline}}, {{team}}. Two sentences.
- Problem — what was broken or missing, and for whom. State the constraint that made it hard: deadline, legacy system, conflicting stakeholders.
- Process — how you explored: research, sketches, options considered. Show the decision points, not every artifact. Why did you choose direction B over A?
- Solution — the final work, in enough fidelity to judge craft. Real content, not lorem ipsum, wherever possible.
- Outcome — what happened: {{Metric moved}}, {{qualitative result}}, or honestly, what you would measure if you could. A shipped date and an adoption number beat ten more screens.
- Reflection — one or two sentences on what you would do differently. This is the highest-signal, least-used section in portfolios.
Craft and presentation
- The portfolio site is itself exhibit one. Slow loading, broken links, or inconsistent type on a designer's own site contradicts every case study inside it.
- Readable performance: compress images; a reviewer on a laptop with forty tabs will not wait eight seconds per page.
- Typography and spacing discipline — reviewers judge the container as hard as the contents.
- Mobile check: plenty of first opens happen on a phone from an email link.
- Password-protected work: if key projects are confidential, say so and abstract them (redact the client, keep the process). An empty portfolio with an NDA note is still an empty portfolio.
Access and framing
- One link, no friction. The link in your resume and profile goes straight to work — not to a splash page, a login, or a PDF download.
- A short about page with your positioning: what kind of designer you are, {{Specialty}}, and what you want next. Hiring managers route candidates by this.
- Contact visible on every page. The moment of intent should never require a search.
- Name the file and URL professionally: {{yourname}}.design or similar beats a platform default with digits.
Before you send it anywhere
- Every case study answers: problem, your role, decisions, outcome.
- Someone outside design understood each project's point in two minutes.
- All links clicked through on desktop and phone this week.
- Your weakest piece is gone — you know which one it is.