← Back to Directory

Optiver interview notes, page 6 of 10

Large Enterprises

Most of these Optiver write-ups come from Software Engineers (69), then Data Scientists (22). The most reported rounds are the technical phone screen (65), the onsite coding round (8), the online assessment (5) and the system design round (5).

91 interview notes · updated Aug 2026

Optiver·Data Scientist·Technical Phone Screen

Jun 2026
Optiver Data Scientist interview had a math/logic puzzle that looked deceptively simple on the surface. One coding question about pile balancing, and it required actually thinking through the structure of the problem rather than just throwing a loop at it.
  • You have two piles of apples with sizes a and b. In each move, you pick one pile as the receiver and double it by moving apples from the other pile (only legal if the giving pile has enough). Can you reach a state where both piles are equal? Return true or false.

“Spent the first few minutes trying to simulate it with a BFS and realized that could blow up badly given the constraint range goes up to 10^9.”

View Post

Optiver·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a Software Engineer role at Optiver and got a calendar arithmetic problem that looked deceptively simple. No date libraries allowed, which is where it gets annoying fast.
  • Given two date strings in YYYY-MM-DD format, compute the absolute number of days between them from scratch. No date or calendar libraries. You need to handle leap years and varying month lengths yourself.

“The leap year rule is where people slip up.”

View Post

Optiver·Software Engineer·Recruiter / HR Screen

Jun 2026
Recruiter screen for a software engineering intern role at Optiver. Skips the usual opener and goes straight into a project deep dive, which honestly threw me a little. The whole thing is basically one long conversation about a single project you choose, so pick carefully.
  • Tell me about a project you've worked on. High level to start, and we'll go from there.
  • What were the hardest parts of that project, and how did you work through them?
  • Looking back, what decisions would you make differently on that project?
  • You mentioned your teammate handled that part. What exactly did you contribute there?
  • How did you know your fix actually worked? What would have happened if you'd missed it?
  • Was there any disagreement on the team about these decisions, and how did it get resolved?
  • Have you actually applied any of those 'things you'd do differently' on a later project?

“The opener sounds easy until you realize every follow-up depends entirely on what you say here.”

View Post

Optiver·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral question from an Optiver software engineer interview. Just the one question about weaknesses, but it had some teeth to it.
  • What is your biggest weakness? Be specific and show what you've actually done to address it.

“The part that trips people up is they want something real, not the 'I care too much' non-answer.”

View Post

Optiver·Software Engineer·Technical Phone Screen

Jun 2026
Quant interview at Optiver with a probability/stochastic processes question. Pretty classic setup but the execution is where things get tricky.
  • Consider a random walk on the interval [a, b]. What is the expected number of steps to reach either boundary?

“I knew the general shape of the answer from having seen gambler's ruin problems before, but the general [a, b] framing made me second-guess my setup.”

View Post

Optiver·Software Engineer·Technical Phone Screen

Jun 2026
Optiver software engineer interview with a concurrency-focused coding problem. The question was about building a thread-safe stock inventory class where sells have to be atomic check-and-deduct operations. Pretty classic for a trading firm but the details matter a lot here.
  • Design and implement a thread-safe StockInventory class that supports concurrent buy and sell operations, where sell is all-or-nothing and the available share count must never go negative.

“The single-threaded version took me about two minutes.”

View Post

Optiver·Software Engineer·Technical Phone Screen

Jun 2026
Optiver software engineer interview with a pretty involved design problem centered around balloon physics and wind simulation. Not your typical LeetCode grind, this one made me actually think about how to model time-dependent state and floating point thresholds cleanly.
  • Design and implement a BalloonFestival class that manages hot-air balloons and wind fields over time. The class must track balloon altitude, compute aggregate wind speed from multiple anchors using a Lorentzian sum formula, determine balloon stability based on wind thresholds and time duration, and return rewarded balloons at inspection time.
  • How would you handle the stability state transitions precisely, including when a balloon changes altitude while already airborne and when wind anchors are added or updated mid-flight?
  • What data structures would you use to support up to roughly one million operations efficiently, targeting near O(log N) per method call for N active balloons or wind anchors?

“This was a full system design plus implementation question, not just a concept sketch.”

View Post

Optiver·Data Scientist·Technical Phone Screen

Jun 2026
Optiver data scientist interview hit me with a pretty deep algorithmic puzzle that I wasn't expecting to go so far into the math. The whole session was basically one extended problem with a lot of follow-up layers.
  • You have an m×n grid of lights where toggling a cell also flips its orthogonal neighbors. Given a starting configuration and a target, find the minimum number of toggles to reach the target, or determine that it's impossible.

“This wrecked me a little because I started thinking BFS and they clearly wanted something more principled.”

View Post

Optiver·Software Engineer·Technical Phone Screen

Jun 2026
Optiver quant engineer interview threw a sequence puzzle at me that looked deceptively simple until I started second-guessing my own arithmetic. Classic Optiver style: short problem, lots of pressure.
  • A sequence is given: 1, 2, 5, 11, 26, 59, ?, 137. Find the missing term by identifying the underlying recurrence relation.

“Stared at it for a bit trying to spot a ratio pattern first, which was a dead end.”

View Post

Optiver·Data Scientist·Technical Phone Screen

Jun 2026
Optiver data science interview had a timed probability question that was genuinely stressful. The 90-second clock made it hard to think clearly, and the extensions they asked for afterward were where things got interesting.
  • An urn has r red, b blue, and g green balls. You draw 3 without replacement. What's the probability of getting at least 2 reds? You have 90 seconds, and they also want a mental-math shortcut that generalizes.

“The 90-second cap is real and they mean it.”

View Post