Judging a product designer by their visuals is like judging a chef by how well they can plate.
Sure, plating matters. Garnish matters. Nobody wants a sloppy plate. But if the chef can't run a kitchen, build a menu, or hold it together when the tickets are piling up, who cares how nice the parsley looked?
Even Michelin—the people who literally invented the star system—don't judge restaurants by how the food looks. They gave a star to a $2 chicken rice hawker stall in Singapore. Plastic stools. Hanging chickens. No tablecloths. Because they're judging ingredient quality, harmony of flavors, mastery of technique, consistency, and the chef's voice. Not the presentation.
Here's the thing: in most orgs, individual designers have surprisingly little control over the visuals. They're working inside design systems, brand guidelines, legacy UI inherited from someone who left three years ago, accessibility standards, and platform conventions. The pixels you're evaluating in a portfolio? Those are often the most constrained part of the job.
So when you treat high-fidelity screens as the primary signal, you're mostly measuring how well someone complied with the guardrails—not how much judgment, taste, and strategic thinking they bring to the table.
The real work—the expensive work, the work that actually moves the needle—is invisible:
- Figuring out which problem to solve (and having the spine to say no to the wrong ones)
- Turning vague stakeholder vibes into actual requirements
- Making trade-offs when the timeline, the tech, and the user goals don't all fit in the same box
- Aligning a room full of people who all have different definitions of 'done'
- Shipping something that holds up in production, not just in a prototype
Less than 10% of what product designers do is visual. The other 90% is the scaffolding that makes the visual even possible.
When a hiring manager flips through a portfolio like it's a Pinterest board, they're grading the least representative slice of what product designers actually do—and they're going to end up hiring decorators, not designers.
And frankly, it cheapens the whole discipline.
It feeds the myth that designers exist to make things pretty at the end—that we're the garnish, not the recipe. But the best design work happens upstream. Defining the mental model. Mapping the edge cases. Shaping the rules that govern how a system behaves. Get that right, and the screens practically draw themselves. Get it wrong, and no amount of visual polish will save you.
"Okay, but I have 1000 applicants and 20 minutes. Visuals are a quick filter. What else am I supposed to do?"
Fair. You need a heuristic. But if you're going to skim, skim for the right things.
Instead of scanning for pretty pixels, scan for these:
- Can they articulate a problem? If the case study opens with 'I redesigned the dashboard' instead of 'Users were abandoning the onboarding flow because...'—move on. That tells you they think in outputs, not outcomes.
- Do they show constraints and trade-offs? A portfolio full of 'here's my beautiful solution' with no mention of timeline, tech limitations, stakeholder pushback, or what got cut is a red flag. Real work is messy. If everything looks pristine, they're either hiding something or they've never shipped anything hard.
- Did it actually ship? Concepts are fine for students. But if a senior designer's portfolio is all speculative redesigns and zero production work, be skeptical. It's easy to design something beautiful when there's no deadline breathing down your neck and no legacy system fighting back. Anyone can make something gorgeous when the conditions are perfect—that's not the job. The question isn't 'can they design in a vacuum?' It's 'can they ship something good when the conditions are difficult?'
- Do they talk about outcomes? 'We reduced support tickets by 30%' hits different than 'I created a clean, modern interface.' One shows impact. The other shows they know how to use Figma.
This takes the same 60 seconds as scanning visuals. But it filters for judgment, not just aesthetics.
The best designers don't just make things look good. They make things work—and then make them look good.