The portfolio is the single most important document in a UX Designer's career. More than your degree, more than certifications, more than years of experience. A US or UK recruiter who gets 200 applications for a junior opening opens 30 portfolios, looks at 15 seriously, and brings 5 in for interviews. Your portfolio is the first impression — often the only one you get. And yet most junior portfolios (and plenty of mid-level ones) are structured poorly, tell the wrong stories, and generate far fewer interviews than they could.
This article is a practical guide to building a UX design portfolio that actually works in 2026 for the US and UK market: what to include, how to structure case studies, which platforms to use, the most common mistakes, and how to avoid them.
What you'll learn:
- What recruiters and design managers really look for in a UX portfolio
- The canonical structure of an effective case study
- How many case studies to include (and how many is too many)
- The best platforms for publishing your portfolio in 2026
- The most common mistakes in junior portfolios
- A reusable case study template you can adapt to your next project
What recruiters actually want to see
Recruiters and design managers at US and UK tech companies — from Silicon Valley scale-ups to London fintech — consistently point to three things they look for in a portfolio.
1. Process, not just the result
"Hero shots" — the beautiful finished screenshots — are maybe 10% of a portfolio's value. The other 90% is telling the story of how you got there: which problem you identified, how you researched it, which decisions you made and why, what you learned along the way.
A portfolio with 10 polished screens and no process behind them is a graphic design portfolio, not a UX one. US and UK UX recruiters spot the difference in 30 seconds and move on.
2. Hard decisions
The best case studies show trade-offs. "I picked A over B because B had these advantages but would have cost us X, while A gave us Y in an acceptable timeframe." A candidate who clearly thought about trade-offs is a candidate who can make complex decisions inside a product team.
A candidate who presents only the winning solution as if it were obvious, with no alternatives considered and rejected, looks less mature to a hiring manager.
3. Metrics and real impact
When possible, the strongest portfolios close case studies with numbers: "task completion went from 62% to 87%", "average time-on-task dropped from 2:40 to 0:55", "support tickets on this flow went down 40%".
Numbers aren't mandatory for your first case studies (often class or personal projects without real data), but wherever they're possible they should be there. This is especially true for mid and senior roles at companies like Google, Meta, Spotify, Monzo, or Revolut, where impact metrics are a basic expectation.
The canonical case study structure
A UX case study in 2026 typically follows this structure:
1. Title + summary (1 paragraph)
A specific title defining the project plus 2–3 sentences of context: who the client was, which problem it solved, what the final result was. This is the part 70% of readers will read before deciding whether to keep going.
2. Problem and context
Who was the user? What was the problem? Why did it matter to solve? What was the business context? This section sets up the "why" of the project.
Common mistake: skipping this section and jumping straight into solutions. Without a clear problem, the solution looks arbitrary.
3. Research
What did you do to understand the problem? User interviews? Data analysis? Competitor analysis? What did you find? What are the 3–5 key insights?
Common mistake: presenting research as a list of activities ("I did 8 interviews") with no conclusions. Insights are the output, not the method.
4. Design decisions
How did you turn insights into concrete decisions? Which alternatives did you evaluate? Why did you choose this direction and not another?
This is the most important section of the case study. It's where you show you can think as a designer, not just execute as a pixel pusher.
5. Result (prototype + final screens)
Finished screens, an interactive prototype (link), any specs. This section is the "hero shot" — beautiful but less important than everything that comes before.
6. Validation / testing
How did you verify your solution worked? Usability testing? A/B tests? Post-launch metrics?
Important: even on class case studies where you didn't really ship, you can run qualitative tests with 3–5 people on a clickable prototype. A case study with no validation feels arbitrary.
7. Learnings
What did you learn? What would you do differently? This is often undervalued but highly appreciated: it shows maturity, self-critique, and the ability to iterate — qualities US and UK hiring managers care about at every level.
How many case studies to include
The honest answer surprises a lot of beginners: 2–3 strong, complete case studies are worth more than 8 mediocre ones.
- Junior (first job): 2–3 case studies
- Mid-level (2–5 years of experience): 3–5 case studies
- Senior (5+ years): 4–6 selected case studies
Recruiters don't read everything. They read the first case study for 5–10 minutes, the second for 3–5, the third for 1–2. Then they decide. If you post 8 mediocre case studies, the recruiter sees the first 3 mediocre ones and stops.
Quality, not quantity. And always put your strongest case study first.
Where to publish your portfolio
In 2026 the most common platforms for US and UK UX designers are three.
1. Personal site on Framer or Webflow
Framer and Webflow let you build sites visually, without code, with full design systems and excellent performance. They're the go-to for UX designers who want full control over how their work is presented.
Pros: maximum control, customization, professional impression — ideal for applications at top-tier US/UK companies.
Cons: take time to build, plus hosting and domain costs (around $10–20/month).
2. Notion
Notion is surprisingly effective as a portfolio platform. A public page with well-structured case studies, images, and links. Zero cost, fastest to publish.
Pros: free, fast, easy to edit.
Cons: limited customization, recognizable "default Notion" look.
Notion is an excellent choice for the first portfolio of a junior who wants to start applying immediately without spending weeks building a site — particularly useful if you're applying to LinkedIn Jobs on the Rise openings with a tight deadline.
3. Behance / Dribbble
Designer portfolio platforms. Historically more oriented toward visual and graphic design, but they accept UX case studies.
Pros: organic traffic, community, easy publishing.
Cons: rigid format, mixed with visual-only work, less room to tell a process story.
They can work as a secondary channel alongside a main site, not as the only platform.
Avoid: Medium as a primary portfolio
Medium is great for articles, not portfolios. No interactive components, no screenshot galleries, and the "post" format dilutes visual impact. If you want to write deep-dive articles, Medium is fine — but the portfolio belongs elsewhere.
The most common mistakes
Five mistakes that make portfolios less effective.
1. Too many screens, too few words
A case study with 40 screens and no explanatory text is confusing. Balance visuals and narrative: every section should have 2–3 screens and 2–3 paragraphs of text.
2. No problem stated
"I redesigned X" is not a problem statement. "Checkout completion at X dropped 15% last quarter, causing an estimated $Y loss" is. The clarity of the problem is half the value of the case study.
3. Only final results, no iterations
Early wireframes, discarded ideas, prototypes that didn't work are part of the story. Showing them makes the process look real. Hiding them makes everything look too perfect to be true.
4. Portfolio too generic
A case study titled "App redesign" is anonymous. A specific title ("Cutting cart abandonment by 30% for a US fashion e-commerce brand") is far more powerful.
5. No About and no contact info
Incredibly common: a portfolio with 4 brilliant case studies but no "about me" section and no clear contact info. The impressed recruiter has no way to reach you. Always include: a short bio, a photo, contact links (at minimum email and LinkedIn), and optionally a downloadable CV.
Case study template
A reusable structure for your next case study:
## [Specific title: what you did + for whom]
**Role:** UX Designer | **Duration:** 8 weeks | **Team:** 1 designer, 2 engineers, 1 PM
### The problem
[2-3 paragraphs setting up what wasn't working and why it mattered]
### What I did to understand
- 5 interviews with target users
- Competitor analysis across 4 similar products
- Review of analytics from the last quarter
**Key insights:**
1. [first insight with supporting evidence]
2. [second insight]
3. [third insight]
### Design decisions
[Section that walks through the 2-3 most important decisions, with alternatives considered and rationale for the final choice]
### The result
[Finished screens + link to an interactive prototype]
### How I validated it
[Usability testing with N participants + metrics collected]
### What I learned
[2-3 paragraphs of honest reflection on the project]
This structure works for class projects, freelance, and company work. Adapt it to your context but keep the sequence intact.
Frequently asked questions
Can I include class or exercise projects?
Yes, absolutely. First portfolios are almost always made of class or personal projects. What matters is documenting them as real projects: problem, research, decisions, testing. The fact that the client is fictional doesn't subtract from the value of your process — US and UK hiring managers know this.
Do I need pixel-perfect screenshots?
Not necessarily. "Perfect mockup" screenshots are more typical of UI design portfolios. A UX case study can include wireframes, sketches, and rough prototypes without issue. Substance matters more than aesthetics — though a Silicon Valley recruiter will notice both.
Can I copy the structure of a famous case study?
Yes — the structure is public and you can learn from the best. What you can't copy is the content: your case study has to talk about your actual work, not someone else's project.
What about projects under NDA?
If you're working for a company with an NDA, ask explicitly for permission before including a project in your portfolio. Some NDAs let you show work with sensitive data (numbers, client names) masked. Others don't. When in doubt, leave it out — US and UK legal teams take this seriously.
Is a portfolio without freelance work a problem?
No, if the projects you have are solid. Most first junior portfolios are made of class or personal projects. The absence of freelance or company work is normal for a first job.
Visual-heavy or text-heavy portfolio?
Balanced. Visual-only portfolios feel shallow; text-only ones are boring. The rule: every section should have both a written explanation and a supporting visual. Text and image work together.
Next steps
The portfolio is a living document: you'll keep improving it for years. To start building or refining yours:
- Study the 12-month roadmap that includes portfolio building as a month-6 milestone
- Read how to become a UX Designer by prior background to understand how to position your experience
- Deepen your grasp of UX analysis, which is what feeds your case studies
In CorsoUX's complete UX Design course you build 3 complete case studies during the program, with senior mentors from US and UK tech companies reviewing each phase and helping you tell them effectively for your portfolio.
