Quant Developer
The round for the people who turn research into something that runs — correctly, fast enough, and the same way twice. It is a coding interview in the sense that it is about algorithms, data structures and the language you would actually write, but half of it is the machine: cache lines, floating point, allocation, threads and where the tail latency comes from. Expect to be asked why the asymptotically better structure lost, and expect the follow-up to be a number rather than an opinion.
Before you start
- 20 questions in 45 minutes. The clock does not stop.
- No hints, no worked examples, no indication of difficulty.
- You are never told whether an answer was right — not after a question, not at the halfway mark.
- A good answer sometimes draws a follow-up, exactly as it would in the room.
- You may leave a question blank and move on. Blank scores the same as wrong, and costs less time.
- Nothing here asks you to write code. It asks the questions an interviewer asks about the code you wrote.
- Everything — scores, mistakes, the correct answers, and what to study — arrives in the debrief.
What it covers
20 questions drawn across 8 subjects. You are never told which subject a question belongs to, or how hard it is meant to be — the debrief scores each one separately.
The clock starts when you press Begin on the next page, and it does not stop. Set aside 45 uninterrupted minutes.