Hiring your first designer without a design leader
When you're hiring your first product designer, finding candidates is the easy part. The hard part is that nobody at the company can tell a strong one from a well-presented one. A structured assessment gives you an outside reference: the same twelve situations for everyone, scored against the capabilities you said this role needs, and a recommendation you can read without being a designer.
Request access to the betaNo card or call needed, and the report is ready the second they finish.
What usually happens
You have five candidates. All five portfolios look good, because portfolios are made to look good and because the people who make them are designers. You have no internal benchmark and no design lead to ask, so you can't tell whether you're looking at senior work or a competent presentation of junior work.
So you fall back on the interview, and the interview rewards whoever is most comfortable talking about their work. That correlation with judgment is weaker than most founders assume, and it's weakest where the stakes are highest: at senior level, where the calmest presenter is often the one who has been shielded from the hard decisions.
$40,000
What a wrong first design hire costs a seed-stage company, before counting the four months of product direction that went with it.
The objection we hear
“I'm not a designer. How would I even read the result?”
That's the reader the report is written for. It opens with a recommendation in plain language, without design vocabulary.
You don't need to know what information architecture is to see the difference between someone who says “we should improve the onboarding experience” and someone who says “88% set up their venue without help; they aren’t lost, they’re tired”. One of those is thinking. You can tell which.
How it fits your process
01 / 03
After the first call, before the final round
Send it once you have three to five people you'd seriously consider. Running it earlier wastes candidates' time; running it later means you've already formed an opinion the report has to fight.
02 / 03
It gives you questions as well as a ranking
The most useful output for a founder is the “main risk” line. It tells you what to press on in the final conversation, which is the part you're good at.
03 / 03
It works for a contractor too
The same case works whether you're hiring permanently or bringing someone in for three months. The failure mode is identical: paying for six weeks before discovering the fit is wrong.
Roles you probably hire
Product Designer
The CEO: “We need a guided onboarding with tooltips. I saw it at a competitor and it works.”
Product Manager
The CRO: “Sales lost three deals this quarter because we don't have SSO. Put it in the next sprint.”
Design Engineer
A product designer: “Just add a variant to the button component, it's a one-line change.”
Questions
Questions from startups
That's the strongest case for it. A team that hires ten designers a year develops a feel for it and can afford a mistake. Hiring one means you get a single attempt with no calibration, and that person defines your product for the next two years.
Not with this format. Seniors object to unpaid weekend assignments. Fifteen minutes on a fictional company, with nothing to prepare, is a different request. And they only sit it once: if another company asks for the same assessment, they don't repeat it.
Yes, and it's arguably the best fit. A founding designer is hired for judgment under total ambiguity, which is exactly what the case puts them in.
Related reading
Read these before you decide
9 min
How to hire a UX designer
Start by deciding whether you need a UX designer or a product designer, because in most companies today the two titles describe the same job and in a few they don't. Then assess the three things a portfolio structurally can't show: what they questioned in the brief, what they cut when the date wouldn't move, and what they refused to ship. Everything else (visual craft, tool fluency, case study narrative) is either visible in the work or no longer reliable evidence of anything.
Read it11 min
How to choose a hiring assessment tool
The choice is decided by two numbers before any feature list matters: how many different roles you hire for, and what a wrong hire costs you. Wide and cheap points to a test library; narrow and expensive points to a purpose-built instrument. Everything vendors compete on (question formats, integrations, dashboards) only starts to matter once those two numbers have eliminated most of the market.
Read it8 min
How to evaluate a UX researcher
Evaluate a UX researcher on what they refuse to conclude: whether they reframe a question that can't be answered, whether the method follows the decision rather than the budget, how they spot a flawed study and say so, and how they deliver a finding nobody wants. A portfolio shows conclusions that survived. It never shows the studies that shouldn't have been run.
Read it