What the firm publishes
DRW's graduate and intern pages describe the programmes and the tracks - trading, quantitative research, and technology - rather than a numbered interview sequence. Its own published account of a quantitative trading analyst's path is the most useful primary reading: it describes the work the interviews are selecting for, which is more actionable than a stage list.
The tracks are genuinely distinct. A trading process and a software engineering process at the same firm test different things, and preparing generically is a poor use of the time.
The stages candidates report
Everything in this section is candidate reporting rather than firm publication, and is hedged accordingly.
Candidates commonly describe an initial quantitative challenge that can be completed remotely, mixing mental arithmetic, probability, and some market-flavoured questions; then a live technical interview weighted toward probability and statistics; then a final on-site stage combining coding, a trading exercise, and back-to-back conversations with people from different desks.
For technology roles the reported emphasis is on C++ and Python and on low-latency systems work, which is consistent with what the firm says publicly about its engineering.
Stage counts and timings shift year to year. Treat any specific number as a guide.
What to prepare
Probability and statistics live, out loud. The reported middle stage is a conversation, not a written test, and thinking audibly is a trainable skill.
Mental arithmetic under mild time pressure. Enough to keep the early screen from being the binding constraint.
Code that compiles and runs. For the technology track, practical fluency beats breadth of theory.
Practise the same formats
The question sets below are ours, written in the formats this process is reported to use. They are not DRW's questions, and nothing here reproduces any part of its assessment.