Delivery pipelines and developer experience

• Design, build and maintain software delivery (CI/CD) pipelines that are fast, reliable and secure by default.
• Build and maintain infrastructure-as-code configuration, security and guardrail solutions (e.g. Helm charts, Open Policy Agent policies, and EKS admission controllers) to enforce secure, consistent deployment patterns across environments.
• Improve build, test, release and deployment workflows in collaboration with Engineering.
• Contribute to environment strategy (dev/test/staging/production) and release management strategies.
• Support the Engineers during rollouts and deployments.

Bridging DevOps and Engineering

• Work directly with Engineering teams to understand application-level constraints, so infrastructure and pipeline decisions reflect real delivery needs.
• Ideally, read, debug and reason about backend and/or frontend code where needed, enough to have credible technical conversations with engineers, contribute to root-cause analysis, and make informed platform decisions that account for application behaviour.
• Represent DevOps in architecture, design and planning discussions, including with senior engineers and product, and be able to constructively challenge and defend a technical position, as well as understand when trade-offs are necessary.

Leadership and initiative

• Take ownership of significant infrastructure and delivery initiatives from proposal through to delivery and operations.
• Research emerging tools, practices and approaches to identify improvements to our platform, delivery pipelines and operational processes, and propose practical, well-reasoned solutions to the problems you find.
• Participate as a peer in design and planning conversations across DevOps and Engineering, contributing independent judgement rather than executing instructions.
• Support the Head of Architecture and Security and the other DevOps Engineers in technical direction-setting and be capable of covering senior technical decisions and initiatives in their absence.
• Document significant technical decisions (e.g. via ADRs/RFCs), review and contribute to RFCs written by Engineers, and to the team's standards, patterns and reference architectures.

Monitoring, observability and reliability

• Design observability across infrastructure and services: metrics, logs, tracing and alerting that give early warning rather than after-the-fact explanations.
• Bring SRE practice into how the team works: define and track metrics where meaningful, drive incident response and blameless post-incident review, and turn recurring issues into permanent fixes rather than repeat firefighting.
• Continuously improve signal quality, reduce alert noise, close observability gaps, and make it fast to answer "what's actually happening in production right now".

Security, IT infrastructure and compliance support

• Evaluate, monitor, and improve as necessary the security resilience of FXE’s systems. Keep IT and network controls aligned with security and architecture requirements, and to keep audit evidence current and defensible.
• Help support and operate FXE's corporate IT infrastructure, including Microsoft 365 (identity, device management, mail, collaboration tooling) in collaboration with a 3rd party, and our ZTNA network.
• Assist with technical evidence, control implementation and remediation work for compliance frameworks such as SOC 2 and Cyber Essentials Plus.
• Balance this work proportionately alongside product infrastructure and delivery responsibilities, this is a supporting part of the role, not the majority of it.

What we are looking for

Essential

• Extensive, hands-on experience in infrastructure; you can design, troubleshoot and reason about network architecture at depth, not just consume managed services.
• Real experience developing, deploying and supporting complex infrastructures made up of many moving parts, not just designing them on a whiteboard. The kind of knowledge and judgement that only comes from having built these systems, watched them break, and fixed them under pressure.
• Strong, production-grade experience with Infrastructure as Code, including design, state management and multi-environment workflows, as well as scripting languages such as Python.
• Deep working knowledge of AWS across compute, networking, storage, IAM, and managed services in a multi-account setup.
• In-depth understanding of access controls, encryption, and networking concepts and protocols.
• Proven experience designing and operating CI/CD delivery pipelines in a production environment.
• Experience with containerisation and orchestration (e.g. Docker, Kubernetes or equivalent).
• Experience implementing security and guardrail controls in Infrastructure as Code and Kubernetes environments to enforce policy at deploy time rather than relying solely on after-the-fact review.
• Solid experience with monitoring and observability tooling (metrics, logging, tracing, alerting) and using it to drive real reliability improvements, not just dashboards.
• SRE experience or equivalent; comfortable owning production reliability, leading or contributing to incident response, and working from SLIs/SLOs where appropriate.
• Recent, hands-on experience developing and supporting modern, multi-tenant systems, using AI-assisted tooling and workflows in day-to-day engineering, current DevOps practices, and close, ongoing collaboration with developers/engineers.
• Track record of taking technical ownership of initiatives from design through to delivery, with minimal oversight.
• Demonstrated ability to operate as a credible technical peer in design and architecture discussions with senior/lead-level engineers.
• Working knowledge of software development sufficient to read and reason about application code (backend and/or frontend) and engage meaningfully with engineers on design trade-offs.
• Solid understanding of resilience, security and operability considerations in infrastructure design (e.g. failover, backup/recovery, least-privilege access, secrets management, observability).
• Strong written and verbal communication; comfortable documenting decisions and rationale for technical and non-technical audiences.

Desirable

• Experience working in a small or mid-sized organisation where DevOps and Engineering are separate but tightly coupled teams.
• Experience with configuration/decision-recording practices such as ADRs and