Portfolio reviews for experienced designers: what to look for

The most polished senior portfolios I've seen in interviews were for candidates who didn't get the offer. The portfolio was beautifully presented, every case study told a clean narrative, the outcomes were compelling. And in the conversation, it became clear that the designer had a very limited understanding of why the work went the way it did.

At the junior and mid levels, a strong portfolio is evidence of strong craft. At senior levels, the portfolio is just context for a more important question: how does this person think when they're in the middle of a hard problem?

What polished portfolios hide

A senior portfolio is a retrospective. It's the version of the work that the designer assembled after knowing how things turned out. The hard decisions got resolved before the case study was written. The direction that didn't work got cut. What you see is the path from problem to solution, which looks logical in hindsight and was almost certainly not logical in the moment.

This means polished portfolios naturally obscure the things you most need to evaluate in a senior hire: how the designer navigates ambiguity, what they do when the problem definition is wrong, how they handle stakeholders who push back, how they decide when to fight for a direction and when to compromise.

None of that shows up in a case study that was written after the project shipped successfully.

The questions that get under the surface

The portfolio is a starting point for the conversation, not the content of it. The useful questions are the ones that push past the narrative.

"What didn't work on this project?" is one. But it's common enough that many designers have prepared an answer. The follow-up is more useful: "What did you do when that didn't work?" A practiced answer tends to be abstract. A real one tends to be specific and a little uncomfortable to tell.

"Who disagreed with you on this, and how did it get resolved?" almost always produces useful information. Every meaningful design project has a moment where someone pushed back. How the designer handled that moment tells you more about how they'll operate on your team than any artifact in their portfolio.

"What would you do differently if you had to start over?" surfaces self-awareness. The designer who says nothing differently is either telling you the project was perfect, or that they're not used to reflecting critically on their own work. Neither is a good sign at the senior level.

What you're actually evaluating

At the senior level, you're evaluating three things the portfolio doesn't directly show you.

The first is reasoning quality. Can this person explain why they made the decisions they made, in a way that holds up when you push on it? Not confidence. Designers can be confidently wrong. But the ability to work through a question in real time, recognize what they don't know, and adjust.

The second is operating style under constraint. Senior designers work in conditions of resource shortage, unclear requirements, competing stakeholder priorities. Does this person have a history of doing good work in those conditions, or only in well-resourced, well-defined projects?

The third is what they want to get better at. A senior designer who isn't actively trying to improve something specific is a designer who's coasting. Not necessarily bad, but worth knowing before you hire them. "What are you working on in your own development right now?" is a low-stakes way to find out.

The portfolio presentation itself

How a designer presents their portfolio is part of the evaluation, not a formality before the real interview. Watch for whether they orient you to what they're about to show you, or drop you into the work without context. Watch for whether they leave space for questions or run through the case study as a performance. The candidates who treat the presentation as a conversation tend to be better at the real thing.

The portfolio that's made to impress is designed for a passive audience. The work that will matter in the role happens with people who are engaged, pushing back, and not yet convinced. Those are very different contexts, and how a candidate handles the difference in the interview is a reasonable preview of how they'll handle it on the job.