How Optiver Interviews in 2026: Process, Questions & What They Score

• Timed arithmetic drills in the '80 in 8' format: rapid-fire addition, subtraction, multiplication, division, percentage, and fraction problems with no calculator and only seconds per question.
• Quick percentage/fraction conversions performed verbally on the spot during live interviews (e.g., 'what's 17/34 as a percent, fast').
• Separately, sequence/pattern-recognition problems (the 'NumberLogic'-style test): given a series of numbers, identify the pattern and predict the next value under time pressure.
• On-the-spot mental math embedded inside a market-making exercise: recalculating fair value quickly as new information (e.g., a revealed card) changes the picture.

• Timed probability/expected-value questions in the 'Beat the Odds' format, often multiple choice with approximate answer bands rather than exact values.
• Dice and coin-flip probability problems (e.g., expected number of rolls to see a specific outcome, or probability of a compound event).
• Conditional probability and Bayesian-updating problems (updating a belief about a hidden quantity as partial information is revealed).
• Classic brainteasers commonly used across quant-trading interviews generally (Monty Hall variants, gambler's-ruin style problems, simple martingale setups). These are standard prep material rather than confirmed Optiver-original questions, so treat them as good practice, not guaranteed prompts.
• 'I'm thinking of a number between 1 and 100: make me a market on it' style prompts requiring a stated bid/ask spread and justification.

• Quote a two-sided market (bid and ask) on a hidden quantity such as the sum of several face-down cards, then adjust prices as the interviewer trades against you and more cards are revealed.
• Make markets on constructed payoffs such as the median of three dice, the number of red marbles in an urn, or the value of a simple synthetic derivative, while interviewers or other candidates trade against your quotes.
• Live group trading-game rounds during the final 'Optiver Day,' where multiple candidates simultaneously quote and trade against each other while being observed for composure and adjustment speed.
• Follow-up discussion questions probing why you set a particular spread, and how/why you would move your price after a trade fills.

• LeetCode-style data-structure and algorithm problems (easy to medium/hard), with recurring emphasis reported on heaps, queues, and circular-buffer-style structures relevant to low-latency systems.
• Object-oriented design problems, e.g., designing a simplified shopping/register system or a task scheduler.
• Lower-level topics: bit manipulation, basic networking concepts, memory management, and concurrency reasoning.
• System-design style prompts for more experienced candidates, e.g., designing a market-data feed system that ingests and processes real-time prices, expected to touch on data processing, notification/API layers, and storage.
• General 'how do you think about tradeoffs' follow-ups (e.g., choosing data structures for latency-sensitive code). Optiver's own SWE interview-tips page states it wants to see how you break down complexity and reason out loud, not whether you already know a memorized trick.

• Tell me about a time you were confident and wrong. (Widely and consistently reported by candidates and prep sources as a recurring Optiver question, used to probe whether you 'tilt' after a mistake or reset and refocus; this framing comes from third-party interview-prep analysis of candidate reports, not an official Optiver statement.)
• Why trading (or this specific track: trading vs. quant research vs. engineering) rather than another path?
• Describe a high-pressure situation you faced and how you handled it.
• Tell me about your biggest professional (or academic) failure and what you took from it.
• Tell me about a time you had to learn or master something completely new very quickly.
• Describe a time you had to adapt your approach based on new information mid-project.
• Tell me about a time you worked as part of a team toward a shared goal. What was your specific contribution?

Optiver's process has 6 stages, in order: Application & resume/cover letter screen, Online assessment(s), Recruiter/HR behavioral screen, Technical/case interview(s), Final round / 'Optiver Day' (onsite or virtual onsite), Decision / offer.

Optiver evaluates candidates against No publicly documented named framework (e.g., no Amazon-style 'leadership principles' list): Numbers-oriented mindset / pattern-finding under complexity: confirmed on Optiver's own 'What does Optiver value' careers page, which describes seeking 'people who find patterns in complexity, challenge what they see and use numbers as a common language for better decisions', Problem-solving in one of the 'most complex and competitive' market environments: also from Optiver's own careers-culture page, Continuous professional development / growth orientation: reflected in Optiver's careers-page material on its Global Optiver Academy, structured onboarding, and mentorship model, Collaboration, transparency, and intellectual curiosity: an exact phrase used on Optiver's own software-engineer interview-tips page, Composure under pressure and sound decision-making with incomplete information: a recurring theme across multiple independent prep sources and candidate reports, not language found in an official Optiver document.

Optiver's question bank spans 5 categories: Mental math & speed arithmetic; Probability, expected value & brainteasers; Market-making & trading simulations; Software engineering: coding & CS fundamentals (for SWE-track candidates); Behavioral & motivational fit.

This playbook is medium confidence, compiled from 26 public sources, and last verified July 7, 2026. It describes one well-documented shape of Optiver's interviews, not a guarantee of what any individual loop will look like.