DEV Community

Cover image for Optiver OA Experience | 90min Coding + Probability + Logic + Game Test Breakdown
interview-aid-Etesis Elay
interview-aid-Etesis Elay

Posted on

Optiver OA Experience | 90min Coding + Probability + Logic + Game Test Breakdown

Just finished the Optiver Online Assessment, and the best way to describe it is simple: it’s not about difficulty alone — it’s about endurance under sustained pressure.

The entire assessment takes around 3 hours, but what stands out is the intensity. There is almost no breathing room between sections, and every part is designed to test how consistently you can perform under time constraints. For anyone new to quant or trading firm interviews, the experience can feel like a shock in terms of pace and density.

OA Structure Overview

The Optiver OA is composed of four major components:

  • Quantitative Coding (90 minutes)
  • Beat the Odds (Probability Test)
  • Number Logic Test
  • Zap-N Game Test

Each section evaluates a different dimension — from algorithmic thinking to probability intuition and cognitive speed.

1. Quantitative Coding (90 min)

This section includes two coding problems. The difficulty is around Medium to Medium+, but the real challenge lies in modeling real trading scenarios rather than solving abstract algorithm puzzles.

Problem 1: Worst Trade Reporter

The task involves processing trade data and computing profit and loss (PnL). Each record contains fields such as trade type, instrument, buy/sell indicator, price, and volume.

The core logic revolves around:

  • Data aggregation
  • State maintenance across trades
  • Hash map / grouping logic
  • Edge case handling for incomplete or overlapping trades

This is less about algorithms and more about correctly simulating a financial data pipeline.

Problem 2: Order Book Matching Engine

This problem simulates a simplified trading engine. You need to match buy and sell orders based on price constraints:

  • Buy orders match with the lowest sell price ≤ P
  • Sell orders match with the highest buy price ≥ P
  • Matched orders are removed from the order book
  • Track total transaction value from all executed trades

A typical approach involves using:

  • Min-heap for sell orders
  • Max-heap for buy orders

However, the real difficulty is not the data structure — it’s handling cascading matches, repeated executions, and maintaining consistency when orders continuously interact.

2. Beat the Odds (Probability Test)

This section contains 30 questions, each with a strict 90-second time limit and no ability to revisit previous questions.

The focus is heavily on core probability concepts:

  • Conditional probability
  • Bayes’ theorem
  • Expected value
  • Permutations and combinations
  • Independence vs dependence

The main challenge here is not conceptual difficulty, but time pressure. Many questions are solvable, but there is simply not enough time to deeply analyze each one.

3. Number Logic Test

This section lasts about 25 minutes and contains around 26 sequence-based questions.

The patterns typically involve:

  • Arithmetic and geometric sequences
  • Pattern transformations
  • Multi-step logical deductions
  • Rapid pattern recognition

The pace is intense — averaging less than one minute per question. By the later part of the test, it becomes more about instinctive recognition than deliberate reasoning.

4. Zap-N Game Test

This section consists of 9 mini cognitive games covering memory, reaction, and attention control.

It is less about “playing well” and more about maintaining consistency under stress:

  • Reaction speed
  • Working memory capacity
  • Attention switching ability
  • Performance stability under pressure

Key Takeaways

1. Coding is only one part of the evaluation

Unlike traditional SWE interviews, coding is just one component. The problems are business-oriented and require strong modeling ability rather than pure algorithmic tricks.

2. Math and logic carry significant weight

Probability and number logic sections are critical filters. Many candidates underestimate how important these are compared to coding.

3. Time pressure is the real filter

Across all sections, the defining factor is not difficulty but speed. The OA is designed to test sustained accuracy under continuous time constraints.

Preparation Tips

If you're preparing for Optiver or similar firms like Jane Street or IMC, focus on the following areas:

  • Master probability fundamentals (Bayes, conditional probability, expected value)
  • Practice trading-style coding problems (order books, transaction systems)
  • Improve mental math speed and accuracy
  • Train sequence and pattern recognition under time pressure
  • Simulate full-length timed assessments regularly

Final Thoughts

The biggest takeaway from the Optiver OA is this: it’s not about solving a single hard problem — it’s about maintaining accuracy and composure under sustained cognitive pressure.

Many candidates can handle coding problems individually, but performance often drops when probability, logic, and fatigue accumulate across multiple sections.

If You Are Preparing for Quant / Big Tech OA

If you are targeting companies like Optiver, Jane Street, IMC, DRW, or other trading firms, the key gap is usually not knowledge — but exposure to real assessment conditions.

Most candidates struggle because they have not experienced:

  • Full-length OA simulation under strict timing
  • Probability and mental math under pressure
  • Continuous multi-module fatigue management

Structured preparation and realistic simulation can significantly improve stability on test day.

Interview Aid focuses on North America tech and quant interview preparation, including OA simulation, mock interviews, and full interview strategy design. Many candidates use structured practice sessions before their actual OA to replicate real testing pressure and stabilize performance.

You can learn more here: Interview Aid Services

Hope this breakdown helps anyone preparing for Optiver OA. Good luck and stay consistent under pressure.

Top comments (0)