Watch your confidence skyrocket

What is a technical aptitude test?

A technical aptitude test is a timed psychometric assessment used by technology employers to measure how well you reason with numbers, patterns, language and unfamiliar problems, before anyone looks at how well you code. It is not a programming exam. It measures the underlying abilities that predict how quickly you will learn on the job: interpreting data, spotting the rule in a system, following logical steps under time pressure and making sound judgements in workplace scenarios.

One point of confusion is worth clearing up straight away, because the same phrase means something different in other industries. Some test publishers and careers sites use "technical aptitude test" to describe mechanical and spatial test batteries, such as the Saville Swift Technical Aptitude, aimed at engineering, manufacturing and trades roles. If that is the test you have been invited to, our mechanical reasoning and spatial reasoning pages will serve you better.

For everyone applying to jobs in the technology industry, this page is for you. When a software company, fintech, consultancy, IT services firm or tech graduate scheme mentions a technical aptitude test, an online assessment or a reasoning test in its hiring process, it almost always means the tests covered below: numerical, logical, diagrammatic, verbal and abstract reasoning, sometimes with a situational judgement test alongside. These assessments usually arrive early in the process, often between your application and your first interview, and they are frequently used as a filter. A strong score gets you through to the stages where you can show what else you can do, which is exactly why they reward preparation.

The good news is that these tests are learnable. The question formats repeat, the underlying skills improve with practice, and familiarity alone removes much of the time pressure that catches candidates out. Take a free practice test on any of the pages below to see where you stand.

Which tests do technology employers actually use?

Most technology employers build their assessment stage from a small set of standard test types, either individually or bundled into a single online assessment. Which combination you face depends on the role: data-heavy and commercial roles lean on numerical reasoning, developer and infrastructure roles lean on logical and diagrammatic reasoning, and graduate schemes often use the full spread. Here is each test type, what it measures in a tech-hiring context, and what to expect.

Numerical reasoning

Technology businesses run on metrics: user growth, conversion rates, uptime, revenue per customer, infrastructure costs. Numerical reasoning tests measure whether you can read that kind of data accurately and draw the right conclusion quickly. In a tech-hiring context, employers use them to check you can work with percentages, ratios, rates of change and multi-step calculations, the everyday arithmetic of standups, sprint reviews and product decisions.

Expect a series of tables, charts and short passages of figures, each followed by multiple-choice questions. The maths itself rarely goes beyond GCSE level; the challenge is extracting the right numbers from the data and working under a strict time limit, often with roughly a minute per question. An on-screen or physical calculator is usually permitted, but the clock means you need to know which calculation to do without hesitation.

Start with a free numerical reasoning practice test on our numerical reasoning page.

Logical and diagrammatic reasoning

These are the test types most closely associated with technology hiring, and for good reason: they measure the same mental muscles that programming and systems work depend on. Logical reasoning tests present sequences and relationships and ask you to deduce the rule that governs them. Diagrammatic reasoning tests go a step further, showing you inputs passing through operators or processes and asking you to work out what each operator does, which is essentially debugging in miniature. Employers treat strong performance here as a signal that you can hold a system in your head, trace cause and effect, and reason from rules to outcomes.

Expect sequences of shapes or symbols with one frame missing, sets of figures to classify, and flow diagrams where coded operators transform an input. Questions typically get harder as the test progresses, and time pressure is deliberate: the tests are designed so that few candidates finish comfortably.

Try a free logical reasoning practice test on our logical reasoning page, and a free diagrammatic reasoning practice test on our diagrammatic reasoning page.

Verbal reasoning

Technology work is more written than outsiders expect: requirements documents, technical specifications, documentation, tickets, incident reports and a constant stream of asynchronous communication. Verbal reasoning tests measure whether you can read a dense passage once, understand precisely what it does and does not say, and resist reading your own assumptions into it. In tech hiring, that maps directly onto interpreting a spec correctly the first time.

Expect short passages followed by statements you must mark as true, false or cannot say based only on the passage. The "cannot say" option is where most marks are lost, because it forces you to separate what the text states from what merely seems plausible. Passages in tech-flavoured assessments may draw on business or technology topics, but no prior knowledge is needed; everything you need is in the text.

Practise with a free verbal reasoning practice test on our verbal reasoning page.

Abstract reasoning

Abstract reasoning tests are the purest measure of fluid intelligence in the battery: the ability to find patterns in material you have never seen before. That is precisely why technology employers like them. Tech roles involve constant novelty, whether that is a new framework, an unfamiliar codebase or a problem no one has documented, and abstract reasoning performance indicates how quickly you get to grips with the genuinely new. Because the tests use shapes rather than words or numbers, they are also less affected by educational background, which makes them popular for high-volume graduate screening.

Expect grids and sequences of abstract shapes governed by one or more hidden rules, such as rotation, reflection, alternation or changes in number and shading. Your task is to identify the rule and choose the figure that continues the pattern. Speed matters: the format rewards candidates who have seen enough patterns in practice to recognise rule types on sight.

Take a free abstract reasoning practice test on our abstract reasoning page.

Situational judgement

Not every quality tech employers care about shows up in a reasoning score. Situational judgement tests (SJTs) present realistic workplace scenarios, such as a slipping deadline, a disagreement over a technical approach, an unhappy stakeholder or a teammate who is struggling, and ask which responses are most and least effective. In a tech-hiring context they measure collaboration, prioritisation, communication and integrity, the behaviours that determine whether a technically capable hire actually works well in a team.

Expect a scenario followed by four or five possible responses, which you rank, rate or select from. There is rarely a perfectly obvious answer; the test is calibrated against how the employer's most effective people respond. Unlike the reasoning tests, SJTs are usually untimed or generously timed, and preparation is about understanding what employers value: taking ownership, communicating early, escalating appropriately and putting the team's outcome ahead of personal credit.

See how you fare with a free situational judgement practice test on our situational judgement page.

How aptitude tests fit alongside coding assessments and interviews

If you are applying for a technical role, the aptitude test is usually one layer in a longer funnel, and it helps to know exactly what each layer is measuring.

A typical technology hiring process runs: application, then online aptitude tests, then a coding assessment or technical exercise, then interviews. The aptitude stage measures trainability and raw problem-solving, and it typically acts as the first filter because it is cheap to administer at scale. The coding assessment, often delivered through a HackerRank-style platform, measures your current technical skill: can you actually write working code against a specification, today. Interviews then probe depth, judgement and fit.

The two assessment types are complementary, not interchangeable. An employer hiring graduates or career changers may weight aptitude heavily, because it wants people who will learn fast rather than people who already know a particular stack. An employer hiring senior engineers may weight the coding stage more, but still use aptitude tests to screen a large applicant pool down to a manageable shortlist. Non-coding tech roles, such as product, delivery, QA, support and technology consulting, often use aptitude tests and SJTs without any coding stage at all.

The practical implication is simple: you cannot interview your way past a failed aptitude test, because you will never reach the interview. This site prepares you for the aptitude side of the funnel. Your coding practice belongs elsewhere; your reasoning practice starts with a free practice test here.

Worked examples

The fastest way to understand these tests is to try them. Here is one diagrammatic question and one numerical question, each with a full explanation.

Example 1: diagrammatic reasoning

A process diagram shows symbols passing through coded operators. You are shown what each operator does by example, then asked to apply them.

• Input ♦ ♠ ♥ passes through operator X and becomes ♥ ♠ ♦
• Input ♦ ♠ ♥ passes through operator Y and becomes ♠ ♥ ♦

Question: the input ▲ ● ■ passes through operator X, and the result then passes through operator Y. What is the final output?

A) ■ ● ▲ B) ● ▲ ■ C) ● ■ ▲ D) ▲ ■ ●

Answer: B. First work out each operator's rule from the examples. Operator X turns ♦ ♠ ♥ into ♥ ♠ ♦: the sequence is reversed. Operator Y turns ♦ ♠ ♥ into ♠ ♥ ♦: the first symbol moves to the end. Now apply them in order. X reverses ▲ ● ■ to give ■ ● ▲. Y then moves the first symbol to the end: ■ moves behind ● ▲, giving ● ▲ ■. The common mistake is applying the operators in the wrong order or trying to combine both rules in one mental step; in the real test, write nothing off and process one operator at a time.

Example 2: numerical reasoning

A cloud platform commits to 99.9% uptime for its customers each calendar month. The table shows its recorded downtime.

Question: in which months did the platform meet its 99.9% uptime commitment?

A) April and May B) May only C) May and June D) All three months

Answer: C. A 99.9% uptime commitment allows at most 0.1% of the month as downtime. For a 30-day month that is 0.001 × 43,200 = 43.2 minutes; for a 31-day month it is 0.001 × 44,640 = 44.64 minutes. April recorded 50 minutes against an allowance of 43.2, so it breached. May recorded 41 minutes against 44.64, so it met the commitment. June recorded 43 minutes against 43.2, inside the allowance by a fraction of a minute, so it also met the commitment. Note the two traps: April and June have the same allowance but May does not, because the allowance depends on the length of the month, and June's result is close enough that rounding carelessly flips the answer. Real numerical questions are built the same way: straightforward arithmetic wrapped around details that punish assumptions.

If both of those felt comfortable, test yourself against the clock with a free practice test. If either felt unfamiliar, that is precisely what practice fixes.

How to prepare for a technical aptitude test

Preparation for these tests follows a reliable pattern, and modest, consistent effort moves scores meaningfully.

Start with a diagnostic. Take a free practice test in each type your employer uses, under timed conditions, before you do anything else. This tells you where your time is best spent; most candidates have one clear weak area, and improving it yields more than polishing a strength.

Practise timed, always. The single biggest difference between practice and the real thing is the clock. Untimed practice builds accuracy but not the pacing instinct you need. Work at roughly a minute per question and learn to make the call between solving, guessing and moving on.

Review every explanation, including for questions you got right. The value of practice is in the explanations. When you review why an answer is correct, you are learning the rule types, calculation shortcuts and question conventions that repeat across tests. A right answer reached slowly or by luck still has something to teach you.

Train little and often. Several short sessions across a week or two beat one long cramming session. Pattern recognition, which underpins the logical, diagrammatic and abstract formats, builds through repeated exposure rather than intensity.

Rehearse the conditions. Sit at least one full-length practice test in exam conditions: quiet room, laptop, calculator and rough paper if permitted, no pauses. On the day itself, confirm the basics in advance: a stable internet connection, a charged machine, and the test provider's rules on calculators and notes.

Know your test provider if you can. Invitation emails usually name the assessment platform. Question styles vary slightly between publishers, so if you know which one you are facing, weight your practice towards that style.

Ready to begin? Choose a test type above and take a free practice test now.

Frequently asked questions

What is a technical aptitude test? In technology hiring, a technical aptitude test is a timed online assessment measuring the reasoning skills that predict success in tech roles: numerical, logical, diagrammatic, verbal and abstract reasoning, sometimes alongside a situational judgement test. It assesses how you think, not what you already know about any particular technology.

Is a technical aptitude test the same as a coding test? No. A coding test measures your current programming skill by asking you to write working code. An aptitude test measures underlying reasoning ability and trainability, and requires no programming knowledge. Many tech hiring processes use both, with the aptitude test coming first.

Are technical aptitude tests the same as mechanical aptitude tests? No, although the names overlap. Some publishers use "technical aptitude test" for mechanical and spatial batteries aimed at engineering and trades roles, such as the Saville Swift Technical Aptitude. Tests for technology-industry jobs are reasoning based. Check your invitation email for the test publisher and format if you are unsure which you are facing.

Which employers use technical aptitude tests? They are common across the technology sector and beyond it: software companies, fintechs, consultancies, IT services firms, banks hiring for technology divisions and graduate schemes of all kinds. They are most heavily used where application volumes are high, because they provide an objective early filter.

Do I need a maths or computer science background to pass? No. The numerical content rarely exceeds GCSE-level arithmetic, percentages and ratios, and no test in the battery requires programming knowledge. The tests are designed to measure reasoning ability rather than education, which is why practice, rather than study, is the right preparation.

How long do the tests take? It varies by employer and publisher, but individual tests are short, commonly somewhere between ten and thirty minutes each, with roughly a minute per question on the reasoning formats. A full battery of several test types can usually be completed within an hour or so, often in one sitting.

What score do I need to pass? There is no universal pass mark. Your raw score is compared with a norm group, such as other graduate applicants, and each employer sets its own cut-off, which typically varies with application volume. The practical goal is to score as highly as you can, and practice is the most reliable way to raise your percentile.

Are calculators allowed in numerical reasoning tests? Usually yes, since the tests measure data interpretation rather than mental arithmetic, but policies differ between publishers and some provide an on-screen calculator only. Check the instructions in your invitation, and practise both with and without one so the rules on the day do not unsettle you.

Can I retake a technical aptitude test if I fail? Generally not within the same application; most employers allow one attempt per hiring cycle, though you can usually reapply in a future cycle. Some employers also re-test shortlisted candidates at an assessment centre to verify online scores, which is another reason to prepare properly rather than rely on a lucky run.

How should I prepare if my test is only a few days away? Prioritise ruthlessly. Take a free practice test in each type you will face to find your weakest area, spend most of your remaining time on timed practice there, and read the answer explanations carefully. Even a few focused sessions build the format familiarity that removes most avoidable mistakes.

Ready to see where you stand? Every test type on this page has questions written in the style technology employers actually use, with full explanations for every answer. Pick your weakest area from the cards above and take a free practice test today.