How to build a UX portfolio
that gets you hired

A UX portfolio is a small set of case studies showing how you solve problems. Each case study is evidence for one claim about you: that you can do research that changes decisions, design clear flows, work with engineers under constraints, or improve a metric. Together, the case studies show range and depth.

Reviewers skim. Nielsen Norman Group asked more than 200 UX hiring managers what they look for in portfolios and found that expectations differ for designers and researchers, and for junior and senior roles,¹ so tailor what you show. Its research on reading behaviour shows people scan headings and first words rather than reading everything.² So case studies need summaries, headings and visuals that carry the story. The reward is real: AmbitionBox lists UX designers in India at a typical ₹12.6–13.9 lakh³ and junior UX designers at ₹5–5.8 lakh,⁴ while the US Bureau of Labor Statistics puts web and digital interface designers' median pay at $104,000.⁵

Case studies in a typical strong portfolio

2–4

How reviewers read case studies (NN/g)

Scan

Typical UX designer pay in India (AmbitionBox)

₹12.6–13.9 lakh

US median, web and digital interface designers (BLS, 2025)

$104,000

Table: How UX portfolios are assessed (editorial summary)

Table: A skimmable case study structure (editorial guidance)

Table: How UX portfolios have changed (editorial summary)

• Two to four case studies with summaries
• Your role stated clearly in each
• At least one project with research evidence
• At least one outcome (metric or qualitative)
• A 30-minute presentation version
• A score on the free UX Portfolio Assessment

Your CV should point to the portfolio and highlight the same results. Keep project names consistent so reviewers can connect them. Put the portfolio link at the top of the CV.

"Walk me through this project."

Summary first, then problem, your role, key decisions, outcome and reflection.

"What was your specific contribution?"

Name your work clearly and credit others honestly.

"What would you do differently?"

A genuine reflection — a research gap, a scope decision or a missed edge case.

"Why did you choose this project for your portfolio?"

It shows a specific strength relevant to the role.

"How did you measure success?"

The metric or evidence, how you got it, and its limits.

• "Which case study was most relevant to this role, and why?" — reveals what they value.
• "What do strong portfolios here have in common?" — useful feedback.
• "How are designers' outcomes measured?" — success criteria.
• "Would you like a deeper walkthrough of any project?" — shows openness.

Table: Portfolio expectations by role and typical pay in India (AmbitionBox, October 2026; indicative)

Table: Tools for building a UX portfolio (editorial guidance)

• Student / switcher — self-initiated projects.
• Junior designer — first real projects.
• Designer — outcome-led case studies.
• Senior designer — strategic and leadership stories.
• Lead — team-level impact and mentoring.

1. Week 1: Choose — Pick two to four projects that show different strengths.
2. Week 2: Write — Summaries, decisions, outcomes.
3. Week 3: Design and review — Build pages; get feedback from two designers.
4. Week 4: Present and check — Rehearse a walkthrough; take the UX Portfolio Assessment.

Related: UX Designer Interview Test and UX/UI Design Fundamentals. Guides: UX designer interview, UX portfolio examples and UX case study.

Portfolio skills are communication skills you use daily:

• Presenting — sharing work with stakeholders.
• Writing — clear design rationale.
• Documenting — decisions and outcomes.
• Reflecting — learning from projects.
• Measuring — tracking results.
• Storytelling — making the case for design.

"Why are there only three projects?"

"I chose depth over breadth — each shows a different strength. Happy to discuss others."

"Which project are you least proud of?"

Choose a real one, explain what went wrong and what you learned.

Table: A plan to keep your portfolio current (editorial guidance)

The best time to build your next case study is while you're doing the work. Keep a short log of problems, decisions, alternatives and results as you go. Save before-and-after screens and any metrics you're allowed to share. Drafting a case study every few months keeps your portfolio ready for opportunities without a rushed rewrite.

The summary at the top is the most important part of each case study, because many reviewers will read nothing else. Write it last, once you know the full story, and keep it to three or four lines.

A reliable formula is: context + problem + your role + key decision + outcome. For example: "A fashion marketplace was losing money on support for returns. I led design for a new self-serve returns flow, working with a PM and three engineers. We replaced a five-step form with a guided two-step flow based on usability testing. After launch, return-related support tickets fell and completion improved."

Add a few scannable facts beside it: timeline, team, platform and your responsibilities. If outcomes are confidential, describe them qualitatively and honestly: "Leadership approved the rollout to all markets based on pilot results." Avoid jargon and buzzwords. A clear, credible summary invites the reader into the rest of the story.

AI makes it easy to generate polished mockups and even whole case study write-ups, so hiring managers have become more sceptical of slick visuals. What stands out now is evidence of real thinking. That means research with actual users, decisions you can defend in conversation, and outcomes you can explain in detail.

Be transparent about how you used AI in your projects. If you used it to synthesise research notes, generate design variations or draft copy, say so and explain how you checked and refined the results. Many teams see thoughtful AI use as a strength. Avoid AI-written case study text that sounds generic. Interviewers will ask follow-up questions, and your answers need to match what's on the page. Authentic, specific stories are now the strongest differentiator.

• Too many shallow projects.
• Screens without context or decisions.
• Unclear role in team projects.
• Invented or inflated metrics.
• Slow, hard-to-navigate sites.

Portfolio guidance and reading behaviour come from Nielsen Norman Group; India pay from AmbitionBox (read October 2026); and US pay from the Bureau of Labor Statistics. Case study structures, assessment stages and history are editorial. Science of Apps publishes the free assessment linked here. Last reviewed October 2026.

• Case study — a story of how you solved a design problem.
• Outcome — the result of your work, measured or observed.
• NDA — a non-disclosure agreement limiting what you can share.
• Self-initiated project — work you chose and did independently.
• Portfolio walkthrough — presenting case studies in an interview.