How to Hire Your First Product Designer

Hiring a product designer for the first time is different from hiring almost any other early role. There is no engineering test to lean on, no obvious way to check the work objectively, and the person you hire will shape how your product looks, feels and behaves for years. Most founders default to judging a portfolio. That is a mistake, or at least an incomplete one.

Why the portfolio is the wrong starting point

A portfolio shows you the output. It rarely shows you the thinking. Great designers can present mediocre work persuasively, and average designers can inherit a beautiful final product they had little influence over. What you actually need to know is how someone approaches ambiguity, how they respond to pushback, and whether they can turn a vague founder brief into something buildable.

Use the portfolio as a prompt for conversation, not as evidence in itself. Ask the candidate to walk through one project in detail: what the brief actually was, what constraints they were working under, what they got wrong, and what they would do differently now. The quality of that conversation tells you far more than the screens on the page.

Judgement matters more than style

Early-stage companies do not need a designer with a signature style. They need someone with good judgement under uncertainty: when to ship something rough to learn quickly, when to slow down and get the details right, and when to say no to a feature that will create long-term mess. This is the hardest thing to screen for and the easiest thing to overlook.

A practical way to test judgement is to present a real, unresolved problem from your own product and ask how they would approach it in the first week. You are not looking for a polished answer. You are looking for good questions, sensible prioritisation, and comfort saying “I would need to find out more before deciding.”

Collaboration is the real skill you are hiring for

A first product designer sits between founders, engineers and, eventually, customers. If they cannot work well with engineering, their designs will not ship as intended. If they cannot push back on a founder’s pet idea, the product will accumulate bad decisions.

In interviews, ask about a time they disagreed with an engineer or a founder and how it was resolved. Ask what they need from engineering to do good work, and what they find frustrating about how designers and engineers typically collaborate. Their answers will tell you whether they have actually worked closely with technical teams or only handed off finished files.

Deciding when to hire at all

Not every early-stage company needs a dedicated designer immediately. If you are still working out whether the product has a market, a founder with taste, a fractional designer, or a strong design-literate engineer can often cover the gap. The point at which a full-time hire pays for itself is usually when design decisions are becoming a bottleneck for shipping, or when inconsistent product experience is starting to cost you users or credibility.

When you do hire, resist the urge to over-specify the brief. A generalist who can research, design and prototype will serve you better than a narrow specialist at this stage. Specialisation becomes useful once you have a design team, not before.

How we help

We screen every product design candidate ourselves before a client meets them, testing judgement and collaboration as carefully as craft. Whether you need a single critical hire or are building out a wider product and design function, our services cover retained search and contingent recruitment depending on how urgent and senior the role is. Browse current jobs or get in touch to talk through your first product design hire.