Infrastructure-as-Code for Latency-Critical Bare Metal Systems

Infrastructure

Leanne Fok is a Senior Infrastructure Engineer in Amsterdam with 15+ years at Optiver. She previously led the Infrastructure Platform team responsible for our internal Infrastructure-as-Code stack and is now leading the Infrastructure Kubernetes project.

Infrastructure-as-Code is straightforward in the cloud. But what about on bare metal?

In her PyLadies talk, “Infrastructure-as-Code in a Latency-Critical Bare Metal World,” Senior Infrastructure Engineer Leanne Fok shares how we brought declarative IaC principles to physical, latency-sensitive trading infrastructure where nanoseconds matter and every cable is intentional.

Managing thousands of bare metal servers across global data centers introduces a different class of problems. There is no managed control plane. No provider APIs to rely on. Just hardware, strict performance constraints, and very little tolerance for configuration drift.

So how do you:

  • Define infrastructure intent clearly enough to automate it
  • Enforce standards across physical devices, ports, power, and networking
  • Detect when real-world state quietly diverges from what you declared
  • Build trust in automation while migrating from legacy processes

In this talk, Leanne walks through the architectural patterns we adopted, including declarative intent modeling, reconciliation loops, truth collectors, and a custom Terraform provider that translates infrastructure definitions into enforceable standards.

Watch the full 15-minute talk

Interested in latency-critical systems?

Explore open engineering roles and learn more about the infrastructure challenges behind them.

Related articles

View all

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

AI Engineering

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?