What hiring managers look for
A UX portfolio is not a gallery of pretty screens. Hiring managers evaluate: Problem framing: Can you articulate the problem clearly before jumping to solutions? Process: Did you follow a systematic approach, or did you skip straight to mockups? Decision-making: Can you explain why you chose one direction over others? Impact: Did your design actually improve something measurable? Collaboration: How did you work with engineers, PMs, researchers, and stakeholders? Communication: Can you tell a clear, engaging story about your work? A portfolio with four well-told case studies beats one with twelve screenshot galleries.
The portfolio is also a design artifact — it demonstrates your skills by being well-designed itself. If your portfolio has poor information architecture, inconsistent typography, broken responsive behavior, or confusing navigation, you're demonstrating exactly the kind of work the hiring manager should expect from you. The portfolio is simultaneously the content and the proof.
Portfolio structure
Portfolio Architecture Core Method
Use when: structuring your portfolio site or document.
A portfolio needs three elements: Landing page: Your name, title ("Product Designer" or "UX Designer" — be specific), a one-line positioning statement ("I design enterprise B2B tools" or "I make complex financial products simple"), and 3–5 case study previews with thumbnails. The landing page should communicate who you are and what kind of work you do within 5 seconds. Case studies: The core of your portfolio. 3–5 detailed case studies that show range (different project types, different stages of the design process, different outcomes). About page: Brief bio, your design philosophy (2 sentences), skills/tools, and contact information. Don't over-design this page — it's reference material, not the main event.
Writing a case study
Case Study Framework (STAR) Core Method
Use when: writing any portfolio case study.
Follow the STAR structure: Situation: What was the context? The company, the product, the team, the timeline, your role. Set the stage so the reader understands the constraints. Task: What was the specific design challenge? What were the goals? What metrics needed to move? Make the problem feel real and urgent. Action: What did you do? Walk through your process — research, ideation, design decisions, testing, iteration. This is the bulk of the case study. Show your thinking, not just your output. Result: What happened? Quantitative results (conversion increased 23%), qualitative results (users rated the new flow 4.5/5), and organizational impact (the project was expanded to three more product lines). If you can't share specific numbers, describe the direction and magnitude.
Impact Statement Writing Technique
Use when: summarizing the result of a design project.
Impact statements should be specific and attributable: Weak: "The redesign improved the user experience." Better: "The redesigned checkout flow reduced cart abandonment by 18%." Best: "The redesigned checkout flow reduced cart abandonment by 18%, contributing to an estimated $1.2M additional annual revenue." If exact numbers are NDA-protected, use ranges or relative improvements: "Task completion time improved by more than 40%." If the project was never launched, frame the impact as validated potential: "Usability testing showed 90% task success rate, up from 55% with the existing design."
Show the messy middle
The most compelling case studies show the process — including the parts that didn't work. Sketches that were rejected, usability test findings that forced a pivot, stakeholder feedback that changed the direction. This demonstrates something more valuable than perfect outcomes: the ability to iterate, handle ambiguity, and improve through feedback. A case study where everything went perfectly is either dishonest or boring.
Showing process, not just outcomes
Process Documentation Technique
Use when: deciding what process artifacts to include in case studies.
Include artifacts that demonstrate thinking: Research artifacts: Interview quotes, affinity diagrams, persona snapshots, journey maps. Show that your designs are grounded in real user needs. Ideation artifacts: Sketches, whiteboard photos, Crazy Eights output, design studio results. Show that you explored alternatives. Decision artifacts: Comparison matrices, trade-off analyses, stakeholder feedback notes. Show that you made informed choices. Testing artifacts: Usability test highlights, before/after comparisons, iteration history. Show that you validated and improved. Don't include every artifact from every project — curate. Show the 3–4 artifacts that most clearly demonstrate your thinking process.
Portfolios for different roles
Role-Specific Portfolio Focus Framework
Use when: tailoring your portfolio to a specific role type.
Product designer: End-to-end case studies showing research → design → validation. Emphasize strategic thinking, cross-functional collaboration, and measurable outcomes. UX designer: Focus on interaction design, information architecture, and user flows. Show detailed wireframes, flow diagrams, and usability testing iterations. Visual/UI designer: Show craft. Design systems, typography decisions, color theory application, micro-interactions, responsive implementations. High-fidelity work should be stunning. UX researcher: Focus on methodology, analysis, and impact. Show research plans, synthesis frameworks, and how findings changed product direction. Less visual design, more analytical rigor. Generalist (startups): Show range. Include projects where you did research, design, prototyping, and testing yourself — demonstrating you can handle the full spectrum.
Presenting NDA-restricted work
NDA Work Presentation Technique
Use when: your best work is under NDA or confidential.
Strategies for showing restricted work: Abstract the visuals: Replace real UI with wireframes, change colors and branding, use placeholder content. The process and thinking remain; the specifics are obscured. Focus on process: Describe the approach, methods, and thinking without showing the final product. Journey maps, personas, and process photos often aren't NDA-restricted. Ask for permission: Many companies allow portfolio use if you ask — especially for work that has shipped publicly. Get written approval. Create a password-protected section: Some case studies are available only to interviewers who request access. Use personal or side projects: Supplement NDA-restricted work with personal projects, design challenges, or redesign concepts that demonstrate your skills without confidentiality issues.
Templates and checklists
- The landing page communicates who you are and what you do in 5 seconds
- You have 3–5 case studies that show range (different types of projects)
- Each case study follows a clear narrative structure (problem → process → outcome)
- Quantitative or qualitative impact is stated for each project
- Process artifacts are included (not just final screens)
- Your role is clearly stated in each project
- The portfolio itself demonstrates good design (IA, typography, responsiveness)
- It loads quickly and works on mobile
- Contact information is easy to find
- No case study is longer than 5 minutes to read
Real-world examples
Case study
The before/after case study structure
One of the most effective case study patterns: show the existing experience (with its problems clearly annotated), walk through the design process that identified and prioritized solutions, then show the redesigned experience side-by-side with the original. The visual contrast makes the improvement tangible and the impact self-evident. This structure works especially well for redesign projects where the improvement is visible: cleaner information hierarchy, simplified workflows, reduced steps in a flow.
Why it works: Before/after creates an immediate visual argument that's more persuasive than written descriptions of improvement. The hiring manager can see the quality delta with their own eyes.
Case study
The unsolicited redesign: risks and rewards
Redesigning an existing product (without being hired to) is common in junior portfolios. Done well, it demonstrates initiative and analytical thinking: identify real problems through heuristic evaluation, propose solutions grounded in principles, and acknowledge constraints you might not know about. Done poorly, it looks naive: "I redesigned Spotify's navigation" without understanding why it's designed the way it is. The key: show that you understand the current design's rationale before proposing changes. "Here's what the current design does well, here's where user data suggests friction, and here's my proposal" is respectful. "I fixed Spotify" is arrogant.
The rule: Unsolicited redesigns are best when they identify real problems, acknowledge constraints, and propose thoughtful alternatives — not when they just reskin an existing product.
Common pitfalls
Screenshot galleries without narrative
A page of 20 beautiful screens tells a hiring manager nothing about your thinking process, decision-making, or collaboration skills. They can see you can push pixels — but can you solve problems? Wrap every visual in the story of why it exists and what it achieved.
Too many projects, too little depth
Eight shallow case studies are worse than three deep ones. Depth demonstrates the kind of thinking hiring managers want to see. If you have many projects, feature 3–4 as full case studies and list the rest as a brief project gallery with one-line descriptions.