How to Build a Design Portfolio That Gets You to Senior

Most designers build their portfolio the same way they did when they were starting out: pick their best-looking projects, document the process, show the final screens. At junior and mid level, that works reasonably well.

At senior level, it stops working. And a lot of designers don't realise why they're getting screened out.

Here's what's actually different.

What hiring managers are looking for at senior level

At junior level, a hiring manager is trying to answer: can this person make good design work? They want to see craft, process, and potential.

At senior level, the question is different: can this person figure out the right problem to solve and navigate the complexity of getting it done in an organisation? That's a much harder question, and polished Figma screens don't answer it.

Senior hiring managers want to see how you think. What assumptions did you question? What constraints did you push back on? What did you get wrong early and correct? How did you bring other people along?

The work itself matters, but it's almost secondary to the story of how you got there.

Show the messy middle

The most common mistake in senior portfolios is presenting everything as clean and resolved. A neat process diagram, a set of explorations, and then the final screens.

The problem is that this makes you look like a very good executor. You took a brief, ran a process, delivered an outcome. That's fine. But it's not what gets you hired at senior.

What actually signals senior thinking is showing the moments where the problem changed. The insight from research that made you throw out two weeks of work. The stakeholder constraint that forced you to reframe the solution. The edge case you caught in testing that nobody had thought about.

These messy moments are where senior judgment actually lives. Hiding them to make the case study look clean removes the most interesting parts.

Make your decisions legible

For each major decision in a case study, the reader should understand: what were the options, why did you choose this one, and what were you trading off?

You don't need to narrate every micro-decision. But the three or four pivotal moments in a project, where the direction could have gone differently, should be explicit.

"We went with the simpler pattern because the user research showed people were already familiar with it, and adding something novel would have introduced friction we didn't have enough time to validate" is ten times more useful than a before-and-after screenshot.

Decisions tell the reader how you think. Outputs only tell them what you made.

Include cross-functional complexity

One thing that separates senior designers from mid-level ones is the ability to operate in complex, multi-stakeholder environments. If your portfolio doesn't reflect that, a hiring manager at a senior level will wonder whether you've actually done it.

Include one case study where the complexity wasn't the design problem, it was getting three teams to agree, or navigating a pivot mid-project, or doing research in an environment where nobody believed in research. The messy organisational stuff.

This doesn't mean writing a case study about internal politics. It means briefly acknowledging the real constraints of the work and how you handled them. That's what makes a portfolio feel like it was done in the real world rather than a design studio.

Be ruthless about what you include

Senior portfolios shouldn't have five case studies that all look similar. Two or three strong, detailed studies are better than six average ones.

Depth matters more than breadth. A case study where a reader genuinely understands how you think is worth more than three surface-level project summaries. If you can only go deep on two things, go deep on two things.

Also cut anything old that doesn't represent how you work now. A mid-career portfolio with your first-year work in it raises questions, not opportunities.

Your portfolio is a conversation starter, not a complete record

The goal of a senior portfolio isn't to document everything you've done. It's to make someone want to have a conversation with you. Get them interested in the decisions you made, the problems you worked through, the way you think.

If the portfolio does that, the interview will take care of the rest.

If it's just a gallery of screens, even great-looking ones, you'll keep getting filtered out before the conversation starts.