The Complete Guide to Cognitive Ability and Aptitude Testing
How to Implement Cognitive Ability and Aptitude Tests
This is a practical guide to get you started with implementing cognitive ability tests in your own organisation. If you haven’t already, it may be worth checking though the previous chapters of this guide, to better understand what they are, their key benefits and how to choose the right tests.Â
Key Takeaways:
- Define purpose: Use tests as a screen, a final data point, or for development.
- Timing: Test after the CV filter but before interviews to maximize efficiency.
- Scoring: Set thresholds based on internal benchmarks, not just industry averages.
- Communication: Brief candidates on the “why” and “how” to improve experienceConsistency: Administer identical tests under identical conditions for fairness.
- Interpretation: Prioritize percentile ranks over raw scores for better context.
- Balance: Combine test data with interview impressions; never rely on one alone.
- Evolution: Review hiring data annually to refine and improve your thresholds.
Step 1: Define What You're Trying to Achieve
Before sending a single test, be clear on what you’re using it for. This isn’t just about having a purpose statement — it shapes every practical decision that follows.
The most common uses are:
- Early-stage screening to reduce the number of candidates going forward to interviews
- A data point alongside interviews to inform a final hiring decision
- Evaluation for internal promotion or role change
- Identifying development needs and learning potential in existing employees
These aren’t mutually exclusive, but they require slightly different approaches. For external hiring, you’ll typically set a threshold score that filters candidates before interviews. For internal decisions, scores tend to be used as one input in a broader conversation rather than as a filter. For development purposes, there’s no threshold at all — you’re using the data to understand someone better, not to make a pass/fail call.
Knowing which of these applies helps you communicate the process correctly, interpret results appropriately, and avoid using the test in a way it wasn’t designed for.
Step 2: Decide When to Implement The Test in Your Process
For external hiring, the most common and practical placement is after an initial application filter — once you’ve removed anyone who clearly doesn’t meet the basic requirements of the role — but before interviews.
This ordering makes sense for a simple reason: interviews take a lot of time. Testing before interviews means you’re only investing that time in candidates who’ve already demonstrated the cognitive capability to do the job. It also means you go into interviews with data in hand, which can shape the questions you ask.
Some organisations send the test at the very start of the process, before any CV review. This works well for high-volume roles where you’re receiving more applications than you can meaningfully screen. The test becomes your first filter rather than your second.
The one placement to avoid is using it as an afterthought at the end of the process — for example, testing candidates who’ve already completed multiple interview rounds. By that point, you’ve already invested heavily in them, and using a test result to reverse a near-final decision creates problems both practically and in terms of candidate experience.
Step 3: Establish Your Scoring Approach Before You Start
This is the step most organisations skip — and it’s where a lot of avoidable problems come from.
Before you test anyone, you need to decide how you’re going to use scores. There are two main approaches:
Threshold scoring — you set a minimum score, and candidates who fall below it don’t progress. This is easy to administer and works well for high-volume screening where you need an efficient filter. The risk is that thresholds set too high cut out capable candidates, and thresholds set too low add little value.
Comparative scoring — you don’t set a hard cutoff, but use scores to rank or compare candidates relative to each other. This is more nuanced and works well when you’re dealing with smaller applicant pools or using the test as one input alongside others.
A sensible starting point for most organisations is a moderate threshold — one that filters out clearly low scores while still leaving you a reasonable pool to interview. Your test provider should be able to advise on what score ranges typically indicate for the type of role you’re hiring for.
A word on benchmarking. Ideally, your threshold reflects your own organisation’s standards — not just industry averages. The most reliable way to build this is to administer the same test to your current employees in the same or similar roles, then look at where your stronger performers score. This gives you a real-world reference point specific to your context.
If you’re just starting out and don’t have that data yet, lean on your provider’s benchmark data for comparable roles as an interim guide. As you build up your own data over time — seeing how candidates who scored at different levels actually perform once hired — you can refine your thresholds to reflect your own experience.
One important note: don’t benchmark exclusively against your top performers. If your threshold only allows through candidates who match your very best people, you’ll cut your pool too aggressively and miss capable candidates who simply score slightly lower. The goal is to screen out those unlikely to succeed — not to only let through clones of your best hire.
Step 4: Communicate The Process Clearly — To Candidates and Your Internal Team
For candidates, how you introduce the test matters. Candidates who understand why they’re being asked to complete an assessment, what it involves, and roughly how long it takes approach it more straightforwardly — and it reflects better on your organisation as an employer.
A brief, clear explanation is all that’s needed. Something along the lines of:
“As part of our process for this role, we ask all candidates to complete a short online cognitive ability assessment. It takes around 20 minutes and looks at how you approach problems and process information. There’s no specific knowledge required.”
This reduces potential anxiety, sets accurate expectations, and gives candidates the best chance of performing at their actual level rather than being thrown off by an unexpected or unexplained step.
For your internal team, if multiple people in your organisation are involved in hiring decisions, they all need to understand how to interpret and use scores correctly — particularly anyone who might be inclined to treat a score as the final word, or conversely, to dismiss it entirely because it doesn’t match their interview impression.
A short internal briefing before rolling out is worth doing. Key points to cover: what the score does and doesn’t measure, what your threshold is and why, and how scores should factor into the overall decision alongside other information.
Step 5: Administer The Test Consistently
Every candidate for the same role should complete the same assessment under the same conditions. This is both a practical and a fairness requirement — scores are only meaningful when they’re comparable.
In practice this means:
- The same test version for all candidates in a role
- The same time allowance for everyone (most modern platforms handle this automatically)
- Clear, consistent instructions sent to all candidates at the same point in the process
- Accommodations documented and applied consistently for candidates who need them — for example, extended time for candidates with specific learning differences
For internal assessments, the same principle applies. If you’re evaluating several employees for a promotion, they should all complete the same assessment.
Step 6: Understand What You're Reading in The Results
Most cognitive ability test results show two things: a raw score (the number of correct answers) and a percentile rank (how that score compares to the reference population).
The percentile is generally more useful than the raw score alone, because it gives you context. A raw score of 32 out of 50 tells you little on its own. Knowing that score places a candidate in the 78th percentile — meaning they scored higher than 78% of comparable candidates — tells you something meaningful.
Some reports also show sub-scores across different cognitive areas — for example, separate scores for verbal, numerical, and abstract reasoning. These can be useful for roles where one particular area is especially critical. A finance role might weight the numerical sub-score more heavily. A communications role might look more closely at verbal reasoning.
Step 7: Use Scores As One Input in Your Decision Making— Not The Only Factor
A score tells you something important about a candidate’s cognitive capability. It doesn’t tell you about their motivation, their communication style, how they work with others, or whether they’re genuinely interested in the role.
The practical decision-making process for most hiring situations looks something like this:
- Use the test score to filter or rank candidates at the screening stage
- In interviews, treat the score as context — not as a verdict already reached
- Where scores and interview impressions align, that’s a stronger signal in either direction
- Where they conflict, dig into why
That last point is worth dwelling on. If a candidate scores highly but interviews poorly, it’s worth understanding what the disconnect is — poor communication style? Disengagement? Nerves? These are different problems with different implications. If a candidate interviews exceptionally well but scores below your threshold, that’s a judgment call: there may be a good explanation, or the interview may simply be doing what interviews often do, which is flattering candidates who present confidently.
Neither score nor interview should automatically override the other. The combination of both, interpreted by a human who understands the role, is where good hiring decisions come from.
Step 8: Review and Improve Over Time
The real value of using cognitive ability tests compounds over time as you build your own data.
Track what happens after you hire. Do the candidates who scored in a certain range perform better or worse in the role? Do they stay longer? Do they progress? This kind of follow-up takes effort, but it turns your scoring approach from a borrowed benchmark into something calibrated to your actual organisation and roles.
Even a simple informal review — looking back at a year’s worth of hires and comparing assessment scores with how those people are actually performing — gives you useful signal. Over time, you can refine your thresholds, adjust for specific roles, and build a much more grounded sense of what scores actually mean in your context.
This is also how you start to catch problems early. If you notice that candidates who scored above your threshold are still struggling in a particular role, that might indicate the test alone isn’t sufficient for that role, or that your threshold needs adjusting. If you’re finding that your threshold is cutting out candidates who would have done well, you can revise it. The system should improve with use.
A Note on Legal and Compliance Considerations
Laws around the use of pre-employment assessments vary by country and in some cases by state or region. In most jurisdictions, the key requirements are that assessments are job-related, applied consistently to all candidates, and don’t disproportionately exclude protected groups without justification.
Using a validated, reputable assessment goes a long way toward meeting these requirements, but it doesn’t remove the need to understand the rules in your specific context. If you’re rolling out assessment at scale, or in a jurisdiction with specific requirements — the UK, EU, US, and Australia all have different frameworks — it’s worth confirming your approach with your legal or HR team before you start.