How to choose a hiring assessment tool
By Sergio Gualda · 11 min read · Updated
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.
The two numbers that decide it
Every buying guide in this category opens with a feature comparison, which is why they're all useless. Every tool has every feature. What separates them is the problem they were built to solve, and that maps onto two things about you.
First, how many different kinds of role do you hire for? A company hiring accountants, warehouse staff, support agents and two engineers needs coverage. A company hiring product people needs depth. No tool is good at both, and the ones that claim to be are good at coverage and calling it depth.
Second, what does a wrong hire cost? At high volume the answer is low: you replace the person and the process absorbs it. On a five-person team hiring its second designer, the answer is a year, and possibly the shape of the whole product.
Wide and cheap: buy coverage, and optimise for speed and price per candidate. Narrow and expensive: buy depth, and stop caring about price per candidate entirely. At three hires a year, the gap between $20 and $200 per assessment barely registers next to the cost of getting it wrong.
The five categories that actually exist
Vendors don't describe themselves this way, because every one of them wants to be all five. None of them is. Named examples are illustrations rather than endorsements, and one of these categories is ours.
- Test libraries. Hundreds or thousands of ready-made tests across every function: TestGorilla, Testlify, Adaface. The right answer for breadth. You assemble an assessment per role from stock parts, and the score describes the candidate rather than their fit with your job.
- Work-sample platforms. The candidate produces actual work and it gets graded, increasingly by AI; Vervoe is the clearest example. They're strongest where the job has an observable output in an hour, which is true of far fewer roles than people assume.
- Psychometric instruments. Personality and cognitive ability, grounded in decades of published research: Alva Labs, and the enterprise incumbents. They're the most validated things on this list, and they measure the person rather than the fit with one particular job.
- Game-based assessments. Short games that read cognitive and behavioural signal from how someone plays, such as Equalture. Excellent completion rates, role-agnostic by design, and they need enough hiring history to build a model from.
- Enterprise hiring platforms. Video interviewing, AI screening, ATS integration, everything: HireVue and its peers. They solve throughput across an organisation, which is a different problem from choosing between four people.
The sixth category, and why it barely exists
Purpose-built instruments for one narrow band of roles. There are few of them, and the reason is economic rather than technical: a tool covering six roles can only be sold to companies hiring those six roles, a fraction of the market a library addresses.
That constraint buys something a library structurally can't offer: a result about your role rather than about the candidate in general. A stock product designer test can't know that your role needs someone who will fight about scope while the last one needed someone who ships what's agreed.
uxerhub is in this category, so read the previous paragraph accordingly. And if you hire across more than one function, you'll end up buying a library too; the narrow instrument supplements it rather than replacing it.
What a demo won't tell you
Four questions that change the answer, and that no sales call volunteers.
- What has this been validated against, and on how many people? It's the only question that matters. A good answer names a criterion and a sample size. A logo wall isn't an answer, and neither is “our customers report”. Ask us this too: our instrument isn't yet calibrated against hiring outcomes.
- What happens when a candidate contests a result? If a language model produced the score, explaining it is hard, and the vendor knows it. Ask what the human review process is and who runs it.
- How much unpaid candidate time does this cost, multiplied by everyone you assess? A ninety-minute assessment isn't more rigorous than a fifteen-minute one. It's longer, and the people who decline are the ones with competing offers.
- What does it cost to run one real candidate this week, without a call? A free trial that requires a demo is a lead form. The answer also tells you what the company thinks of your time.
The costs that never appear on the pricing page
There are three, and together they usually exceed the licence.
Candidate time, which you pay in declines rather than money. It doesn't show up in your funnel: you see a shortlist and assume it represents the market, when it partly represents who had a free evening.
Review time. A tool producing rich output that someone has to interpret costs you an hour per candidate of a hiring manager's week, and hiring managers are the most expensive reviewers in the company. A tool producing a recommendation costs five minutes. That difference is larger than any price difference in the category.
Setup, which is where most implementations die. If configuring a role takes an afternoon, it gets done once, badly, and then reused for every later opening regardless of what those openings need.
Where each category breaks
None of this is a criticism of a vendor. Each breaking point follows directly from what that category optimised for, so it's structural and no feature will fix it.
Libraries break when one title covers jobs that need different people, because the test can't know which job it's for. Work-sample platforms break when the job's output takes weeks rather than an hour, and when the artefact can be generated.
Psychometrics break when a stable trait gets used to answer a question about one particular job. Game-based assessments break below the hiring volume needed to model your own performers. Enterprise platforms break on small teams, where the procurement cycle costs more than the hire.
And narrow instruments break the moment your next opening isn't one of the roles they cover, which for most companies is soon.
A shortcut, if you want one
Answer these three and the field collapses to one or two options.
- Do you hire for more than three distinct functions? If yes, you need a library, and the rest of this page supplements that decision rather than replacing it.
- Does the role have an output someone could produce, and you could evaluate, in under an hour? If yes, a work sample beats everything else. If no (and for most product roles it's no), you're choosing between measuring traits and measuring decisions.
- Do two jobs with the same title in your company need different people? If yes, you need something that assesses against the job rather than the title. Almost nothing does.
Frequently asked
- What is the best hiring assessment tool?
- That question has no answer as asked, and any page giving you one is ranking vendors it has a relationship with. The useful version is narrower: best for how many role types, at what cost of a wrong hire, and for roles with verifiable answers or roles without them. Those three make the choice nearly automatic.
- Are free hiring assessment tools worth using?
- Free tiers are usually enough to find out whether a category fits your problem, which is the expensive thing to get wrong. They won't tell you whether the instrument predicts anything. For that you ask about validation, and the answer costs nothing either.
- How many assessments should a candidate do?
- One, in almost every case. Stacking a personality test, a cognitive test and a work sample produces three hours of unpaid work before anyone has spoken to the person, and the third instrument adds close to nothing. Pick the one that answers the question you have.
- Do assessment tools reduce bias in hiring?
- They move it somewhere visible. Deciding in advance what the role needs and scoring everyone identically makes the judgment explicit and arguable, where before it arrived as a feeling after a conversation. That's an improvement, but bias remains: someone still chose the criteria, and an instrument can carry bias in its own construction.