I've reviewed somewhere north of a thousand portfolios over the years — Selfridges, then JD.com, with a long detour through agency and freelance reviewing. The pattern is depressingly consistent. Most portfolios are over-decorated, under-written, and structured in a way that makes it impossible to tell whether the designer can think.
The good news: the bar is lower than people assume. A portfolio that's honest, well-structured and clearly shows how decisions were made will beat a beautifully designed one with no thinking behind it, every single time. This guide is the version I wish I could send to every junior designer who emails asking for feedback.
What the portfolio is for
The portfolio is a screening artefact. It gets the candidate to the interview stage. Final designs and craft are necessary but not sufficient; the differentiator is evidence of thinking.
When I'm reviewing a portfolio, I'm answering four questions in my head:
- Did this designer understand the problem before they designed?
- Did they make real decisions, with real trade-offs?
- Did the work ship — and if not, why not?
- Can they write? Because most of senior design work is communicating, not pixel-pushing.
Everything in the portfolio either earns its place against those four questions or it doesn't.
Portfolio structure
Three pages do almost all the work. Everything else is optional.
The three pages every portfolio needs
- Homepage. Name, one-line positioning, three to five case study cards with specific titles, contact CTA. Nothing else.
- Case study pages. One per featured project. Self-contained. Readable in five to eight minutes.
- About page. A short bio, a clear current title, links to social proof, and how to contact you. Two short paragraphs is the right length.
Optional but useful: a "selected work" gallery for senior portfolios where some projects warrant inclusion without a full case study. A blog or writing page if you actually publish. A speaking page if relevant. None of these are necessary.
Number of projects
The most common single mistake: too many case studies. Quality compounds, quantity dilutes.
- Juniors and career switchers: 2 to 3 case studies. Quality matters far more than quantity.
- Mid-level (2-4 years): 3 case studies. Should show range across at least one collaboration-heavy project.
- Senior (5+ years): 3 case studies plus an optional selected-work gallery. Case studies should show systems-level thinking, not just feature design.
If you have six case studies at junior level, the reviewer assumes you can't tell which of your work is strongest. That's a worse signal than having two.
Case study anatomy
The anatomy this section sketches is the same anatomy I use to coach designers on portfolios. The deep version with templates lives in the case study template; what follows is the structural overview.
The nine-block case study
- Hero summary: one paragraph — company, role, problem, outcome.
- Context: what the business was trying to do and what was getting in the way.
- Your role: what you owned end-to-end, what you contributed to, who else was in the room.
- Research: lead with the insight, mention the method in passing.
- Problem framing: the sharpened question this case study answers.
- Process and decisions: the two or three real decisions you made and why.
- Solution: the final design, annotated with rationale.
- Outcome: numbers if you have them, honest qualitative evidence if you don't.
- Reflection: what you'd do differently and why.
The decision section (block 6) is where the portfolio is won or lost. Each decision follows the same micro-structure: what you decided, why, what trade-off you accepted. Three real decisions of this shape beats twenty paragraphs of generic process narrative every time.
Presentation quality
The portfolio's craft level should match the seniority being applied for. Three things to get right.
Typography and reading
Body text should be 16 to 18 pixels, with 1.5 to 1.75 line height, and a max-width of around 65 characters per line. This sounds technical but it's the single biggest determinant of whether a reviewer finishes a case study or bails halfway.
Image quality
Screenshots compressed correctly (WebP or AVIF, sized to actual display dimensions), with sufficient padding so they don't feel cramped. Hero images that load fast. Each image should be doing one job; multi-purpose images dilute the point.
Visual restraint
Restraint reads as confidence. Heavy gradients, parallax effects, drag-to-reveal animations, and oversaturated brand colour all signal a designer who's compensating. The strongest portfolios in 2026 lean editorial: clear typography, lots of whitespace, screenshots that earn their space.
Mobile responsiveness
Recruiters and hiring managers increasingly screen portfolios on phones. Between meetings, during commutes, while their coffee brews. A portfolio that falls apart below 600px gets closed and never reopened.
The minimum:
- Single-column layout below 720px.
- Body text remains 16px+ on mobile.
- Hero images don't overflow.
- Navigation collapses cleanly (hamburger or compressed inline).
- Case studies are still readable end to end on a phone.
The frustrating truth: most portfolios I receive in 2026 are still desktop-first and break on mobile. Fixing this is a one-evening job and a major hiring signal.
What recruiters actually do
Internal recruiters, agency recruiters, and hiring managers behave slightly differently. The common patterns from the 2024 to 2026 hiring cycle.
The implications for how you structure the portfolio are direct. The first case study slot is the most important. The opening of every case study has to do more work than the body. The homepage cards must telegraph what's in each case study without requiring a click.
Seniority expectations
What hiring managers expect to see, by level. Match your portfolio's pitch to the level you're applying for.
Junior (0-2 years)
- Evidence you can think, not just produce.
- Three case studies showing the same designer learning under real constraints.
- Honest about scope, role, and outcomes.
- Bootcamp projects are fine if honestly framed.
Mid-level (2-5 years)
- Evidence of trade-off thinking under stakeholder pressure.
- At least one collaboration-heavy project (with engineers, PMs, research).
- Shipped work with honest outcomes.
- One project that shows growth from junior baseline.
Senior (5-8 years)
- Systems-level thinking, not just feature design.
- Evidence of leading or influencing decisions beyond the immediate team.
- Demonstrated impact at the product or business level.
- Selected-work gallery for breadth.
Lead / Principal (8+)
- Evidence of org-level impact: design systems, hiring, mentorship, strategy.
- Case studies that frame the business problem first, the design second.
- Writing or speaking as a leadership signal.
- The portfolio is increasingly a CV-with-projects, not a craft showcase.
Platform comparison
Where to host the portfolio. Picked by job-to-be-done, not popularity.
Pick by what your portfolio needs to do
- Read.cv — writing-led, clean, growing. Best for designers whose differentiator is thinking and prose.
- Framer — best-in-class visual quality, custom feel, low effort. Best for senior visual designers.
- Squarespace — easy, reliable, conventional. Best for designers who want it to just work.
- Cargo — visual range, designer-friendly. Best for designers with strong visual identity.
- Custom-built — only if you can actually build it well. A janky custom site reads worse than a clean template.
- Notion / Standard Resume — fine for a quick MVP, weaker for senior roles where craft is part of the signal.
The platform matters far less than the case study quality. A strong case study on Squarespace beats a weak case study on a beautiful custom build, every single time.
Common mistakes
Six patterns that explain most portfolio rejections.
- Process worship. Long Double Diamond explanations. Frameworks are scaffolding, not content.
- Methods montage. Grid of every research method, each with one screenshot. Looks thorough; signals nothing.
- Vague pronouns. "We did this." Hiring managers want to know what you specifically owned.
- No problem, no decisions. Case study jumps from brief to final mockup with no visible thinking.
- Aesthetics over substance. Beautiful portfolio chrome wrapped around case studies that say almost nothing.
- Identical case study templates. All three case studies follow the exact same template. Bootcamp signal, reads as derivative.
Four-week build plan
If you're starting now, here's the process I've seen produce strong portfolios reliably. Faster timelines exist but the four-week version produces noticeably better outcomes than the two-week sprint.
From rough notes to portfolio that lands interviews
- Week 1: project selection. Pick the two to three projects. Write a one-paragraph summary of each. Get someone you trust to red-flag the weakest one.
- Week 2: case study writing. Write each case study in plain text, no platform, no design. Get two readers (one designer, one non-designer) to read each.
- Week 3: visuals. Four to six high-quality screenshots per case study. Compress and size correctly. Annotate where it adds clarity.
- Week 4: build, refine, test. Choose the platform. Build the homepage and three case study pages. Test on a phone. Test reading speed: a case study shouldn't take more than eight minutes.
Frequently asked questions
How many case studies should a UX portfolio have?
Three to five. Juniors aim for three. Mid-level three to four. Senior three plus an optional selected-work gallery. Quality compounds, quantity dilutes.
What do recruiters actually look at?
Ten to 15 seconds on the homepage. 30 to 60 seconds on the first case study. They look for role clarity, real constraints, named decisions, honest outcomes, and writing quality. They rarely scroll to the bottom on a first pass.
Should case studies show final designs or process?
Both, with thinking foregrounded. Open with problem and outcome, walk through the two or three decisions that mattered, use screens as evidence. Process diagrams for their own sake belong in the appendix.
Does my portfolio need to be mobile responsive?
Yes. Recruiters screen on phones. A portfolio that breaks below 600px gets closed. One-evening fix, major hiring signal.
Which platform is best?
Read.cv for writing-led, Framer for senior visual, Squarespace for hassle-free, Cargo for visual range. Custom only if you can build it well. Platform matters far less than case study quality.