Trading Systems Engineers
Flow TradersAbout the Role
Trading Systems runs the 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. The team also builds and runs the self-service infrastructure platform the rest of Technology depends on.
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.
The role 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. You will take a share of the global 24/7 on-call rotation and cross-skill deliberately between the Linux and cloud sides of the estate.
Requirements
- Strong Terraform experience, including writing, debugging and producing reusable modules for others to consume
- CI/CD experience, ideally GitHub Actions — and the guardrails, not only the pipelines; equivalent GitLab CI or Jenkins experience is fine
- Solid Kubernetes in production across workloads, CNI, Helm and Argo
- Hands-on experience provisioning and operating GCP or AWS through Infrastructure as Code, with an appetite to go deeper
- Strong Linux fundamentals — able to debug a production host without a runbook: processes, networking, storage, systemd, logs, kernel versus user space
- Proficiency in Python or Go, with demonstrable experience of test-driven development
- Direct experience of production on-call and incident response, and a considered view on what makes a rotation sustainable
- Typically 5+ years in infrastructure, platform or systems engineering
- Fluent written and spoken English
- Based in the Amsterdam area or willing to relocate — this role is on-site and is not remote
- Nice to have: a genuine cross-domain background — both Linux/systems and cloud/platform
- Nice to have: GCP specifically, as our primary cloud
- Nice to have: Kafka in production; real Kafka depth would be a significant win
- Nice to have: Puppet for host configuration management at scale, Ansible and AWX, and Foreman
- Nice to have: bare-metal and datacenter infrastructure — provisioning, hardware lifecycle, virtualization (VMware, Proxmox) — and networking depth across routing, load balancing, BGP and multicast
- Nice to have: financial services, trading, or another high-availability, latency-sensitive environment
- Nice to have: Dutch is useful but not required
- Nice to have: self-managed or bare-metal Kubernetes clusters, and contributing to or authoring operators