What a UX designer
portfolio should show.
A UX designer portfolio should be built around three to five deep case studies, not a gallery of pretty screens. Each case study carries the full arc: the problem and its constraints, the research you ran, how you framed the problem, the design decisions and the iterations you rejected, and the measured outcome, whether that is task success, conversion, retention, or fewer support tickets. Show the artifacts that prove the process, flows, wireframes, and prototypes, and state exactly what you did on a team project versus what a colleague did. Below is the full list of what to put in, the terms a design hiring manager searches, and which of the Portfolio designs suit a case-study-led site.
The sections a UX portfolio needs.
A UX designer is hired on evidence of thinking, not decoration. The portfolio is organised around case studies that show how you reason from a problem to a measured result. Work through these in order, and read the flagged block twice.
Three to five deep case studies
Not ten thin ones. Pick your strongest projects and give each the room to breathe. A reviewer would rather read three cases that show real depth than click through a dozen that stop at the final screen. Lead with the one closest to the role you want.
The problem and the constraints
Open each case with the actual problem, the business goal behind it, and the constraints you worked inside, the timeline, the platform, the tech limits, the users you could and could not reach. A design decision only reads as smart once the reader knows what boxed it in.
The research you ran
Show the discovery work: user interviews, usability testing, survey or analytics data, a heuristic evaluation, a competitive teardown. Say how many people you talked to, what you asked, and the one or two findings that changed the direction. This is the section junior portfolios most often skip and hiring managers most want to see.
How you framed it and iterated
Walk from insight to a framed problem statement, then to the flows and wireframes, then to the prototype. Include the versions you rejected and why. A before and after with a line on what the change fixed is worth more than a polished final comp on its own.
The measured outcome
Close every case with what changed. Task success rate, conversion, activation, retention, drop in support tickets, time on task, or a usability score. If a number is under wraps, describe the direction and the size honestly. A case with no result reads as a mockup, not a project.
Your role and your tools
On any team project, state plainly what you owned and what you did not: research, IA, interaction design, prototyping, the design system, the hand-off to engineering. Name the tools, Figma, prototyping, a Sketch legacy file, the design system you contributed to. Ambiguity about your role is the fastest way to lose a reviewer's trust.
Never include: pretty screens with no context, or confidential work
Do not publish a wall of Dribbble shots or final UI with no problem, no process, and no result. A reviewer reads that as decoration and moves on. Every image needs a reason it exists and a sentence on what it shows.
Respect your NDAs. Do not expose unreleased client work, internal roadmaps, or real user data pulled from research, names, emails, faces, or raw interview recordings. If a project is confidential, put it behind a password-protected case study and share the link on request. That is the honest fix, and reviewers respect it.
Terms a design hiring manager searches.
Design roles still route through an applicant tracking system, and a recruiter searches it for specific skills. If these are true of your work, use the exact words, because a system indexes the words you wrote, not the ones you meant. Tailor the list to each posting.
Paste your resume into the free ATS score checker with a real UX job posting to see which of these terms the posting uses and your resume is missing.
Which designs suit a case-study site.
A UX portfolio lives or dies on narrative, so the site has to carry long-form text and images in sequence, not just a grid of thumbnails. Of the 60 Portfolio designs and 48 resume layouts, these are the shapes that fit.
Pick a design that gives each project its own page with room for a running narrative and images placed in reading order. Avoid the pure gallery grids built for visual portfolios, they front the images and give your process nowhere to go.
Of the 48 resume layouts, choose a single-column one over a two-column design. Multi-column resumes can serialise into a scrambled reading order when an applicant tracking system parses them, which is the last thing you want on a screened application.
Order each case study so the problem comes first, the research and iterations sit in the middle, and the measured result closes it. A reviewer scans for that arc, so make the shape obvious before they read a word.
Use restrained type and generous spacing so the flows, wireframes, and prototypes read clearly. Your judgement is the product here; a loud template competes with it instead of framing it.
Who a UX portfolio is not for.
A portfolio is the price of entry for most UX roles, but not every situation calls for a full custom site. Read this before you spend a week building one.
Worth building if you
- +Are applying for product design, UX, or interaction design roles, where a case-study portfolio is expected and often required to get an interview.
- +Have shipped work with an outcome you can point to, or research and iterations you can walk a reviewer through end to end.
- +Are moving from a related field, research, visual design, or front-end, and need to show you can reason through a UX problem.
- +Want one link that shows your thinking, so a recruiter can vet you before a call instead of guessing from a resume.
Skip it, for now, if you
- −Have nothing you can show without breaking an NDA, and no time to build a self-directed or redesign case study to stand in for it.
- −Are only applying to roles that never open an external link, though these are rare in design.
- −Would fill the site with final screens and no process. A thin portfolio can hurt more than no portfolio.
- −Have a deadline this week. Fix the resume for the ATS first, then build one strong case study, then add the rest.
Questions UX designers ask.
Straight answers on depth, NDAs, process, and building a portfolio with little shipped work.
How many case studies should a UX portfolio have?
Three to five. Below three you look thin, above five most reviewers stop reading and the weaker cases drag down the strong ones. Choose your best work, put the case closest to the target role first, and give each one enough room to show the full arc from problem to outcome.
What if my best work is under NDA?
Do not publish it in the open. Put the case study behind a password and share the link on request, or describe the work at a level that reveals no unreleased feature, internal metric, or real user data. Recruiters see confidential work often and respect a designer who protects it. A self-directed project or a public-product redesign can also stand in.
Do I need to show process, or just the final outcome?
Both, and the process is what separates a UX portfolio from a visual one. A reviewer hires the thinking, so show the research, the framing, and the iterations you rejected, then close with the measured result. Final screens alone read as decoration. Outcomes alone read as a claim with no working shown.
I am a junior designer with no shipped work. What do I put in?
Build case studies you can control: a redesign of a real product with a documented problem and usability test, a self-directed concept, a bootcamp or coursework project taken deeper than the brief, or volunteer and freelance work. Run real research even if the sample is small. What matters is that the thinking is genuine and the process is visible.
Should my portfolio be research-heavy or visual?
Match it to the role. A product design role wants to see interaction design and polish alongside the reasoning; a UX or research-leaning role wants the discovery and testing front and centre. Read the posting, then lead with the case study that shows the strength that job is buying.
How long should a single case study be?
Long enough to show the arc and no longer. Most strong cases run a scroll of five to eight sections: problem, research, framing, design and iterations, outcome, and your role. Write tight, caption every artifact, and let a reviewer skim the headings and still follow the story.
Where to go next.
Build the site, test your resume, or read how the paste-a-resume flow works.
Turn your UX
resume into a site.
Paste your resume and Portfolio drafts a case-study-led website in about a minute. Room for the problem, the research, the iterations, and the outcome, published to your own domain with TLS handled for you.