Optiver Interview Questions
& Process for Software Engineers

Optiver runs two very different interviews under one roof, and the fastest way to waste a month is to prepare for the other one. The timed arithmetic sprint and the market-making game gate the Quant Trader and Researcher track. The Software Engineer loop is a coding-and-systems interview, so confirm your track at the first recruiter contact rather than borrowing a trader's prep. The engineering spine holds across candidate reports: a four-part HackerRank assessment that cuts most of the field, an early behavioural, a systems-heavy technical interview, and a final day where the offer is decided. Optiver lists its open engineering roles on its own careers site.

The center of gravity is not where a big-tech plan expects. Optiver is a market maker where microseconds are money, so the loop is built on low-latency C++, memory, concurrency, and networking rather than exotic algorithms. You do not need a finance background: the firm teaches the trading, and every graduate first spends ten to twelve weeks at the Global Optiver Academy in Amsterdam before joining a team. What the open door hides is a brutal bar. Candidates have scored around ninety percent on the assessment and still been cut, often for headcount reasons, with an eight-month wait before a re-attempt. Because you interview with the team that would hire you, there is no FAANG-style team match afterward, and the whole process runs a few weeks.

Past the assessment the loop turns human, and the behavioural conversation brackets the technical work on both ends. It appears early, right after the assessment, run on the STAR method and framed as two-way, so "why Optiver" comes up before you have written a line of code. Then comes the standalone technical interview, a collaborative session in your strongest language, and finally the final interview day of two technical rounds plus one behavioural, mostly virtual in the US offices. The technical rounds lean harder into C++, memory layout, and performance as they progress, which is the surface a low-latency trading firm actually lives on.

The round to plan around is that final day, because it is where the holistic decision is really made. The interviewers care more about how you reason and how you take a hint than whether you reach a textbook answer, and they expect you to defend a design choice when it is pushed. Systems depth is a gate rather than a tiebreaker: a strong coder who cannot reason about a cache line, a socket, or safe concurrency does not clear the loop, however clean the algorithm was. A ninety-percent assessment is a ticket to the room, not a pass.

Behavioural InterviewEarly STAR

An early conversation, usually right after the assessment, run on the STAR method and explicitly two-way. Motivation, collaboration, and fit, with "why Optiver" the near-universal opener. It is read against the five published values rather than a per-value scorecard, and no finance background is expected.

Technical InterviewC++ + systems

A collaborative working session in your strongest language and the machine underneath it: data structures and complexity, how data sits in memory, computer architecture, networking, concurrency, and low-latency thinking. Deliberately not a LeetCode puzzle hunt, and you are expected to defend your design out loud.

Final Interview DayDecides the offer

Two more technical rounds and one behavioural, back to back, mostly virtual in the US offices. The technical rounds push deeper on C++, memory layout, and performance; the behavioural round revisits fit. A holistic decision follows within about a week.

Optiver's coding problems do not come from a public problem bank. The four-part HackerRank assessment leads with a bespoke object-oriented simulation, and it carries most of the weight and most of the clock, commonly around ninety minutes. You implement a class that ingests a stream of instructions, keeps state as they arrive, and answers queries in order, reskinned across cycles under whimsical themes but built on one shape: an order book that adds, cancels, and matches; a thermal controller tracking cores as load climbs; a subscription engine streaming ordered updates. The visible tests are minimal, so clean modelling and exact spec-reading earn the marks, not a clever one-liner.

The real depth sits one layer down, in the C++ and systems rounds. They press on the C++ cost model, how data sits in memory and how the cache and allocator behave, lock-free versus a single-threaded event loop, false sharing, and the networking a market maker lives on. This is deliberately not a run of LeetCode brainteasers. A candidate who spent every hour on hard graph algorithms and none on how a cache line or a socket behaves has prepared for the wrong interview, so weight the assessment toward modelling and state and the rounds toward low-level C++ and concurrency.

Get the honest version first: Optiver does not run a hyperscale-web design round for software engineers. There is no whiteboard where you shard a feed for a billion users or size a CDN. For graduate and standard software roles design stays small, folded into a technical round as a decision you defend rather than its own stage.

What takes its place is a low-latency systems conversation that grows with level. From the final-day technical rounds upward it becomes a real discussion of how a fast trading system is built: how you would lay out an order book or a matching engine, how data sits in memory and how the cache treats it, where concurrency helps and where it hurts, and how you keep the hot path free of surprises. The one worked design this section builds is a single-symbol matching engine under price-time priority, with price levels as arrays of intrusive lists, an order-id map for O(1) cancels, and a single-threaded event loop that beats locking the book. Determinism and mechanical sympathy carry the weight that raw scale carries elsewhere.

So read the round as latency-first and sharply level-gated. If you are early-career, do not over-invest here at the expense of the assessment and the C++ and systems depth that decide your loop. If you are senior, prepare one clean low-latency design, choosing its data structures by their cost in cache misses and cycles, and be ready to walk the architecture of a fast system you have shipped.

An Optiver offer is a proprietary-trading package, not a tech one, and the shape surprises people coming from big tech. It is a high base plus a large discretionary cash bonus, a share of the firm's trading profits rather than a slice of ownership. There is no stock grant, no four-year vest, and no refresh cycle to model, because Optiver is privately held and grants no equity at any level. The eye-catching new-grad total, around $340K in recent US data, is a base near $215K plus a first-year discretionary bonus near $125K.

Optiver keeps its public engineering titles simple: Graduate Software Engineer, Software Engineer, Senior Software Engineer, with separate hardware, FPGA, and quant tracks alongside and no public Staff or Principal title. Comparison sites normalise the rungs as L3 through L6; read that as an outside mapping, not Optiver's own names. The compensation for each level lives in the offer lesson.

The thing to internalize is that a graduate offer is entry into a structured cohort. Every graduate hire, US and APAC desks included, starts with ten to twelve weeks at the Global Optiver Academy in Amsterdam, which is part of why the graduate base reads as a standardized figure rather than an individually negotiated one. Lateral and experienced hires sit outside the academy track, where the level itself, Software Engineer versus Senior, becomes the thing worth getting right.

With no equity to argue over, the movable surface is narrow. For a new graduate the base is banded and largely set, so the marginal ask moves to a sign-on bonus, the one line with a documented move. For an experienced hire the level you enter at is the larger lever, since the two bands differ. The large annual bonus looks like a lever and is not: it is discretionary and settled against firm and desk performance after you join, so ask how it is structured but do not counter on a figure. Anchor a competing offer to quant and trading peers like Jane Street, Citadel Securities, IMC, or Jump rather than FAANG, because that is the market Optiver prices against.