DRW Psychometric Tests Prep

• Core-skills practice. Numerical, verbal and logical reasoning at graduate level: the skills under DRW's test, without pretending to be its interface.
• Provider-true difficulty. Item difficulty mirrors the band the real tests sit at, so your score means something.
• Coaching, not just a score. "You are spending too long on table-data questions" beats "you scored 68%". Specific advice per weak section.
• Percentile benchmarking. Your score placed on a modelled UK graduate norm curve, so you know if 70% is excellent or worrying for that test.

Free practice section, scored. Sign up free to save your report.

1. 1

   Time management collapse

   Spending too long on difficult questions early in the test, leaving half the module unattempted.

2. 2

   Misreading verbal constraints

   Applying real-world logic to verbal statements instead of strictly adhering to the provided text.

3. 3

   Calculation rounding errors

   Failing to track decimal places or misinterpreting data scales in numerical tables.

4. 4

   Ignoring test interface navigation

   Losing precious seconds trying to figure out how to submit or flag questions due to unfamiliarity with the Aon or HackerRank interface.

5. 5

   Inefficient algorithmic complexity

   Writing brute-force code solutions in coding tests that fail performance benchmarks on large datasets.

6. 6

   Inconsistent situational profiling

   Providing contradictory answers in situational judgement or workstyle profiles due to overthinking.

7. 7

   Failure to test edge cases

   Submitting code without checking for null pointers, zero values, or boundary limits.

8. 8

   Neglecting practice calibration

   Walking into the real assessment cold without experiencing the severe time pressure of modern adaptive tests.

• Platform interface fluency

  Practicing on exact interface clones so that clicking, navigating, and keyboard shortcuts become second nature.

• Rigorous time-budgeting

  Allocating a strict hard stop per question (e.g., maximum 35 seconds per numerical item) and moving on instantly if stuck.

• The "Cannot Say" discipline

  Cultivating instant mental separation between personal assumptions and strict textual proof in verbal reasoning.

• Pre-test calibration runs

  Completing at least 5 to 10 full-length timed mock tests under strict exam conditions prior to opening the official link.

• Complexity awareness

  Mentally calculating time and space complexity ($O(n \log n)$ vs $O(n^2)$) before writing a single line of code.

• Error-free scratchpad usage

  Maintaining a clean physical notepad during numerical tests to jot down intermediate figures without mental math fatigue.

• Emotional reset capability

  Maintaining composure after missing a question and immediately refocusing on the next item without panic.

• Structured prioritization

  Selecting high-yield, straightforward questions first in mixed-format evaluations.

• Where to get practice material

  Use specialized psychometric preparation sites that replicate the exact Aon cut-e and SHL interfaces (such as AssessmentDay, JobTestPrep, or TestSolve AI). For coding components, practice actively on LeetCode and HackerRank under timed constraints.

• Hours to invest

  Successful candidates typically invest between 15 to 25 hours over a 2-week window leading up to the assessment.

• Key drilling habit

  Practice under conditions where you deliberately force yourself to abandon questions that take longer than 30 seconds to prevent time-management failure during the real exam.

1. 01Set your own clock per question. Divide section time by question count. Move on when you hit your per-question budget, even if you are mid-thought.
2. 02Read the question before the chart. Half the work in numerical is finding the right number in a table. Knowing what you are looking for cuts the time in half.
3. 03Use "Cannot Say" generously. Verbal reasoning rewards strict reading. If the passage does not say it, the answer is "Cannot Say", not your own inference.
4. 04Skip the impossible ones. Most tests do not penalise wrong answers more than skips. If you cannot see it in 20 seconds, flag and move on.
5. 05Practise the exact format, not a generic stand-in. a multi-section reasoning test has its own rhythm, and a generic reasoning test is not the same. Intervyo's simulation is calibrated to this format, so you rehearse the real thing under real timing rather than a generic aptitude set.