Optiver software engineer interviews center on a lengthy, multi-part online assessment, followed by recruiter or behavioral, technical, and design rounds covering data structures, OOP/OOD, and systems concepts. Stage counts vary across candidate reports.
$175K
Avg. Base Comp
$390K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Optiver's software engineer interviews are screening-heavy, starting with a long online assessment before most live conversations. Candidates describe OAs of roughly two to four-plus hours, one with seven days to complete, that combine design-style coding with CS fundamentals multiple-choice and logic or aptitude games. Reported coding prompts include a single problem mixing min/max heaps with lazy deletion, Fibonacci sequencing, and hash maps. Others were practical systems such as a checkout notification service and a real-time ticket-matching system. One intern candidate reported that Python was not allowed, so confirm your language options early.
After the assessment, a recruiter or behavioral screen typically covers why Optiver, why software engineering, and how you've handled feedback, conflict, or disagreement with a manager. Technical rounds then mix live coding with low-level and object-oriented work: designing a queue on a circular buffer, answering bit-storage questions, implementing a scheduler in Java or C++, and object-oriented design problems like a shopping or register system. Some live prompts are long and descriptive but reduce to a few lines once understood, so clarify requirements early. Networking concepts and Java OOP also came up in one loop.
A system design or architecture round appears in several reports, sometimes exchange-related and sometimes deliberately vague. One candidate was told three behavioral rounds were needed for an offer, and another faced a later behavioral round that grilled them on past projects, so prepare detailed project stories. Stage counts vary widely across reports.
Synthesized from 60 candidate 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.
I started with an online assessment that was quite lengthy—plan for about three hours total. It included a coding test that was relatively straightforward, some OS-related questions that required solid fundamentals, and a Zap-N test, which honestly felt more like a game than a traditional interview component. The coding part wasn't overly difficult, so I felt reasonably confident after finishing that section.
After the online assessment, I had a quick phone call with a recruiter, followed by a behavioral phone screen. The behavioral round covered pretty standard ground: they asked why I wanted to work at Optiver, how I communicate with colleagues, and about challenging situations I'd faced in past work or group projects. They seemed interested in understanding how I handled conflict and collaboration.
Based on the timeline, I believe there was supposed to be an onsite with additional technical interviews, but I didn't advance past the behavioral phone screen. The whole process felt insightful even though it didn't work out—the online assessment was well-designed and the questions they asked during the behavioral round were fair, just not enough to move forward together.
Prep tip from this candidate
The Zap-N test is a unique component of Optiver's process, so familiarize yourself with what that actually entails beforehand. Also, while the coding section is relatively accessible, the OS-related questions in the online assessment suggest you should review operating systems fundamentals—not just algorithms.
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
Find the maximum profit from at most two stock buy/sell transactions
| Question | |
|---|---|
| Sum to N | |
| Session Difference | |
| Stranded Miner | |
| Hurdles In Data Projects | |
| Priority Queue Using Linked List | |
| 85% vs 82% | |
| Slow SQL Query | |
| Optimistic vs Pessimistic Locking | |
| Ticket Reservation Locking | |
| Gas Station Counting | |
| Minimum Days for Scheduling All Meetings | |
| Client Solution Pushback | |
| Index Fund Return | |
| Ranking Metrics | |
| Processing Large CSV | |
| LRU Cache 1 | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a lengthy OA, roughly 2 to 4+ hours. It mixes data-structure coding, such as min/max heaps with lazy deletion and hash maps, with practical system-style prompts like a checkout notification service or real-time ticket matching. Many also describe separate CS fundamentals multiple-choice sections and logic or aptitude games, and one candidate had seven days to complete it.
A recruiter or phone screen typically covers why Optiver, why software engineering, and how you've handled feedback or disagreement. It sometimes asks you to explain a recent project in nontechnical terms. Later behavioral rounds can probe your resume and past projects more aggressively.
Live rounds combine coding with low-level and object-oriented design, such as a queue on a circular buffer, bit-storage questions, a scheduler in Java or C++, or a shopping/register system. Some prompts are long and descriptive, and interviewers were described as friendly and willing to give hints when you explain your approach.
A design-focused round appears across several reports, including an exchange-related architecture discussion. Some candidates found this stage vague and said it required going with the flow, while others found it relaxed after harder technical rounds. One intern's process ended after a technical interview where system design came up.
One candidate was told three behavioral interviews were needed for an offer, each focused on self-awareness and growth. Another candidate received a rejection within a few days of the final round and described the recruiters as responsive throughout.
