The Short Answer
A UX portfolio isn’t a gallery of pretty screens. It’s a collection of case studies that tell a story: here’s a problem, here’s how I solved it, and here’s the impact.
Recruiting managers spend an average of 2-3 minutes scanning a portfolio. Your goal isn’t to show everything you’ve ever done. It’s to show that you think like a UX designer.
Here’s how to build one that gets you hired.
What a UX Portfolio Actually Needs
Forget the perfectionism. A hiring-quality portfolio needs exactly three things:
1. A Strong Introduction
Your name, what you do, and one sentence that captures your design philosophy.
Examples:
- “I design products that make complex data simple and accessible.”
- “UX designer focused on creating inclusive experiences for underserved audiences.”
- “I turn ambiguous problems into clear, user-centered solutions.”
No fluff. No “passionate ninja rockstar” energy. Just clarity.
2. Three to Five Case Studies
Each one should follow a consistent structure (more on that below).
3. An About Page
Your background, your perspective, what you’re looking for. Make it human.
That’s it. Three things. Everything else is decoration.
What Hiring Managers Actually Look For
Here’s what separates a portfolio that gets interviews from one that gets ignored:
They Want to See Your Thinking, Not Just Your Screens
The mistake most portfolios make: they show final designs without showing how they got there.
Bad case study: “Here’s what I designed. Isn’t it beautiful?”
Good case study: “Here’s the problem, here’s what I learned from users, here’s what I tried, here’s what worked, here’s what I’d do differently.”
The Red Flags That Get Portfolios Rejected
- No process — Pretty screens with no research, no wireframes, no rationale
- No constraints — “I designed an entire app from scratch” with no real-world limitations
- No metrics — No way to measure whether the design actually helped
- No reflection — No discussion of trade-offs, failures, or what was learned
- No storytelling — Just a gallery with no narrative thread
The Case Study Structure That Works
Each case study should follow this structure. It’s proven. It works.
1. The Hook (2-3 paragraphs)
Start with the problem and why it matters.
Template:
“[Company] was struggling with [problem]. [Number]% of users [negative outcome]. The challenge was to [goal] while [constraint].”
2. Your Role (1 paragraph)
Be specific about what you did.
Template:
“As the sole UX designer on this project, I was responsible for [list 3-4 key responsibilities]. I worked with [stakeholders] over [timeline].”
3. The Research (2-3 sections)
This is where most portfolios fail. Show your work.
- User interviews — Quotes, findings, pain points
- Competitive analysis — What others do well, where they fall short
- Data insights — Analytics, surveys, behavioral observations
- Synthesis — What patterns emerged? What surprised you?
4. The Process (3-4 sections)
Show how you moved from research to design:
- Problem framing — How you defined the challenge
- Ideation — Sketches, wireframes, decisions you debated
- Prototyping — What you built and why
- Testing — What you learned from users
Include screenshots of your sketches, whiteboard sessions, and rough drafts. This proves you actually did the work.
5. The Outcome (2-3 sections)
What happened? What did you learn?
- Design decisions — Why you chose what you did
- Results — Metrics, user feedback, business impact
- What I’d do differently — Shows maturity and self-awareness
Choosing Projects That Get You Hired
Not all projects are equal. Here’s what to include and what to skip.
Include Projects That Show…
Diversity of skills:
- One research-heavy project
- One interaction design project
- One visual design project
- One project with measurable impact
Diversity of formats:
- Mobile app
- Web application
- Design system or component library
- Service design or physical-digital hybrid
Diversity of users:
- B2B (business)
- B2C (consumer)
- Accessibility-focused
- International or multilingual
Skip Projects That…
- Are purely visual with no research component
- Are theoretical exercises with no user validation
- Don’t show your decision-making process
- Are too similar to each other
The Spec Project Question
Should I do a speculative redesign?
Yes, but only if:
- You do actual user research (not just your opinion)
- You validate your designs with real users
- You frame it as “exploring improvements to [X]” not “[X] is terrible, here’s my fix”
Redesigns of existing products carry baggage — users already have habits and expectations. Approach with respect for the existing experience.
Making Your Portfolio Itself a UX Case Study
Your portfolio website is your first UX project. If it’s confusing, slow, or broken, it undermines every case study.
Portfolio Must-Haves
- Fast loading — Under 3 seconds. Every extra second hurts your credibility
- Clear navigation — Home, Case Studies, About, Contact. Nothing more
- Readable typography — No decorative fonts. Readability over aesthetics
- Mobile responsive — Many hiring managers will view on their phone
- Consistent design system — Your portfolio should demonstrate strong visual design skills
What to Avoid
- Splash pages — Nobody wants to click through an intro animation
- Full-screen carousels — Users skip them. Don’t waste the top fold
- Excessive animations — They slow down your site and distract from content
- Hidden contact info — Make it easy to reach you
- Stock photos — They make your portfolio feel generic
Writing Case Studies That Stand Out
The writing is as important as the designs. Here’s how to make your case studies compelling:
Use the STAR Method
- Situation — What was the context?
- Task — What were you asked to solve?
- Action — What did you do and why?
- Result — What happened and what did you learn?
Write for Skimmers
Hiring managers don’t read every word. They scan.
Do this:
- Use clear headings and subheadings
- Bold key insights
- Use bullet points for lists
- Keep paragraphs to 3-4 lines
- Put the most important info first
Don’t do this:
- Walls of text
- Jargon without explanation
- Overly academic writing
- Starting with your education instead of the problem
Show, Don’t Just Tell
Every section of text should be accompanied by relevant visuals:
- Research → Screenshots of interview notes, personas, journey maps
- Process → Wireframes, sketches, flow diagrams
- Design → High-fidelity screens, prototypes
- Results → Metrics, user quotes, before/after comparisons
Be Honest About Failures
Nothing shows maturity like admitting what didn’t work.
Example:
“Our first prototype failed with 4 out of 5 users. The navigation structure confused them. We went back, reorganized the information architecture, and retested. The second version had 80% task completion.”
This shows:
- You test early
- You iterate based on feedback
- You’re not afraid to kill your darlings
Portfolio Platforms: Where to Build It
You have options. Each has pros and cons.
Website Builders (Recommended)
Webflow
- Pros: Design freedom, no code needed, fast hosting
- Cons: Learning curve, paid ($14/month)
Framer
- Pros: Fast, beautiful templates, great for designers
- Cons: Less flexible than Webflow for complex sites
Framer/Figma
- Pros: Great if you’re already in Figma, fast to publish
- Cons: Limited customization
Developer Platforms
GitHub Pages + Hugo
- Pros: Free, great for showing technical skills
- Cons: Requires HTML/CSS knowledge
Next.js / Astro
- Pros: Full control, impressive technical skills
- Cons: Time investment, hosting costs
Template-Based
Notion
- Pros: Fast to set up, easy to update
- Cons: Looks generic, limited design control
Wix / Squarespace
- Pros: Easy, all-in-one
- Cons: Template limitations, not UX-first
My Recommendation
Start with Webflow or Framer. They give you the most design freedom without requiring code. Your portfolio is your brand — don’t compromise on the experience.
Getting Your Portfolio Reviewed
Before you publish, get feedback from people who matter:
Who to Ask
- Other UX designers — They’ll critique your process
- Hiring managers — They’ll tell you what they’re looking for
- Recruiters — They’ll tell you how quickly they can find what they need
- People outside UX — They’ll tell you if your writing is clear
Where to Get Feedback
- ADPList — Free mentorship and portfolio reviews from experienced designers
- Twitter/X — Post snippets and ask for feedback
- LinkedIn — Share case studies and ask for comments
- Local UX meetups — In-person reviews are gold
The 2-Minute Test
Ask someone to look at your portfolio for 2 minutes and then answer:
- What do I do?
- What kind of projects have I worked on?
- What’s my design approach?
- How would I feel about hiring me?
If they can’t answer these quickly, your portfolio needs work.
Common Portfolio Mistakes (And How to Fix Them)
❌ “I’m not a real designer yet”
Fix: You don’t need to be. Your portfolio shows what you can do. Every expert was once a beginner.
❌ “My portfolio isn’t perfect”
Fix: It will never be. Ship it. You’ll iterate. A published portfolio with room to grow beats a “perfect” one that exists only in your head.
❌ “I need a logo for my portfolio”
Fix: No. Your name is your brand. Focus on your work, not your logo.
❌ “I should include everything I’ve ever made”
Fix: Curate ruthlessly. Three strong case studies > ten mediocre ones.
❌ “I need a video intro”
Fix: Nobody watches it. Put your introduction in text. Let hiring managers scroll at their own pace.
The Portfolio That Gets You Hired: A Checklist
Before you share your portfolio, verify:
- Homepage is clear and takes under 5 seconds to understand
- 3-5 case studies with clear structure
- Each case study shows research, process, and outcome
- Real user quotes and data included
- Before/after comparisons where possible
- About page with your story and perspective
- Contact information is easy to find
- Loads in under 3 seconds
- Mobile-responsive
- No typos or broken links
- Tested with 3+ people who gave honest feedback
Final Thought
Your portfolio isn’t a museum of your best work. It’s a conversation starter. It’s proof that you can think through problems, understand people, and create solutions that work.
The best portfolios aren’t the prettiest. They’re the ones that make a hiring manager lean back, close the tab, and think: “I need to talk to this person.”
That’s the goal. Build toward that.