The Pragmatic Engineer deepdive into Optiver — a 40-year-old Amsterdam prop trading firm with ~950 engineers, 2,200 employees, and €4.5B in trading income — reveals an engineering environment with constraints most tech companies never face. No external customers (the business itself is the only client), nanoseconds as a meaningful performance target, and the ever-present cautionary tale of Knight Capital’s 2012 $440M bug that nearly bankrupted a peer firm.
- Build-and-own culture: engineers own from idea to support; new hires get real production changes day one and are expected to become domain experts within a year
- Three-layer stack: signals (market data, ML pipelines) → strategy (risk-enveloped decisions with automated trade-blocking) → execution (hard separation of concerns — no logic beyond executing the trade)
- Platform engineering at scale: 30-40% of engineers on platform (vs 15-20% typical elsewhere); a globalization push since ~2023 consolidating regionally duplicated systems
- Languages with purpose: C++ for low-latency, Python for modeling (with serious performance forks like optiver-asyncpg), Rust emerging for research tooling, C# for trader GUIs, VHDL/SystemVerilog for FPGAs
- CI/CD on bare metal: custom hardware and custom Linux kernels mean CI needs pre-planned capacity like production; GitHub Actions with a custom observability layer for queue time metrics
- Custom hardware: own FPGAs and ASICs; the retreat system (reprising the options surface after each trade) went from seconds to nanoseconds through stack-level optimization
- AI shift: latency is now the floor, better models are the differentiator; Optiver built an AI gateway and MCP hosting platform where users are both humans and automated agents
An extreme environment where every technical choice is a business choice — and the trade-offs between speed, risk, and reliability are unusually clear. The platform investment ratio alone signals how seriously they take developer experience and consolidation.