DevOps Engineer (E4E5B59)

Referment is working with a financial technology business that provides banks with the data infrastructure and intelligence behind personalised digital banking. Its software runs in live banking environments, where infrastructure decisions have direct consequences for customers, security and service reliability.

The business is moving from an Azure-only infrastructure model towards a multicloud strategy, starting with AWS. This is an architectural and operational change rather than a straightforward lift-and-shift, and it is happening alongside active client delivery. As a DevOps Engineer, you'll help design, prove and operate that new environment while keeping existing production systems dependable.

You'll work hands-on with engineering squads, bringing practical production experience to migration decisions, deployment automation and infrastructure design. The remit combines building the next cloud environment with maintaining the systems that bank clients rely on today.

The Role

• Drive the multicloud strategy from design through proof of concept to operational delivery, introducing AWS alongside the existing Azure footprint.
• Own CI/CD pipelines, infrastructure-as-code and deployment automation across environments, making changes repeatable and manageable.
• Work with engineering squads to evaluate cloud migration choices against real client workloads rather than theoretical designs.
• Maintain production reliability while the underlying infrastructure changes, balancing migration progress with continuity of client delivery.
• Use AI tools within the DevOps workflow, including automation, testing and day-to-day engineering tooling.
• Challenge shortcuts that could weaken reliability or security, explaining the practical consequences and helping teams find workable alternatives.

What We're Looking For

• At least five years' relevant experience, including a minimum of three years working with public clouds. You should have operated production infrastructure at scale with real clients depending on it; certifications or lab projects alone are not enough.
• Experience across more than one cloud provider, or ownership of a genuine migration between providers.
• Strong Azure and AWS knowledge, supported by hands-on experience of Kubernetes, Helm and Terraform. You should be comfortable reviewing existing infrastructure-as-code and identifying design or implementation problems.
• Practical CI/CD experience, including FluxCD or ArgoCD.
• Comfort working within regulated or high-stakes environments, including on-premises constraints, security requirements and demanding client expectations.
• Regular use of AI-assisted engineering tools such as Cursor and Claude Code as part of your working practice.

Relevant Desirable Experience

• Cluster observability and monitoring stacks.
• Cloud compliance and security controls.
• Kafka, RabbitMQ or GCP.
• Fintech or another regulated industry background.

Working Environment This is a B2B contract engagement with two days each week in the office and three working remotely. The employer lists private healthcare and support for fitness and everyday working costs. The work offers a concrete multicloud mandate and exposure to software operating within large banks, rather than a cloud strategy that stops at planning.

Interview Process The process starts with a 30-minute screening discussion about systems you've run, decisions you've made and production trade-offs. A 90-minute technical interview centres on a real infrastructure or migration problem; AI tools are welcome. A final 15-minute conversation with the CTO explores your approach to cloud strategy and reliability at scale.

This could suit a DevOps or platform engineer who has already supported demanding production systems and wants to combine hands-on cloud migration with responsibility for keeping live services reliable.

#Referment