Chicago
Chicago
Chicago is Optiver’s US headquarters and the center of our US options business and technology team. Based in one of the world’s leading derivatives markets, teams here build and run the systems that provide liquidity across the US markets.
Building the systems that turn ideas into trades
Automated trading systems
Chicago
“Over the past seven years, I’ve seen the team evolve into something really advanced. We’re building models that learn from huge streams of market data and make decisions at ultra-low latency.”
“Here, it’s not just about implementing something. You’re expected to think about the bigger picture and what actually makes sense to build.”
“Working with driven, curious, and highly competent people has been a big part of the experience. On a daily basis, I’m interacting with quant researchers and devs, all contributing toward a common goal.”
Inside our Chicago office
Supporting the local community
Teams in the Chicago office support the local community through intentional giving and volunteer initiatives focusing on youth development, sustainability and STEM education.
Long-term partnerships and initiatives
These efforts have grown into long-term partnerships and initiatives, including Urban Initiatives, Mercy Home, The Grace Network, the Homewood Science Center, and the Aesha Jackson STEAM Leader Award Scholarship.
Category Manager, Software
Chicago
ExperiencedTechnologyExperiencedTechnologyData Operations Engineer
Chicago
ExperiencedTechnologyExperiencedTechnologyRisk Analyst
Chicago
ExperiencedRisk, Finance & LegalExperiencedRisk, Finance & Legal
Latest in technology
Large language models and alternative data often dominate conversations about deep learning in trading. At high-frequency horizons, Karun Rao looks instead at the order book, where models learn from noisy, event-based market data whose structure is hard to capture by hand.
A conversation with NVIDIA on how accelerated computing is changing research and engineering in trading.
Optiver’s software engineering function was profiled by The Pragmatic Engineer, a leading technology publication on Substack.
Latency and research iteration pull in different directions. Software engineer Daniel B. explores how three generations of trading systems evolved to balance both.
For the past several years, the AI conversation has largely centered on models: which are the most capable, which will dominate and how quickly they will improve.
Engineering the Agentic SDLC
Instead of throwing agents into an SDLC that wasn’t built with them in mind, we’re trying to do something different: design the development lifecycle around them from the ground up. Below is an example of how we shrank a block of work we take on when we connect to a new exchange. Over the last few months, we've been running an experiment. If you take agentic coding seriously, what does it look like?
