Cognitive ability assessment
12 questions · 10 minutes (about 50 seconds per question)
What it tests. Processing speed and accuracy across data interpretation, verbal inference and abstract patterns.
Worked example. Compute the percentage change in combined divisional revenue between two quarters; on a verbal syllogism where only 'some' institutions face higher costs, infer 'Cannot Say' for Barclays specifically; complete a 3x3 inductive matrix with two simultaneous rules.
Common traps. Spending over two minutes on one puzzle, and leaving questions blank (heavily penalised in a 12-question test).
How to handle it. Keep a physical calculator and scratchpad, jot only the needed variables, and guess and move on after about 40 seconds on a hard item.
Personality questionnaire (OPQ32)
30-40 blocks · Untimed (about 15-20 minutes)
What it tests. Typical working style, leadership potential, risk tolerance and collaboration style.
Worked example. From statements on solving problems independently, building consensus, or working under changing priorities, rank Most and Least like you, then resolve the remaining two.
Common traps. Gaming an 'ideal banker' profile (the system cross-checks consistency and flags contradictions) or marking every extreme statement.
How to handle it. Answer honestly in a professional context, keep consistent across blocks and trust your first instinct.
Mindset / situational judgement
About 18-20 scenarios · Untimed (about 20 minutes)
What it tests. Decision-making aligned with the RISE values.
Worked example. Asked to drop a 5pm client credit review for a director's pitch-data request, the best option acknowledges the request, explains the active deadline and proposes a specific time straight after; on a data error a colleague made, correcting it and informing the team beats leaving it or escalating over their head.
Common traps. Prioritising revenue or speed over compliance, and passively escalating routine problems.
How to handle it. View each scenario as a risk-aware, collaborative professional; avoid extremes and choose balanced, process-respecting options.
Technical coding (Expert / Developer tracks)
2-3 coding challenges plus 3-5 design questions · 60-90 minutes
What it tests. Data structures, algorithm optimisation and runtime complexity (O(N) vs O(N squared)).
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. Failing 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 time limit before submitting.