Interview practice
Optiver-style quant developer coding practice
A global market maker headquartered in Amsterdam, trading options, ETFs and futures on major exchanges.
What this assessment looks like
Timed coding screens (HackerRank/CodeSignal style) plus systems questions that separate quant-dev interviews from generic software ones: order-book mechanics, concurrency bugs, and complexity under real constraints.
- Reading concurrent code and pointing at the defective line
- Order-book data structures: what happens on a cross, a cancel, a partial fill
- Algorithmic complexity chosen for the input sizes actually stated
- Monte Carlo methods and when a simulation beats a closed form
Train it here
- Concurrency Clash - Find the data race, name the fix - real C++ defect patterns, five levels.
- Order Book - Matching-engine mechanics: crosses, cancels and partial fills.
- Algorithm Lab - DP tables, Monte Carlo estimation and speed rounds at four difficulty tiers.
Also reported at Optiver
80-in-8 mental math · Number sequences · Probability & estimation · Market making
Outcry is not affiliated with Optiver and has no access to their assessment content. This page describes formats candidates publicly report, and the drills here train the underlying skills - they are not the firm’s questions.