A boutique high frequency trading firm in London is hiring an Infrastructure Automation Engineer.
You'll own their in-house tool that builds and manages their Linux servers. Most of the estate is bare metal, not cloud. The job is to automate the manual work across the estate: server builds, patching, secrets/credentials, networking, releases and monitoring.
No finance or trading experience needed. They care that you can write Python and run Linux.
Responsibilities:
- Own and build on their in-house Linux provisioning tool. It's written in Python.
- Automate patching, OS updates and secrets/credentials across the estate.
- Move network and firewall config into Git, with peer review on changes.
- Improve the build and release process.
- Automate repeatable Windows machine builds.
- Help automate a small cloud setup across Microsoft 365 / Entra and AWS.
- Improve monitoring and alerting so problems are caught early.
Requirements:
- 5+ years' experience in infrastructure, platform, DevOps, SRE or Linux systems engineering.
- Strong Python. It's what their automation is written in, and you'll write a lot of it.
- Proper hands-on Linux administration. You understand how it works underneath.
- A track record of automating infrastructure at scale: repeatable and under version control.
- You treat config as code and ship changes through Git and pull requests.
- Some exposure to bare-metal, on-prem, colocation, hosting, HPC, telecoms or similar infrastructure.
- Some understanding of networking: VLANs, routing, firewalls, switches.
- Senior enough to own systems and make your own calls.
Useful experience:
- Ansible, Salt, Puppet, Chef or Terraform.
- Vault, OpenBao or other secrets-management tools.
- PXE, Kickstart, Foreman, MAAS or similar provisioning tools.
- ESXi or other virtualisation.
- Prometheus, Grafana, PRTG or similar monitoring tools.
- Windows automation, Active Directory or image-based builds.
- An opinion on how this should be done, for example whether to move to immutable, image-based OS builds.
Working model:
- Office-based in London, 5 days a week.
- The odd out-of-hours change when something big needs scheduling.
- No on call. That is covered by the wider infrastructure team.
Why join:
- You'll work on a real, mostly bare-metal estate rather than a cloud-only platform.
- You'll build automation rather than just work through tickets.
- Small team. Everyone can see and work on the code.
- They want someone with opinions on how the estate should be automated.
- Finance experience is not required. Relevant infrastructure experience matters more.