Skip to content

How quant probability interviews work

By the Mockich team · Updated · 6 sources

Probability and mental math rounds are a gate for trader roles and appear lightly in some quant developer loops: short problems on expected value, conditional probability and combinatorics, worked out loud against the clock, and in trader finals a market-making game. The guides we read agree that structure, sanity checks and calm under pushback count as much as the final number.

Key points

  • Reason out loud from the first second. An answer with no reasoning, or silence until you are certain, are both reported failures.
  • Look for symmetry, linearity of expectation or working backward before a long calculation.
  • Check the answer on a small case before you commit to it.
  • Hold a correct answer with reasons when challenged; fix a wrong one quickly.
  • Know which track you are preparing for: developer loops are mostly C++ and systems.

Who gets these rounds

For trader and hybrid roles, probability and mental math are core rounds. For quant developers the guides disagree: one says mental math and market making do not appear in developer interviews, another reports light probability at some firms’ developer loops. Both agree that for developers it is secondary to C++, concurrency and low-latency design.

Sources: [1], [2], [3], [5]

The usual formats

FormatTypical timeWhat happens
Arithmetic testAbout 8 minSixty to eighty quick arithmetic items (reported by one guide for trader tracks).
Probability interview30 to 60 minExpected value, conditional probability and combinatorics, worked out loud.
Market-making gameFinals, variesQuote a bid and an ask on an unknown quantity while the interviewer trades against you.
Developer loopsA short puzzle, if anyAt some firms one probability question inside another round.

Sources: [2], [3], [4], [5]

What interviewers look for

No firm publishes its rubric. The guides describe the same signals:

  • Structure: symmetry, working backward and linearity of expectation instead of brute force.
  • Sanity checks: a small case, a bound, or an extreme value that the answer must fit.
  • Speed: comfortable estimating and approximating under time pressure.
  • Links to trading: price against variance and bet size, and recognizing when there is no edge.
  • In market making: quotes that move after each trade, a spread that reflects uncertainty, awareness of inventory and sizing.
  • Composure: holding a correct answer with reasons, and revising a wrong one quickly.

Sources: [3], [4], [5]

The question themes that come up most

  • Expected value, including games and fair prices.
  • Conditional probability and Bayes’ rule.
  • Combinatorics and counting.
  • Random walks and martingales.
  • Betting and sizing.
  • Estimation of an unknown quantity.
  • Market making: quoting an unknown value and updating after trades.

Sources: [5], [6]

The mistakes guides report most

  • Using a complicated rule where symmetry gives the answer.
  • Giving an answer with no reasoning, or going silent until certain.
  • Folding under pushback, or refusing to reconsider a wrong answer.
  • In market making: not adjusting after trades, refusing to trade, or intervals that are too narrow.
  • Preparing for the wrong track: trader drills for a developer loop, or the reverse.

Sources: [2], [3], [4], [5]

How the interviewer behaves

One detailed source reports that interviewers argue against right and wrong answers alike, interject quick arithmetic and change the problem halfway through. In market-making games the interviewer’s trades carry information you are expected to use. Treat this as plausible rather than settled: it comes mostly from one publisher.

Sources: [4], [5]

How the bar changes with level

Sources on levels are thin. Where probability is asked of experienced candidates, the bar moves from correct answers with structure to linking the results to pricing, risk and position size.

Sources: [3], [6]

Go deeper on this round

Practise the round out loud

Mockich’s probability round runs 30 min: five short problems on expected value, combinatorics, conditional probability, estimation and market making, reasoned out loud. Once you answer, Vera asks you to sanity-check it or extends the problem once, and gives at most two small nudges. Market-making questions are asked like the others; there is no live trading game. The report scores correctness, structured reasoning, speed and estimation, communication (plus market intuition at lead) and quotes what you said.

Sources

We read these public guides on 2026-10-30 and summarised where they agree, in our own words. Sources 1, 4 and 5 come from one publisher and count as one voice. They report typical practice; no firm publishes its rubric, and firm-specific claims in them are not verified.

  1. [1] techinterview.org, The quant developer interview loop, round by round
  2. [2] TraderMath, The Quant Developer Interview Guide
  3. [3] Aced, Quant Developer Interview Questions and Prep (2026 Guide)
  4. [4] techinterview.org, Mental math drills for trading interviews
  5. [5] techinterview.org, What quant trading is and how the interview actually works
  6. [6] quantt.co.uk, Quant developer interview questions