Hiring your first designer without a design leader
When you are hiring your first product designer, the problem is not finding candidates — it 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 needing to be a designer.
Request access to the betaNo card. No call. The report exists 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, no design lead to ask, and no way of knowing whether what you are looking at is 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 actual judgment is weaker than most founders assume, and it is weakest exactly 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 is the case the report is written for. It leads with three sentences the candidate actually wrote, and the score attached to each — not with design vocabulary.
You do not 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 are not lost, they are tired”. One of those is thinking. You can tell which.
How it fits your process
After the first call, before the final round
Send it once you have three to five people you would genuinely consider. Running it earlier wastes candidates' time; running it later means you have already formed an opinion the report has to fight.
It gives you questions, not just 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 are actually good at.
It works for a contractor too
The same case works whether you are hiring permanently or bringing someone in for three months. The failure mode — paying for six weeks before discovering the fit is wrong — is identical.
Roles you probably hire
Product Designer
“We need a guided onboarding with tooltips. I saw it at a competitor and it works.” — the CEO
Product Manager
“Sales lost three deals this quarter because we don't have SSO. Put it in the next sprint.” — the CRO
Design Engineer
“Just add a variant to the button component, it's a one-line change.” — a Product Designer
Questions from startups
That is the strongest case for it, not the weakest. A team that hires ten designers a year develops a feel for it and can afford a mistake. Hiring exactly one means you get a single attempt with no calibration, and it defines your product for the next two years.
Not at this format. Seniors object to unpaid weekend assignments, not to 75 timed minutes on a fictional product with the criteria published upfront. And they only sit it once: if another company asks for the same assessment, they do not repeat it.
Yes, and it is 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
Worth reading before you decide
9 min
How to hire a UX designer
Start by deciding whether you actually need a UX designer or a product designer, because in most companies today the title is the same job and in a few it genuinely is not. Then assess the three things a portfolio structurally cannot show: what they questioned in the brief, what they cut when the date would not 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 already 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 cannot 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 should not have been run.
Read it
You have an open role right now.
Invite one candidate and read their report the moment they finish.