Most designers build portfolios for other designers. Hiring managers are not designers — or if they are, they're reading under conditions that have nothing to do with appreciating craft. They're scanning for evidence that this person can do the specific job we need done. Here's what that actually looks like from the other side of the table.

They read the first case study twice

If the first case study doesn't land, most hiring managers won't read the second. They'll skim it and move on. The first case study is doing 80% of the work of your entire portfolio. Lead with your best, most relevant piece — not your most recent one, not your most visual one, but the one that best matches the role you're applying for.

They're looking for role fit, not breadth

A portfolio that tries to demonstrate every skill a designer could have signals a candidate who doesn't understand the role. Hiring managers want to see that you've done the specific kind of work they're hiring for — and that you've done it well. Three focused case studies beat eight scattered ones every time.

They want evidence of seniority

For senior roles, craft is table stakes. What hiring managers are scanning for is evidence of influence: Did this designer shape the direction of the work, or execute a brief they were given? Did they navigate ambiguity, push back on constraints, or drive alignment across stakeholders? Senior designers are expected to make things happen, not just make things look good. Your case studies should make this unmistakable.

Outcomes matter more than process

Process sections — research, ideation, testing — are necessary but not sufficient. Hiring managers need to see that the process produced something. What changed as a result of the research? What did testing reveal that shifted the direction? What did the shipped product actually achieve? Quantify where you can; qualify where you can't. 'The redesign improved first-session retention by 18%' is memorable. 'Users responded well' is not.

They notice what's missing

Hiring managers notice when a portfolio has no research, when every project appears to have been delivered without friction, when there's no reflection or learning. Real design work involves constraint, compromise, and course correction. A portfolio that omits all of this reads as either inexperienced or untrustworthy. One well-told story about a project that didn't go as planned demonstrates more maturity than ten perfect-looking retrospectives.