Optiver Business Analyst interview typically runs 3 rounds: HR, technical interview, case study. The process is fairly drawn-out, with long gaps and little feedback between steps.
$81K
Avg. Base Comp
$157K
Avg. Total Comp
3
Typical Rounds
3-6 weeks
Process Length
We've seen Optiver care less about polished bravado and more about whether a candidate can stay structured under messy, high-detail pressure. In the one candidate experience we have, the first conversation was described as casual and behavioral, but the process quickly escalated into a hard Python problem and then a business case that demanded careful tracking of data and edge conditions. That combination tells us the bar is not just analytical ability; it’s whether you can move cleanly from code to business reasoning without losing the thread.
A recurring theme is that Optiver seems to value issue diagnosis over quick intuition. One candidate was shown a visual representation of breaks in an order and booking system and asked to identify where the failure happened and propose causes and fixes. That’s a strong signal that they want people who can reason through operational problems methodically, especially when the data is incomplete or cluttered. We also noticed the interview felt relaxed and welcoming, which makes the real filter even clearer: they are not trying to rattle you, they are trying to see whether your thinking stays crisp when the problem gets complicated.
The non-obvious make-or-break here is attention to detail. The case was described as the hardest part precisely because it required keeping many data points straight at once, not because it was conceptually exotic. Candidates who do best here are the ones who can explain a path, test assumptions, and keep their analysis grounded in the specifics rather than jumping to a neat answer too early.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Optiver process.
The hardest part for me was the case study round, not the first interview. I went through a fairly drawn-out process for the Business Analyst role at Optiver, and the biggest frustration was how much time passed between each step with very little feedback. The first round was with HR and was mostly behavioral, so it felt pretty straightforward and conversational. They asked things like what drives me to perform, and the tone was casual rather than intense. The second round shifted into a technical interview, and that was a noticeable jump in difficulty because they gave me a hard LeetCode-style problem to solve in Python. It was the kind of question where you need to stay organized and explain your thinking clearly while coding, not just get to the answer quickly.
The final round was a case study and felt the most business-relevant, but also the most complicated. I remember there being a lot of data detail to keep track of, and the problem required careful attention rather than a quick instinctive answer. Another part of the process was very visual: they showed a representation of breaks in their order and booking system and asked me to walk through where the break occurred and suggest possible causes and solutions. That round was more about issue resolution and structured thinking than pure technical depth. The overall vibe was actually pretty relaxed, and when I came onsite they made a point of showing off the office and culture. The dress code was business casual, and they seemed to want candidates to feel comfortable and welcome instead of grilled. I didn’t get an offer in the end, but the main takeaway is to be ready for a long process, a genuinely hard coding round in Python, and a case interview that rewards careful analysis of messy details.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Optiver
Write a function compute_deviation that returns the standard deviation of each list in a list of dictionaries
| Question | |
|---|---|
| Experiment Validity | |
| Session Difference | |
| Network Experiment Design | |
| Slow SQL Query | |
| Addressing Data Quality Issues | |
| New UI Effect | |
| Interquartile Distance | |
| Minimum Days for Scheduling All Meetings | |
| Client Solution Pushback | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Cumulative Distribution | |
| Bagging vs Boosting | |
| Comments Histogram | |
| 500 Cards | |
| Employee Salaries | |
| Closest SAT Scores | |
| Button AB Test | |
| Top Three Salaries | |
| Subscription Overlap | |
| Paired Products | |
| P-value to a Layman | |
| Monthly Customer Report | |
| Hurdles In Data Projects | |
| Slacking Employees Salaries | |
| Top 3 Users |
Synthesized from candidate reports. Individual experiences may vary.
The first round is with HR and is mostly behavioral and conversational. Candidates are asked about motivation and what drives them to perform, with a relaxed tone rather than an intense interview style.
This round shifts into a technical coding interview, where candidates solve a hard LeetCode-style problem in Python. The focus is on staying organized, explaining your thinking clearly, and coding through the problem methodically.
The final round is a business-focused case study with a lot of data detail to track carefully. Candidates may also be shown a visual representation of breaks in an order and booking system and asked to identify where the break occurred, suggest causes, and propose solutions.