How to Build a UX Portfolio That Gets You Hired

A UX portfolio isn't a gallery of screens. It's a hiring document. Its job is to make a busy reviewer — usually skimming on a phone between meetings — confident that you can think through ambiguity, partner across a team, and ship work that moves something forward.

After reviewing hundreds of portfolios with coaching clients, a few patterns hold up. The ones that get interviews share the same handful of moves. The ones that don't usually fail in the same places.

What hiring managers are actually scanning for

• Can you frame a problem? Not just describe one — frame it in a way that explains why it was worth solving.
• Can you make decisions under constraints? Show the tradeoffs you faced, not just the path you picked.
• Did your work change anything? Outcomes don't have to be a 38% lift. "We killed the feature" or "the team aligned on a new direction" both count.
• Can you communicate? If your case study is hard to scan, your design reviews will be too.

The case study structure that wins

Hook (1 screen)

Name of the project, your role, your team, the timeframe, and a one-sentence outcome. This is the only part most reviewers will read in detail before deciding whether to keep going. Make it count.

Context and problem (1–2 screens)

What was happening at the company, what was at stake, and why this work landed on your desk. Resist the urge to start with "the user." Start with the business situation, then narrow into the user need.

Your approach and key decisions (3–5 screens)

This is the bulk of the case study and where most portfolios go sideways. Don't walk through every artifact you produced. Pick two or three decisions that meaningfully shaped the work, and explain what options you considered, what you chose, and why. Decisions are more interesting than deliverables.

Outcome and reflection (1 screen)

What shipped, what you learned, and what you'd do differently. The reflection paragraph is one of the highest-signal parts of a portfolio — it tells the reviewer how you grow.

The mistakes that quietly kill portfolios

• Burying your role. If a reviewer can't tell what you specifically did within the first 30 seconds, they'll assume the team did the impressive parts.
• Process theater. Long sections on "I followed the double diamond" with no actual decisions in them.
• No numbers and no story. You need at least one of the two. Both is better, but a clear narrative beats vague metrics.
• Walls of text. The reviewer is skimming. Use headings, short paragraphs, and visual breaks.
• Missing context for early-career work. Bootcamp projects can absolutely land interviews — but only if you frame them with the same rigor as real work.

How many case studies do you actually need?

Three strong case studies will outperform six mediocre ones every time. Pick projects that show range — ideally one research-heavy, one design-heavy, and one cross-functional or ambiguous. Cut everything else, or move it to a brief "other work" appendix.

When to get outside eyes on it

If you're getting portfolio reviews but not interviews, the problem is usually in the first screen of each case study — not the deeper details. A portfolio review with a coach who's been on the hiring side can pinpoint the exact spots where reviewers drop off and what to change.