What hiring managers actually review
A hiring manager opens a portfolio expecting one of three outcomes: this candidate can clearly think, this candidate cannot, or the portfolio is too thin to tell. Their review is fast, ruthless and biased toward decision evidence. The work the portfolio shows matters less than the thinking the portfolio communicates.
The typical hiring manager review pattern in 2026 takes between four and twelve minutes per portfolio across the first screen. They scan the homepage, open one case study (usually the one positioned first), read the hero summary, skip to the decisions or outcomes section, and form a judgement. Only candidates who pass that initial scan get the full read.
What they're scanning for: evidence the candidate can frame a problem, name a decision, defend a trade-off, and articulate an outcome honestly. Polished visuals matter, but in 2026 polished visuals are table stakes — AI tools have compressed the floor on visual production. The differentiator is the writing. Designers who can write about decisions in plain language get callbacks; designers whose case studies read as PR-speak don't.
The full operational view of the discipline is in the UX portfolio guide. This article assumes you've read it and want to compare your portfolio against working examples by level.
What recruiters review
Recruiters are not hiring managers. They look for different signals, faster. A recruiter's review pattern is closer to 30 seconds on the homepage, then a verdict: pass this portfolio to the hiring manager, or don't. The thing they are filtering for is a short list of legible signals: seniority level, named companies, years of experience, specialism (research, product design, content, design systems), location and right-to-work.
Portfolios that lose recruiters in the first 30 seconds usually share three patterns. The homepage leads with mission statement or design philosophy. The candidate's seniority is unclear because no title or years are shown. The named companies are buried inside case studies rather than visible on the homepage. Each of these is fixable in under an hour.
Strong portfolios surface the recruiter-relevant facts above the fold: name, current or most recent role, the three to five case studies as cards or tiles with named companies, contact mechanism, and (optionally) a one-line specialism statement. Photo is optional and varies by region. The full structure for getting past the recruiter screen sits in how to get your first UX job for junior cases and UX CV mistakes for the CV-side companion.
Junior portfolio examples
A strong junior portfolio in 2026 carries two to three case studies and shows working capability across the production layer: flows, wireframes, content, accessibility, polish. The case studies don't need to be on shipped work. Side projects, redesigns of real public products and bootcamp capstones all work — provided they're treated with the same rigour as commercial work and the writing focuses on decisions rather than process narration.
What a strong junior portfolio shows
Case studies (2–3). Each with a problem statement, candidate solutions considered, evidence of decision, final design, honest outcomes. Reading time 5 to 8 minutes each.
Visual quality. Modern, restrained, accessible. Typography legible, contrast meets WCAG 2.2 AA, layout clean. Polish is table stakes.
Writing quality. Plain language, no design-thinking clichés, decisions named explicitly, trade-offs acknowledged.
About page. One paragraph on background, one on interests or specialism, contact details. Short and credible beats long and aspirational.
What it doesn't need. A long manifesto. Generic personas. Design-thinking diagrams. References to bootcamp methodology.
The most common junior portfolio failure is over-investing in process narration and under-investing in decision evidence. Six-week timelines documented sticky note by sticky note. Generic persona slides. Empathy maps the reader has no use for. These artefacts performed UX rigour when bootcamps were younger; in 2026 they signal a candidate who hasn't worked out what hiring managers actually want to see. The junior UX designer mistakes article covers the recurring patterns to avoid.
If you're at the junior end, the highest-leverage move is usually to cut: fewer case studies, less process narration, more decision writing. The portfolio checklist is the working pre-publish review tool.
Mid-level portfolio examples
Mid-level portfolios (3 to 6 years of UX experience) show the transition from production to decision. The strongest examples carry three to four case studies, all on shipped commercial work, with clear evidence the candidate owned meaningful design decisions rather than just executing on someone else's brief.
The mid-level signal hiring managers look for is judgement under constraint. What did the candidate cut to fit a tight scope? Where did they push back on a stakeholder request and what was the result? How did they translate research into a recommendation the team acted on? Mid-level portfolios that read as "I joined a team and made screens" don't pass the senior interview screen, regardless of how polished the screens look.
The strongest mid-level portfolios include at least one case study that names a difficult stakeholder situation. A redesign the engineering team initially resisted. A research finding that contradicted the PM's hypothesis. A scope cut that lost a feature stakeholders wanted. These case studies feel uncomfortable to write because they expose real friction — but they're also the ones that demonstrate the candidate can think under pressure. They are disproportionately well rewarded at interview.
The mid-level case studies I remember from interview review are the ones that named a difficult moment. A redesign the candidate fought for and lost. A research insight that arrived too late. A stakeholder who blocked the recommendation. The candidate's handling of these moments — not their wins — is what told me whether they were ready for the next role.
Senior portfolio examples
Senior portfolios (6 to 10+ years) work differently. The case studies are fewer (often three), longer (up to 10 minutes of reading time), and demonstrate not just design capability but design leadership: scoping projects, mentoring teammates, communicating risk to executives, translating research into roadmap decisions.
The strongest senior portfolios in 2026 include at least one case study where the candidate writes about a project that didn't fully succeed. Maybe shipping was descoped. Maybe the metric moved less than expected. Maybe stakeholders changed direction mid-project. Senior portfolios that show only wins read as inflated; senior portfolios that name an honest failure and reflect on it credibly build trust. The judgement layer that separates mid from senior is most visible in how the candidate handles the projects that went sideways.
Senior portfolios also commonly carry artefacts that signal cross-cluster work: an audit summary, a design system contribution, a stakeholder playback. These signal seniority more directly than case studies sometimes can. The senior vs junior UX designer article covers the operational difference in detail.
Lead portfolio examples
Lead and principal portfolios (10+ years) often deprioritise case studies in favour of strategic artefacts. Three case studies remain useful as evidence the candidate can still ship craft, but the bulk of the portfolio focuses on team direction, hiring, design strategy, stakeholder management at executive level, and the operational rituals the candidate has built into a team.
The strongest lead portfolios I've reviewed include a one-page "how I lead a design team" artefact — sometimes as a separate page, sometimes folded into the about page — that names the candidate's hiring philosophy, their critique rhythm, their stakeholder management approach, and their position on AI's role in the design function. Hiring committees for lead roles want to see this explicitly. Portfolios that bury it inside case studies make the committee's job harder.
Two things rarely belong in a lead portfolio: extensive Figma craftsmanship details and bootcamp-era persona work. Both signal a candidate who hasn't fully made the transition from individual contributor to design leader. The cluster's career-side companion is how to become a UX designer in 2026, which covers the broader market context.
Portfolio homepage examples
The homepage is where the recruiter screen lives. Three structural patterns work consistently in 2026.
The single-screen homepage. Name, role, one-line specialism statement, three to five case study cards with named companies and one-line summaries, contact details. No scroll required. This pattern works exceptionally well for mid-level and senior candidates whose case studies do the talking. It's also the hardest to execute; brevity at this level demands restraint that many designers find difficult.
The grid-led homepage. Photo or name above, then a visual grid of case study tiles below. Used effectively by candidates with strong visual craft and recognisable shipped work. Risk: the grid alone can read as a Dribbble shot collection; named companies and explanatory copy are non-optional.
The narrative homepage. A short paragraph framing the candidate's specialism, followed by case studies. Suits content designers, researchers and candidates with a specific point of view. Hardest of the three to do without slipping into mission-statement territory; the test is whether the paragraph contains specific, verifiable claims rather than generic aspiration.
Three patterns recruiters engage with
- Single-screen homepage — name, role, case study cards, contact. No scroll. Best for mid and senior candidates.
- Grid-led homepage — strong visuals, tiled case studies with named companies. Suits candidates with high visual craft and shipped product recognition.
- Narrative homepage — one paragraph framing, then case studies. Suits content designers, researchers, candidates with a point of view.
Patterns to avoid: hero with a generic mission statement, homepages that hide case studies behind navigation, animated intros that delay content, and anything that requires the recruiter to scroll twice before seeing case study names.
The deeper view of homepage structures lives in UX portfolio homepage examples.
Case study examples
The strongest case studies in 2026 share five structural features. Each is operationally diagnostic: if a case study has all five it usually gets a full read; if it's missing two or more it usually doesn't.
- Hero summary. One paragraph (3–4 sentences) covering company, role, problem in one line, outcome in one line. One hero image — the strongest single screen, not a montage.
- Context. What was the business trying to do? What was getting in the way? One paragraph naming the tension at the centre of the project.
- Decisions section. The heart of the case study. The two or three significant design decisions, with the alternatives considered, the evidence informing each call, and the trade-off accepted. This is where hiring managers spend the most time.
- Honest outcomes. What happened. Numbers where you have them, qualitative evidence where you don't. Honesty signals beat inflated metrics every time.
- Reflection. One short paragraph on what you'd do differently. Builds credibility and demonstrates the judgement layer.
Case studies that follow the case study template (a free download from UX Companion) consistently outperform improvised structures in our portfolio review work. The full set of examples — weak versus strong, with annotation — is in UX case study examples.
What weak portfolios do
Eight patterns recur in weak portfolios. They're worth knowing because they're often invisible to the person who built them.
- Process worship. Long sections on the Double Diamond, design thinking, or generic methodology that doesn't reveal the candidate's specific judgement.
- Methods montage. A grid of every research method the candidate has used. Looks thorough; signals nothing about decisions.
- Vague pronouns. "We did this" without naming what the candidate specifically owned.
- No problem, no decisions. Case study walks from brief to mockup with no visible choices.
- Aesthetics over substance. Beautiful portfolio chrome wrapped around case studies that don't say anything.
- Identical case study templates. All three case studies follow the same headings and structure in the same order. Bootcamp signal.
- Inflated metrics. "Increased engagement 320%" with no baseline, methodology or honesty about attribution.
- Hidden contact. No clear way to get in touch on the homepage. Costs interviews silently.
The 20 portfolio mistakes spoke is the operational deep-dive on these patterns.
What strong portfolios do
Strong portfolios share a different set of patterns. None is exceptional in isolation; together they compound into a portfolio that gets full reads.
- Front-load the strongest case study. The first case study from the homepage carries disproportionate weight. The strongest portfolios put the strongest work first and trust the candidate to defend the choice.
- Name the company every time. Anonymised case studies have a higher review-abandonment rate. NDA-respecting language ("a large UK retailer") is fine when actual names are blocked, but specific names beat vague ones every time.
- Show one screen well, not five badly. The hero image of each case study should be the strongest single screen, not a montage that no one zooms into.
- Write about decisions, not deliverables. "We decided to" carries more weight than "I created the wireframes for".
- Be honest about outcomes. Specific numbers where available; honest qualitative evidence where not. Stakeholders quote saying "that fixed the checkout drop-off" beats fabricated lift percentages.
- Make the reflection meaningful. "I'd revisit X if I had more time" beats generic "this was a great learning experience".
- Surface seniority signals. Years of experience, named companies, current role, specialism. Visible above the fold.
- Cut everything that doesn't earn its place. The portfolio is shorter, sharper and more specific than the candidate originally drafted. Restraint signals seniority more reliably than any other variable.
AI-era portfolio expectations
2026 hiring managers have specific expectations about how AI shows up in portfolios. Three patterns matter most.
AI-shipped work is a positive signal. If you've shipped AI features — generative UI, AI-assisted research synthesis, AI-driven content design — write about them with the same rigour as any other case study. Hiring managers want to see that the candidate can design under the constraints AI features introduce (uncertainty, hallucination, latency, trust).
Speculative AI redesigns are a negative signal. "I redesigned the AI search experience for [large tech company]" speculative case studies are increasingly recognised as filler. They demonstrate visual capability but not judgement under real constraint. If you don't have shipped AI work, write about the AI work you actually did internally — using AI tools to accelerate your synthesis, your wireframing, your content drafting. That's verifiable and current.
Honesty about AI use is rewarded. Portfolios that explicitly name the AI tools used (and the human judgement layered on top) are read more credibly than portfolios that pretend AI didn't exist. The senior hiring conversation now routinely includes "where did you use AI on this project?" — having a clear, honest answer ready is part of being interview-ready.
The deeper view on AI's place in UX work sits in the cluster: AI for UX designers and the authority anchor what AI should not replace in UX. For the case study side specifically, the case study template covers how to write about AI projects without slipping into hype.
Portfolio scoring framework
An operational scoring tool to apply to your own portfolio before publishing. Score yourself honestly across nine dimensions, 1 (poor) to 5 (excellent). Total /45. Aim for 35+ before submitting to a senior role; aim for 30+ for mid-level.
How to rate your portfolio honestly
- Homepage clarity. Can a recruiter tell within 30 seconds who you are, your level, your specialism, and what to read first?
- Case study count and depth. 3–5 case studies of comparable depth, each 5–8 minutes of reading time.
- Hero summary quality. Each case study opens with one paragraph naming company, role, problem and outcome.
- Decision evidence. Each case study explicitly names decisions, alternatives considered, and trade-offs accepted.
- Outcomes honesty. Specific numbers where available, honest qualitative evidence where not. No inflated metrics.
- Writing quality. Plain language, no design-thinking clichés, no vague pronouns.
- Visual polish. Modern, restrained, accessible. Polish is table stakes; aim for "professional" not "spectacular".
- Seniority signal. Years, named companies, role visible above the fold; specialism articulated clearly.
- Reflection and judgement. Each case study includes a short reflection that demonstrates self-awareness.
Score under 30: needs structural rework. Pair this score with the portfolio checklist for the operational pre-publish review.
Frequently asked questions
What does a good UX portfolio look like in 2026?
A strong UX portfolio shows decision evidence, not just visual output. Three to five case studies of comparable depth. Each names the problem, frames the decision the design had to inform, and shows what the designer did under constraint. Polish matters but isn't the differentiator. The differentiator is whether a hiring manager finishes the case study believing the candidate can think under pressure.
How many projects should a UX portfolio have?
Three to five case studies of comparable depth. More than five and reviewers stop reading; fewer than three and the body of work looks thin. Junior portfolios can run to two if both are strong. Senior portfolios sometimes show three. Fewer, deeper case studies outperform more, shallower ones.
Do UX portfolios still need a homepage in 2026?
Yes, and the homepage is doing more work than ever. Recruiters spend 10 to 30 seconds scanning before deciding to open a case study. The strongest homepages communicate seniority signal, named companies, specialism, and case study summaries above the fold. Homepages that lead with mission statements lose the recruiter before the first case study.
Should UX portfolios show AI work in 2026?
If you've shipped AI-feature work, yes — it's a positive signal. Fabricated 'AI redesign' speculative projects are a negative signal. Honest case studies of small AI projects with clear constraints beat speculative AI redesigns of large products every time.
What's the difference between a junior and senior UX portfolio?
Junior portfolios show production capability — wireframes, flows, polished screens. Senior portfolios show decision and trade-off — what the designer chose and why, what they didn't build, how they communicated risk. Juniors who get promoted to senior fastest are the ones who start writing about decisions before anyone asks.
How long should case studies be in a UX portfolio?
Five to eight minutes of reading time. 1,200 to 1,800 words plus screens. Shorter skips the thinking; longer rarely gets finished. Hiring managers reviewing 20 portfolios skim case studies; ones that get full reads have a strong hero summary, a clear decisions section, and honest outcomes.
Can I use a UX portfolio template in 2026?
Yes, but the template should disappear into the content. Recruiters spot bootcamp templates instantly. The UX Companion case study template pack is designed to fade behind the case study rather than lead it.