Old Mission Capital Psychometric Tests Prep

• Core-skills practice. Numerical, verbal and logical reasoning at graduate level: the skills under Old Mission Capital'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

   Severe time mismanagement

   Freezing on difficult arithmetic questions instead of skipping and returning later.

2. 2

   Mental math fatigue

   Making basic multiplication or addition errors due to rushing under pressure.

3. 3

   Misinterpreting probability payoffs

   Failing to distinguish between gross payouts and net expected value.

4. 4

   Lack of platform familiarity

   Wasting precious seconds navigating custom input boxes or on-screen calculators.

5. 5

   Ignoring edge cases in coding

   Submitting code that passes basic tests but fails on boundary conditions.

6. 6

   Inadequate scratchpad organization

   Failing to keep notes clean, leading to transcription errors during multi-step calculations.

• Practising mental math daily

  Using apps or custom scripts to build instantaneous recall of multiplication tables, squares up to 30, and fraction-to-decimal conversions.

• Time-budgeting ruthlessly

  Allocating a strict maximum time per question and moving on instantly if stuck.

• Mastering expected value shortcuts

  Recognizing symmetrical probability distributions to calculate outcomes without writing out full tables.

• Simulating real test conditions

  Practising timed arithmetic tests in a quiet room with zero outside aids to build physical stamina.

• Writing clean boilerplate code

  Setting up fast input/output templates for coding assessments to save seconds during technical rounds.

• Calibrating risk appetite

  Understanding how to balance speed and accuracy without guessing blindly on negative-ev questions.

• Probability study

  Review fundamental probability texts, card counting drills, and expected value exercises commonly found in proprietary trading preparation guides.

• Coding preparation

  Solve medium-difficulty problems on platforms like LeetCode, focusing on clean code implementation in C++ or Python within strict 30-minute time caps.

• Time investment

  Candidate reports suggest successful applicants typically invest 20 to 40 hours of targeted practice before taking the assessment.

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.