UX Portfolio Guide: Structure & Strategy to Get Hired (2026)

If you're switching careers into UX design, you have probably heard the same advice repeated endlessly: "build a portfolio." What you hear far less often is what that actually means, what hiring managers are looking for, and how to build one when you have no client work yet.

This guide cuts through the noise. It covers what to include, how to structure case studies, what most junior portfolios get wrong, and how to present work that makes a real impression - even if you're starting from zero.

Why Your Portfolio Matters More Than Your Certificate

Certificates confirm that you completed a course. A portfolio demonstrates that you can do the work.

Most UX roles - from junior designers at agencies to in-house product teams - ask for a portfolio link before they ask about qualifications. That isn't an accident. Design is a practice-based discipline. Hiring managers want evidence that you can frame a problem, make decisions under constraint, and explain your reasoning clearly.

This doesn't mean certificates are worthless. Structured learning builds your vocabulary, your toolkit, and your confidence. But the certificate opens doors; the portfolio is what gets you through them.

A useful benchmark: when a hiring manager reviews a junior portfolio, they typically spend under five minutes on it. Your job is to make those five minutes count. If you want to see what good looks like in practice, our roundup of UX design portfolio examples shows real-world benchmarks across different experience levels, and the UX Academy student work page shows real portfolios built by career-changers on a live client brief.

How Many Projects Should You Include?

The answer almost every working designer will give you is: fewer than you think.

Three to five strong, well-documented case studies are the target. Not eight half-finished projects. Not every concept you sketched during a course. Three focused pieces of work that show your process, your thinking, and your decisions.

The instinct to show everything is understandable - especially when you feel like you don't have much yet. Resist it. A portfolio padded with weak work signals a lack of editorial judgement, which is itself a design skill. Curate ruthlessly.

If you have done a live-course project with a real client brief (more on this below), that counts as your strongest piece and should lead your portfolio.

What to Include in a Case Study

Each case study should tell a coherent story. The structure doesn't need to be rigid, but it should cover:

The problem. What were you trying to solve, and for whom? Describe the user need and the business or organisational context. If you inherited a brief, explain what was given to you and what questions you asked.

Your process. What research did you do? What methods did you use and why - not just "I did user interviews" but what you were trying to find out and what you learned. Show wireframes, affinity maps, journey maps, or sketches where they're relevant. Don't include every artefact - include the ones that shaped a decision. If you need a starting point for structuring research artefacts like user personas, there are templates that can help.

The decisions you made. This is the part most junior portfolios skip, and it's the most important section. What options did you consider? What did you choose and why? Where did you compromise? A candidate who can articulate a decision under constraint - "we had two weeks and three competing user needs, so I prioritised X because Y" - is far more compelling than one who presents a polished final screen with no context.

The outcome. What happened? If you tested your designs, what did you find? If the project was a course exercise, describe what you'd do next if you had more time or resources. Honesty about limitations reads well.

One rule of thumb: if a section of your case study doesn't help someone understand how you think, cut it.

Show Your Thinking, Not Just Your Screens

The most common mistake junior designers make is treating a portfolio like a design showcase - beautiful final screens, polished mockups, professional typography. That isn't what hiring managers are assessing.

They're assessing your problem-solving process. They want to see messy wireframes alongside final designs. They want to understand why the navigation ended up the way it did. They want evidence that you spoke to users, changed direction based on what you heard, and made considered trade-offs.

A case study that shows a scrappy mid-fidelity prototype and explains why you made three different structural decisions is more valuable than one that shows only pixel-perfect final screens.

This doesn't mean production quality doesn't matter. It does, and it improves with practice. But at junior level, the thinking is the differentiator.

Common Portfolio Mistakes

Too many weak projects. See above. Three focused pieces beat eight thin ones every time.

No narrative. A portfolio isn't a gallery. Each piece needs a beginning, a middle, and an end. "Here is the homepage I designed" isn't a case study.

No outcomes. Even approximate outcomes matter. "We tested with five users and found that two navigation patterns caused confusion; we revised and retested" is a real outcome. "The design was completed" isn't.

Ignoring accessibility and mobile. If your case studies never mention accessibility considerations or how designs adapt across screen sizes, that's a gap. You don't need to have solved every edge case; you need to show you considered them.

An impenetrable homepage. Your portfolio site (or PDF, or Notion page) should load fast, be easy to navigate on mobile, and make it immediately clear what you do and where your work is. Don't make a hiring manager hunt for the case studies.

Copying a template without adapting it. Portfolio templates are a useful starting point but they produce a recognisable visual language. Customise enough that your work is front and centre, not the template.

Format and Presentation Options

There's no single correct format. The options each have trade-offs:

A dedicated website (Webflow, Squarespace, Framer, or hand-coded) gives you the most control and signals a higher level of commitment. It's worth the effort if you're comfortable with the tools.

A PDF is easy to share and readable without any login. It's a reasonable starting point for career changers who want to start applying quickly. The downside is that it doesn't lend itself to interaction or video.

Notion or a similar tool is increasingly common, especially for early-stage portfolios. It's quick to set up and easy to update. The trade-off is that it looks low-effort to some hiring managers at larger organisations.

Figma presentations are a natural fit if your work lives in Figma already. They work well for sharing in interviews; less well as a standalone public portfolio.

Pick the format you can maintain and update. A polished PDF you actually keep current is better than a Webflow site you abandoned eight months ago.

If you want to learn what UX design is and how it differs from UI, read our explainer first - it'll help you frame your case studies with the right language.

Advice for Career Changers with No Client Work

This is the most common question we hear at UX Academy (myuxacademy.com): "How do I build a portfolio when I have nothing to put in it?"

The short answer is that you create the work.

Self-initiated projects. Pick a product you use regularly and find something broken, confusing, or underserved. Document the problem. Do your own research - even lightweight guerrilla interviews with friends or family. Design a solution. Write up the case study using the structure above. This is entirely legitimate. Senior designers do this regularly as creative practice.

Redesign projects. Take an existing product or service - a local council website, a subscription app, a booking flow - and redesign a specific part of it. Be clear that it's a redesign exercise, not commissioned work. The point is to demonstrate your process, not to claim a client relationship that doesn't exist.

Live-course briefs. This is the most underrated option. A structured course with a real client project gives you work you can actually own and discuss in interviews. At UX Academy, students work on a live project as part of the beginner UX design course, which means you finish with a real case study to anchor your portfolio - not a hypothetical exercise.

Volunteer or pro-bono work. Charities, community organisations, and small local businesses often have genuine design problems and no budget to address them. A real brief with real constraints and a real user base makes for a stronger case study than most classroom exercises.

Whatever the source of the project, the standards are the same. Document the problem. Show your process. Explain your decisions. Describe the outcome or what you'd test next.

If you're still figuring out whether UX design is the right career move for you, our guide on switching careers to UX design covers the practical considerations honestly - including what the transition actually looks like from different professional backgrounds.

A Note on Portfolio Reviews

Before you start applying, ask for portfolio feedback from people who hire designers - not just fellow students or friends. A working UX designer, a mentor, or a career coach with design industry experience will give you feedback that matters.

Pay particular attention to feedback on your case study narratives. The visuals are often the last thing experienced reviewers notice; the story is usually what stalls or advances a candidate.

If you're on a structured course, portfolio review should be part of the curriculum. At UX Academy, it's - because a portfolio without feedback is a missed opportunity.

Getting Started

Building a portfolio feels overwhelming when you have nothing in it. The way through is to start with one case study, however imperfect, and iterate from there.

Document everything as you go - your sketches, your dead ends, your research notes. It's far easier to build a case study from notes taken in the moment than to reconstruct a process from memory six months later.

You don't need to have worked with paying clients. You need to have thought carefully about a problem, made decisions, and be able to explain them. That's the standard, and it's achievable from a standing start.

If you want to understand the full picture of what a UX design career looks like - including the skills, tools, and day-to-day reality - that's a good companion read to this one. If you're still in the early stages, how to build a UX portfolio from scratch covers the beginner path step by step. And if you want to see what finished portfolios look like before committing to a structure, the UX portfolio examples breakdown shows real case studies reviewed against the criteria above.

---

If you're ready to build portfolio-ready work as part of a structured programme, the beginner UX design course at UX Academy includes a live client project, portfolio review, and weekly live sessions taught by our lead instructor, Natalia Veretenyk, and her team.

Not ready to commit yet? Book a free 15-minute call with an advisor - a no-cost way to see how we teach and whether the approach suits you.