What should a UX design portfolio include?

A UX design portfolio should include 2-3 detailed case studies that show your full design process, not just final screens. Each case study should cover the problem you were solving, the research you conducted, the insights that shaped your decisions, the iterations you went through, and the outcome. A brief about page and contact details round it out. Quality matters far more than quantity.

How many case studies do you need in a UX portfolio?

Two to three strong, well-documented case studies is the right number for most job applications. Hiring managers rarely have time to read more than that, and a portfolio with eight thin projects signals that you are padding rather than confident. Put your effort into making each case study genuinely good, with clear evidence of research and decision-making, rather than adding more work to fill space.

What makes a UX portfolio stand out to employers?

The single biggest differentiator is evidence of real thinking. Most portfolios show polished final screens; the ones that stand out show why decisions were made, what was tried and rejected, and what the designer learned. Real users involved in research, real constraints, and a clear narrative thread through each project will set your portfolio apart from the majority. Working on a real client brief rather than a self-chosen redesign exercise is also a genuine advantage.

Can you build a UX portfolio with no experience?

Yes, and most people entering UX do exactly that. The key is treating your early projects like real work: define a genuine brief, recruit real users for research, document your process honestly, and reflect on what you would do differently. Volunteering for charities or start-ups, doing course projects with real client briefs, and thoughtful personal projects all count. The portfolio does not need to show paid work; it needs to show sound UX thinking.

UX Design Portfolio Examples: What Good Looks Like

Your CV will get you a conversation. Your portfolio will get you hired.

Most hiring managers spend two to three minutes on a portfolio on first pass. A significant number make up their minds in the first thirty seconds. Not because they are being harsh, but because most portfolios make the same mistakes immediately obvious, and experienced reviewers have learned to spot them fast.

This post breaks down what those mistakes are, what a strong UX portfolio actually looks like, and how to build one even if you are starting from scratch. We have also included examples from UX Academy graduates who built their portfolios through real client projects.

What hiring managers are actually looking at

When a recruiter or design lead opens your portfolio, they are not asking "does this look beautiful?" They are asking a different set of questions, usually in this order:

Can this person solve a problem? UX is a problem-solving discipline. The work you show needs to demonstrate that you start with understanding a problem rather than jumping to solutions.

Is there evidence of process? Research, user interviews, synthesis, iteration — these are the things that separate UX design from visual design. If your portfolio shows only final, polished screens, it looks like you skipped the work that matters most.

Can they communicate their thinking? A huge part of working in UX is explaining decisions to stakeholders, developers, and product managers. Your portfolio is the first test of whether you can do that clearly.

Have they worked on something real? Not necessarily a paid job — but a project with real constraints, real users, and decisions that were genuinely hard to make. The difference between a real project and a contrived exercise tends to be obvious to anyone who has hired before.

The anatomy of a strong UX case study

A case study is not a design showcase. It is a documented piece of thinking. Here is what a strong one contains:

Context

Set up the brief. What was the problem, who were the users, what were the constraints? This section should be short but specific. "I redesigned an app" is not context. "The existing checkout flow had a 68% drop-off rate on mobile, and the business needed to understand why before committing to a rebuild" is context.

Research

What did you actually find out, and how? Walk through the methods you used — user interviews, usability testing, desk research, analytics review — and give the reader a sense of what surprised you. Research that is just listed ("I conducted five user interviews") is weaker than research that shows what you learned from it.

Synthesis

This is the step most portfolios skip. What were the key insights that came out of your research? How did those insights shape the direction you took? If you can show the link between "this is what users told us" and "this is the design decision we made as a result", your case study will be in the top tier.

Design process

Show the thinking, not just the output. Wireframes, early prototypes, iterations, ideas that were tried and rejected — all of this is valuable. A single polished final screen tells a hiring manager nothing about how you got there. Three rough wireframes that show your reasoning tell them a lot.

Do not be afraid to include things that did not work. Showing that you tested an idea, found it failed, and changed direction is evidence of exactly the kind of iterative thinking that companies want.

Outcome

What was tested? What changed as a result? What would you do differently with more time or resource? If you have metrics, use them. If you do not, describe what qualitative evidence you have that the design moved in the right direction.

Length and format

A case study should be scannable in five minutes. Use clear headings, keep your paragraphs short, and make sure every section earns its place. Long does not mean thorough. A case study that buries the interesting parts in dense paragraphs will lose readers quickly.

Common portfolio mistakes (and how to avoid them)

These come up constantly in portfolio reviews. If you recognise any of them in your own work, that is useful information.

Only showing final screens. A portfolio full of beautiful mockups with no process looks like a visual design portfolio, not a UX one. Show the messy middle.

Describing what you did rather than why. "I created wireframes, then prototypes, then conducted usability tests" describes a sequence of activities. What hiring managers want to know is why you made the specific decisions you made, and what evidence you had for them.

Fake redesigns of well-known apps. This is the most common mistake in early-career portfolios. "I redesigned the Spotify playlist experience" as a self-initiated project with no real users, no real constraints, and no real brief is not evidence of UX skill. It shows you can copy existing patterns with a different visual treatment. If you are going to redesign a product you know well, treat it as a proper brief: recruit real users, conduct actual research, document decisions honestly.

Too many projects. Eight case studies, each half-finished, is much weaker than three that are properly developed. Two excellent case studies will get you further than eight mediocre ones.

No real users anywhere. Portfolios that show design artefacts but no evidence of talking to actual humans raise a red flag. Even a small round of interviews or a handful of usability testing sessions signals that you understand UX is not just about design decisions in isolation.

A portfolio site that is harder to use than the projects it showcases. The irony of a difficult-to-navigate UX portfolio is not lost on hiring managers. Keep navigation simple. Make it easy to find each case study. Do not bury the work.

Portfolio formats that work

The platform you use matters far less than the clarity of the work inside it. That said, here are the formats that tend to work well:

Notion portfolios. Fast to build, easy to update, and perfectly functional for early-career candidates. Notion has become a genuinely accepted format — do not let anyone tell you it is not "professional enough".

Dedicated portfolio sites. Webflow, Squarespace, and Adobe Portfolio are all solid options if you want more visual control. Webflow in particular can itself become a portfolio piece if you build it well.

PDF case studies. Useful for direct outreach, where you are sending your work to a specific person rather than waiting for them to find you. A well-formatted PDF case study sent directly to a hiring manager cuts through in a way that a portfolio link sometimes does not.

Whatever format you choose, prioritise loading speed, legibility on mobile, and navigation that does not require explanation. If someone has to figure out how to read your portfolio, you have already lost them.

What "no experience" actually means

Most people entering UX feel that the phrase "we want someone with experience" closes a door before it has opened. It is worth being precise about what experience actually means in this context.

A portfolio does not need paid work. It needs evidence of UX thinking applied to a real problem with real users. There are several routes to that:

Personal projects. Pick a product you genuinely use and find frustrating. Treat it as a real brief: define the problem, recruit users from your network, conduct interviews, run usability tests, iterate on your designs. The product does not need to be obscure. The research and process are what matter.

Volunteer work. Local charities, small start-ups, and non-profit organisations often have real UX problems and very little design resource. Offering to do user research or redesign a key flow in exchange for portfolio permission is a genuine exchange of value, and it gives you real constraints and real users.

Course projects with real clients. This is where the quality of the course matters significantly. A course that gives you a fictional brief is not the same as one that puts you in front of an actual client with an actual problem. The latter produces portfolio work that stands on its own.

UX Academy graduate portfolio examples

Students at UX Academy work on real client projects throughout the course. That means actual companies, actual users, and actual problems — not fictional briefs designed to be safely solvable.

Past client projects have included Avasa, HopStair, and Welfound, among others. Students conduct their own user research, present findings to real stakeholders, and iterate based on feedback from people who actually care about the outcome. That process produces case studies that are meaningfully different from self-initiated redesigns, because the constraints were real and the decisions were genuinely hard.

You can see examples of graduate work at myuxacademy.com/student-work/.

For more guidance on what reviewers look for, our UX portfolio review checklist walks through the criteria systematically, and the UX design portfolio guide covers the full process of building one from scratch.

The practical summary

If you are at the research stage and trying to understand what makes a UX portfolio good, here is the short version:

Show your process, not just your output
Explain why, not just what
Include real users in every project
Two or three strong case studies beats eight weak ones
The platform does not matter; the clarity of the thinking does
"No experience" is not a blocker if you treat early projects like real work

The difference between a portfolio that gets ignored and one that gets an interview is almost always process documentation, not visual polish.

Build a portfolio with a real client brief

If you want to build portfolio work that looks like the examples above, the Beginner UX Design and UX Career Track courses at UX Academy are built around exactly that.

You will work on a real client project, conduct real user research, and receive feedback from instructors who have hired UX designers at Adobe, Google, and Canva. The brief is not invented for the course — it is a genuine company with a genuine problem, and the work you produce is yours to take into your portfolio.

The next cohort starts 5 September 2026. Find out more about the courses or see what previous students have built.