Linux DevOps Engineer

**Cloud \& DevOps Engineer \- Linux** **Overview** 🏢 **Company** \| Trading Technology, Capital Markets Infrastructure, Market Data 👤 **Position** \| Cloud \& DevOps Engineer 🎯 **Impact** \| Linux Engineering, Automation, Platform Reliability 📏 **Size** \| Lean engineering team inside a regulated financial markets business 🌟 **Skills** \| Linux, Terraform, Kubernetes, CI/CD, AWS, Python 📍 **Location** \| London or Paris 💻 **Hybrid** \| 2 days a week in the office. 💰 **Offer** \| Up to £125,000 \+ bonus 💎 **Benefits** \| Private medical, enhanced parental policies, pension, flexible working hours, life assurance, critical illness cover, electric car scheme, and long\-term progression inside a business scaling heavily post\-acquisition. **The Role** A lot of DevOps environments are becoming overly specialised. One person owns pipelines. Another owns cloud. Another owns Linux. Another owns containers. Then something breaks and nobody fully understands the entire system. This team is trying to avoid that. You’ll join a small engineering group supporting high\-performance trading infrastructure where Linux fundamentals still matter just as much as cloud automation. That’s important because the environment is changing fast. Some workloads are moving further into Kubernetes and OpenShift. Other systems are moving back towards on\-prem infrastructure as the economics of cloud get challenged. At the same time, the business is growing aggressively, integrating into a larger international group, onboarding new clients, and hardening infrastructure across security, resilience, and scalability. So this isn’t a “manage a few Terraform scripts and sit in stand\-ups” kind of DevOps environment. You’ll work across cloud, containers, Linux systems, CI/CD, automation, networking, deployment tooling, and infrastructure operations. Sometimes all in the same day. The team is especially interested in people who genuinely understand Linux underneath the tooling. Not people who’ve only interacted with managed services or clicked buttons in cloud dashboards. If you know how systems actually work under the hood, you’ll stand out quickly here. **What you’ll be doing** You’ll: * Build and automate infrastructure across AWS and hybrid environments * Improve CI/CD pipelines, deployment tooling, and automation workflows * Work heavily with Linux systems, containers, and orchestration platforms * Support Kubernetes and upcoming OpenShift projects * Help engineering teams productionise new systems and services * Troubleshoot platform, networking, pipeline, and infrastructure issues * Contribute to security hardening and infrastructure improvement projects * Work closely with experienced engineers in a highly collaborative team **What makes you a strong fit** This team doesn’t need a pure Linux administrator who’s never touched modern DevOps tooling. And they don’t need someone who says they know Linux because they once SSH’d into a Red Hat box running in AWS. They need someone in the middle. You’ll probably fit well if you’ve got strong Linux fundamentals combined with modern automation and DevOps experience. You’ll need experience with most of the following: * Linux systems administration * CI/CD pipelines and deployment workflows * Terraform and Infrastructure\-as\-Code * Containers and orchestration platforms like Kubernetes * AWS environments * Python, Bash, or Ansible automation * Networking fundamentals like DNS, VPNs, routing, and load balancing Experience with OpenShift, databases, or financial services infrastructure would help, but they’re not expecting a perfect match across every tool. What matters more is whether you can learn quickly, solve problems properly, and think beyond your own technical silo. **Why people tend to like this environment** You’ll work on infrastructure that directly supports live financial markets. You’ll sit close to experienced engineers who understand both Linux and modern DevOps properly. You’ll get exposure to cloud, on\-prem, containers, automation, security, and exchange technology in the same environment instead of being boxed into one narrow area. And because the team is lean, your work actually gets seen. 📅 **Interview Process \|** Introductory call \> Technical Teams interviews \> Final culture and systems discussion \> Offer If you’d like the full details, apply and we’ll arrange a confidential conversation. **\*\*\*No sponsorship available for this opportunity, this role involves coming into the office multiple times a week\*\*\***