Situational Judgment Test (SJT)
24 scenarios · Untimed (recommended 20-25 minutes)
What it tests. Decision-making aligned with the six values: Integrity, Sustainable Performance, Client Centricity, Innovation, Discipline and Partnership.
Worked example. Asked to choose between an Associate's pitchbook data and a VP's valuation update both due tomorrow, the best option maps both tasks, communicates the conflict and aligns an explicit priority; the worst accepts both silently and delivers two unverified drafts.
Common traps. The escalation trap (taking a minor problem straight to an MD), the lone-wolf strategy (silently absorbing the work) and splitting the difference without solving the problem.
How to handle it. View every scenario as a risk-aware, collaborative professional; prioritise client interests, transparent communication and team collaboration over individual effort.
Numerical reasoning (Verify Interactive)
About 8-10 questions · Part of a combined 36-minute G+ block (about 90 seconds per question)
What it tests. Interpreting quantitative data and computing percentages, growth, ratios and currency conversions under time pressure.
Worked example. Given quarterly divisional revenues, if Americas falls 15% (600 to 510) and EMEA rises 12% (450 to 504) while APAC and LATAM stay at 300 and 150, set the combined projection slider to 1,464.
Common traps. Visual overload on multi-variable charts, input-precision errors on sliders, and confusing millions with thousands on an axis.
How to handle it. Keep a calculator and scratchpad, read the units, legends and axes first, estimate before fine-tuning the slider and match the platform's required units exactly.
Inductive reasoning (Verify Interactive)
About 7-8 questions · Part of the combined 36-minute G+ block
What it tests. Abstract problem-solving and pattern recognition: deriving rules from non-verbal data and predicting the next step.
Worked example. Across three blocks black triangles fall 3, 2, 1; white circles rise 2, 4, 6; the connecting line rotates 0, 45, 90 degrees. Block 4 is 0 triangles, 8 circles, line at 135 degrees.
Common traps. The single-rule trap (tracking rotation but missing colour or border changes), the time sink and clicking randomly without tracking how actions change the sequence.
How to handle it. Break each pattern into individual variables (orientation, shading, count, position) on scratch paper, isolate each rule, then combine them to build the missing block.
Deductive reasoning (Verify Interactive)
About 7-8 questions · Part of the combined 36-minute G+ block
What it tests. Applying a set of rules to reach a specific conclusion and drawing accurate inferences from complex parameters.
Worked example. With M&A Update immediately before Risk Review, Capital Allocation neither first nor last, and Compliance after Risk Review across four hours, the only valid grid is 09:00 M&A, 10:00 Capital Allocation, 11:00 Risk Review, 12:00 Compliance.
Common traps. Solving entirely in your head, and not locking absolute positions first before mapping relative constraints.
How to handle it. Sketch a matrix or grid, lock any absolute positions, map the relative connections and eliminate impossible combinations until the sequence resolves.
Personality questionnaire (OPQ32)
About 104 trait blocks · Untimed (about 30-45 minutes)
What it tests. Behavioural profile across relationships with people, thinking styles and feelings/emotions: data focus, resilience, compliance and competitiveness.
Worked example. From statements on taking charge in a crisis, double-checking data accuracy or maintaining group harmony, mark one Most and one Least like you per block.
Common traps. The 'perfect candidate' fallacy (contradictions trip the consistency check), extreme polarisation and overthinking individual statements.
How to handle it. Answer honestly in a professional frame, keep consistent across the 104 blocks, prioritise work ethic and analytical focus, and trust your first instinct.
Technical coding (Expert / Quant tracks)
2-3 coding challenges plus design questions · 60-90 minutes
What it tests. Data structures, algorithm optimisation and runtime complexity.
Worked example. Given an array of daily stock prices, write an O(N) single-pass function to find the maximum single buy-then-sell profit, tracking the minimum price seen so far.
Common traps. Missing edge cases (empty inputs, all-decreasing arrays) and over-engineering when a clean array or hash-map approach passes.
How to handle it. Read the constraints, write pseudo-code first, handle edge cases and verify the loops run within the limit before submitting.