Find jobs that fit your situation.

Infrastructure Platform Engineer runs the trading system infrastructure Flow Traders trades on: the global Linux fleet — trading servers, workstations and VDIs — and the multi-cloud and distributed-systems estate that sits alongside it. We also build and run the self-service infrastructure platform the rest of Technology depends on.

We are hiring two engineers into this team. This is a hands-on engineering role: most of your time goes on writing Terraform, building CI workflows and guardrails, automating toil out of the Linux fleet, and operating what you build. A lot of the shared tooling does not exist yet, and building it is the job rather than a side effect of it. The environment is trading-critical and runs across both on-premise infrastructure and public cloud, and you will work on both sides of that line rather than specialising in one.

To be clear about the shape of the seat: this is build-and-operate rather than architecture, strategy or management. There is architecture in it, but the bulk of the work is hands-on and there are no direct reports. A solid Linux foundation is essential across the whole role — it underpins both sides of the estate, and the cloud, container and Kubernetes work rests on it just as much as the on-premise fleet does.

• Write, debug and publish reusable Terraform modules that other engineers consume, covering both the Linux fleet and the cloud estate.
• Design and own CI/CD workflows and guardrails in GitHub Actions — the policy checks, tests and approval gates that let engineers across Technology self-serve infrastructure safely.
• Build and operate Kubernetes on both sides of the estate — managed clusters in cloud and k3s on-premise — along with the distributed systems running on it, particularly Kafka.
• Provision and operate GCP, AWS and Alibaba Cloud resources through Infrastructure as Code.
• Operate and automate the Linux estate: Foreman provisioning across VMs and bare metal, Puppet for host configuration, Ansible/AWX for application deployment, plus patching and lifecycle.
• Build automation and internal tooling in Python or Go, with test-driven development as a normal working habit.
• Take a share of the global 24/7 on-call rotation, and cross-skill deliberately between the Linux and cloud sides of the estate.

• A genuine cross-domain background — both Linux/systems and cloud/platform, rather than one of them plus a passing acquaintance with the other.
• GCP specifically, as our primary cloud.
• Kafka in production. Real Kafka depth would be a significant win for us.
• Our fleet tooling: Puppet for host configuration management at scale, Ansible and AWX, and Foreman.
• Bare-metal and datacenter infrastructure — provisioning, hardware lifecycle, virtualization (VMware, Proxmox) — and networking depth across routing, load balancing, BGP and multicast.
• Financial services, trading, or another high-availability, latency-sensitive environment. Dutch is useful but not required.