I've been on both sides of the portfolio review. I've had mine skipped over, and I've sat in hiring panels watching the design lead spend forty-five seconds on a candidate's work before moving on. The math is brutal: hiring managers are reviewing twenty, sometimes forty portfolios for one role. If yours doesn't stop the scroll in the first thirty seconds, you're not getting a call — regardless of the quality of work buried three case studies deep.

These are the patterns I've seen kill candidates' chances before anyone's read a word of their process.

The first thirty seconds problem

Your portfolio landing page is doing one job: convincing a tired hiring manager that clicking further is worth their time. Most portfolios fail this test immediately. What I see constantly:

• A hero section that tells me nothing.
• 'I am a product designer who loves to solve problems.' That's every product designer on the planet. What kind of problems? In what context? For what scale of product? Give me something to grab onto.
• Showcase images that don't render in the first viewport.
• If I have to scroll to see any actual design work, the page is failing. Put something visually compelling above the fold. Not a photo of yourself — your work.
• No clear specialisation signal.
• Generalist portfolios are fine for junior roles. At mid-senior level and above, I need to see what you're particularly good at — B2B enterprise, complex data products, consumer mobile, design systems. Breadth without depth reads as scattered.

The case study mistakes that lose you the interview

Getting someone to open a case study is the first win. Keeping them is the second. This is where most portfolios collapse entirely. The work might be genuinely strong, but if the case study doesn't communicate it clearly and quickly, it doesn't matter.

• No framing of the problem.
• Jumping straight into 'Here's what I designed' with no context about why the problem mattered, who it affected, or what the constraints were. Every case study needs a crisp problem statement in the first paragraph. If I don't understand what you were solving, I can't evaluate whether your solution is good.
• Outcomes that are all activity, no impact.
• 'We ran workshops, created wireframes, iterated through three rounds of testing.' That's a process description. What actually changed? What did users do differently? What moved for the business? If you can't share real metrics, find another way to evidence impact — qualitative signals, stakeholder feedback, what shipped versus what the original brief asked for.
• Personal projects presented like product work.
• I'm not anti-personal projects. But if your case study involves a redesign of Spotify with no access to users, no real constraints, and no shipped outcome, label it as a design exercise. Presenting it alongside real work without flagging the difference reads as dishonest.

What actually makes me stop scrolling

Since this article is mostly cautionary, let me balance it. Here's what makes me slow down and read properly:

• A clear point of view early.
• Not confidence theatre — an actual position. Someone who can articulate what they believe good design is, in the context of their work history. That's a senior signal.
• Honest framing of constraints and tradeoffs.
• 'We wanted to do X, but the technical constraints meant we shipped Y, and here's what we learned from it.' That's how real product teams work. It tells me you can operate in messy reality, not just ideal conditions.
• Evidence that you influenced something beyond the pixels.
• Changed how the team worked, reframed the brief, pushed back on a requirement that wasn't serving users. This is what separates designers who produce outputs from ones who shape direction.

The portfolio is a filtering mechanism, not a complete picture of who you are. It needs to be clear enough, compelling enough, and honest enough to get you into a conversation. The interview is where you tell the full story. Don't overcomplicate it. Strip it back to the work that best represents what you want to do next, frame it with enough context to make it legible, and let the quality speak.