A UX portfolio case study is the one thing that decides whether you get the interview. Nobody reads a UI/UX design portfolio the way you built it. A recruiter scans it, opens one project, and decides in well under a minute whether your thinking is worth an hour of their time. This guide covers how to structure the site and how to write case studies that survive that scan.
The 30-Second Answer
If you change only five things this week, change these:
- Show 3 to 5 case studies, not twelve. Reviewers judge you on your weakest project, so remove it.
- Say what you decided. Vagueness about who owned which decision is the fastest way to lose a reader’s trust.
- Write section headings that state a finding, not a phase. “Users quit at the address step” beats “Research.”
- Put one measurable outcome in every case study, or say plainly that you never got to measure it.
- Make your contact details reachable in one click from any page.
The rest of this guide is the reasoning behind those five.
Structure Your UI/UX Design Portfolio So the Work Is Findable in 10 Seconds
Four Sections, and Nothing Else
Every extra navigation item is one more decision you are asking a busy stranger to make. Four sections cover it:
- Home. Your name, what you do, and the work. Nothing between the visitor and the projects.
- Work. The case studies. This is the only page that really matters.
- About. Who you are, where you came from, and why you design the way you do.
- Contact. An email address you actually check.
A blog, a resume page, and a services page can all live inside those four. Add them later if you have a reason.
Write a Headline That Says What You Actually Do
“Designer. Thinker. Problem solver.” tells a hiring manager nothing. A specific line does the sorting for them:
- A specialization: “UI/UX designer focused on accessibility in healthcare products.”
- An industry: “Ecommerce checkout and conversion.”
- Availability and location, if you want remote or contract work.
Career switchers often resist this because narrowing feels like closing doors. In practice the opposite happens. A generic headline puts you in a pile of a few hundred identical ones.
Show Three to Five Case Studies and Delete the Rest
This is the hardest instruction to follow and the one that changes outcomes most. Reviewers do not average your projects. They form an impression from the weakest one they happen to open.
- Give each project a thumbnail, a title, and one line saying what problem it solved.
- Keep layout, type, and color consistent across all of them. Inconsistency reads as unfinished.
- Lead with the project closest to the job you want, not the one you enjoyed most.
If you want a structured way to do this with feedback from a working designer, our Portfolio School exists for exactly this problem.
Make the About Page Do Real Work
Career switchers usually apologize on this page. Do not. Your previous career is evidence, not a gap. A nurse moving into health tech, a teacher moving into edtech, and an accountant moving into fintech all arrive with domain knowledge that a design graduate does not have.
Include a short account of how you got here, what you care about in design, one or two testimonials if you have them, and a photo. Skip the list of software logos. Everyone has Figma.
Make It Absurdly Easy to Reach You
A plain email address in the footer of every page, plus links to LinkedIn and wherever else you post work. Contact forms are fine as an addition and a mistake as the only option, because plenty of recruiters will not fill one in.
A UX Portfolio Case Study Is a Story About a Decision
Most weak case studies are not badly designed. They are just a walk through the textbook double diamond with the designer removed from it. Empathize, define, ideate, prototype, test. Nothing in that sequence tells a reader what you personally figured out.
Set the Scene in Four Lines
Before any screenshots, answer four questions in a short block at the top:
- Your role. What you owned, specifically. “I ran the research and designed the checkout flow” is useful. “I collaborated cross functionally” is not.
- The team. Who else was there, and what they did.
- Timeline and constraints. Six weeks with no research budget is a more interesting story than unlimited time.
- The business goal and the user problem, and whether they were in tension.
Then show the final design immediately. Making a reader scroll through six weeks of process to find out what you built is a usability failure inside a usability portfolio.
Write Headings That Carry the Finding
This one change does more than any visual polish. Replace phase labels with what you learned in that phase:
- “Research” becomes “Seven of nine users thought the saved card had already been charged.”
- “Ideation” becomes “We tried a one-page checkout first, and it made the problem worse.”
- “Testing” becomes “The fix worked, but only for returning customers.”
Someone who reads nothing but your headings should come away with the whole story. That is the actual bar, because that is what most reviewers do.
Add wireframes, journey maps, and prototypes where they carry a point. Do not paste in every screen you ever made. Nielsen Norman Group has a useful walkthrough of how to build a portfolio case study if you want a second structure to compare against.
Close With What Changed
End every case study with four things: the final solution, a measurable result, feedback from a client or stakeholder if you have it, and what you would do differently.
If you have no numbers, say so. “This shipped after I left, so I have no post-launch data” is honest and costs you nothing. Inventing a conversion lift costs you the job when someone asks how it was measured.
What AI Changed About Design Portfolios
This article originally went up before generative tools were part of a normal design workflow. Two things have shifted since, and both matter for your portfolio.
First, polished screens are no longer scarce. Anyone can produce a clean dashboard mockup now. Nielsen Norman Group’s State of UX in 2026 puts it directly: available roles increasingly demand breadth and judgment, not just artifacts, and the supply of aspiring UX professionals still outpaces open roles at the junior level. When the artifact is cheap, the decision behind it becomes the only thing worth showing.
Second, reviewers now read every case study with one eye on whether a person or a tool wrote it. Generic process prose that never names who decided what reads as generated, whether or not it was. Specificity is the defense. Real user quotes, real constraints, the thing you got wrong in week three.
Using AI in the work itself is fine, and hiding it is the mistake. If you synthesized research notes with a language model or generated twenty layout variants before choosing one, write that down along with how you checked the output. That is a judgment story, which is the kind hiring managers are short of. Just never generate a project you did not do. For more on where the line sits, see our take on whether AI will replace UI/UX designers.
For context on what the roles pay while you decide how much to invest in this: the U.S. Bureau of Labor Statistics puts the median wage for web and digital interface designers at $98,090 as of May 2024, with the lowest 10% under $47,840 and the highest 10% above $192,180, and projects 7% employment growth from 2024 to 2034.
Six Fixes You Can Make This Afternoon
- Cut your weakest project. You already know which one it is.
- Rewrite every section heading in your best case study to state a finding.
- Add a role line to the top of each project saying what you personally owned.
- Move the final design above the process so it is visible without scrolling.
- Put your email in the footer of every page as plain text.
- Send it to one person who hires designers and ask what confused them. Not friends. Not other students.
Where We Fit, and Where We Don’t
Our Portfolio School starts at $2,100 and runs to $3,200 depending on tier. It is a dedicated portfolio program with weekly one-to-one review from a consistent senior designer, which is unusual. Most bootcamps treat the portfolio as the last two weeks of a longer course. Across graduates of completed cohorts, measured at time to employment, our placement rate is 92.5%.
Here is the honest limit. Portfolio School improves work you already have. If you have never run a project end to end, there is nothing to review yet, and you want the full School of UI/UX Design at $7,080 all in, or at minimum a real project of your own first.
If tuition is the blocker, our on-demand membership is $29/mo on the basic tier and $49/mo on advanced, with one-to-one instructor sessions at $120/hr and $90/hr respectively. It buys you feedback, not a finished portfolio, and that distinction is worth being clear about. Nothing we run is free.
If you would rather compare options first, we keep an honest breakdown of portfolio-focused programs, including ones that are not ours, and a longer argument for why fixing a portfolio alone rarely works.
Frequently Asked Questions
How many case studies should a UX portfolio have?
Three to five. Below three and you look untested. Above five and a reviewer will find the weak one. If a project does not have a decision you can defend in an interview, it does not belong.
What do I put in a portfolio if I have no professional experience?
Self-directed projects work, as long as they are real. Pick a product you personally use and a problem you can actually observe, then recruit five users you do not know. A redesign concept with no research behind it is the most common junior portfolio piece and the least persuasive one.
Should I include a project that failed?
Yes, if you can explain why it failed and what you would change. A project that got killed for reasons outside your control, written up with clear reasoning, often reads better than a success you cannot account for.
Do I need to code my own portfolio site?
No. Nobody is hiring you for your site build. A template you have customized carefully is fine. Spend the time on the writing instead, which is where almost every portfolio actually loses.
Can I use AI to write my case studies?
To tighten your own writing, yes. To produce the content, no. A generated case study reads generic in exactly the places a reviewer looks hardest, and you will not survive the interview questions about decisions you never made.
How long should a case study be?
Long enough to carry the decisions and no longer. Five to eight screens of scroll is typical. Assume the headings get read and the body gets skimmed, and write accordingly.
Start With One Case Study
Do not rebuild everything. Take your strongest project, rewrite its headings so they state findings, add a role line, and put the outcome at the top. Then look at what the other projects lack by comparison.
If you would rather have a working designer tell you what is wrong with yours, book a free clarity call and we will give you a straight answer, including the answer that you do not need us.
