Senior Cloud Engineer

At SBS, we’re more than just a technology company, we’re a global fintech partner helping banks and financial institutions transform, innovate, and grow. With over 5,000 employees worldwide and clients in more than 80 countries, our solutions power everything from digital banking and lending to payments and core banking systems.

As part of
74

Software
, we’re backed by a group of leading software companies delivering mission‑critical solutions worldwide. Our focus is on delivering long‑term value, leveraging cutting‑edge technology, and fostering strong client partnerships. Join us and be part of a collaborative, forward‑thinking team shaping the future of finance.

Why SBS?

At SBS, we’re committed to supporting our employees in every aspect of their lives, from health and wellbeing to financial security and lifestyle perks.

We offer benefits that allow you to thrive at work and beyond, including health coverage, retirement plans, paid time off, flexible work, career development, competitive pay, and global culture perks.

Equal Opportunity Employer

We are committed to providing equal opportunities and ensuring a fair and inclusive recruitment process. We do not discriminate on the basis of age, disability, gender, sexual orientation, race, religion, or any other protected characteristic.

About the Role

We are looking for a Senior Cloud Engineer to join our platform team as a hands‑on third line technical specialist. This is not a generalist role — we want someone who has been deep in the engine room: diagnosing production incidents under pressure, untangling networking edge cases that defeat everyone else, and building the infrastructure that teams depend on daily.

You will be the technical escalation point for complex cloud infrastructure issues, owning problems from first triage through to root cause and lasting fix — not just restoring service and moving on. You'll also contribute to the platforms and automation that reduce the frequency of those escalations in the first place, turning hard‑won experience into better systems.

We are particularly keen to hear about the incidents and fixes you are proud of — the ones that required real diagnostic depth, creative thinking under pressure, or the courage to make a significant change in production. If you have a story that demonstrates what you are capable of at your best, this is the role where that matters.

• Infrastructure Deployment: Deploy, implement, and manage secure, scalable, and resilient AWS infrastructure using Infrastructure‑as‑Code tools such as Terraform through Git Lab.
• Cloud Automation: Design and maintain CI/CD pipelines in Git Lab to automate infrastructure delivery, testing, and compliance checks. Write supporting automation in Bash and Python using Terraform as the primary provisioning tool, reducing manual toil and enforcing consistent, repeatable deployments across all environments.
• Containerisation and Application Delivery: Manage containerised workloads running on Kubernetes, using Helm for packaging and ArgoCD to drive Git Ops‑based continuous delivery. Own the reliability of the deployment pipeline from image build through to production rollout, troubleshooting scheduling, networking, and configuration issues across the cluster.
• Cost Management: Monitor infrastructure costs, analyse usage patterns, and propose optimisations to reduce cloud spend and eliminate waste.
• Multi‑Account Management: Oversee and maintain multiple AWS accounts, ensuring governance, compliance, and consistency across environments.
• Troubleshooting & Incident Response: Own third line escalations across compute, networking, storage, and Kubernetes layers — diagnosing root causes, not just restoring service. Produce post‑incident reviews that convert hard‑won fixes into permanent platform improvements and team knowledge.
• Stakeholder
  
  Collaboration:
  
  Communicate infrastructure decisions clearly to non‑technical stakeholders, translating risk, complexity, and trade‑offs into plain language. Produce documentation that is genuinely useful — runbooks, architecture notes, and post‑incident summaries — not documentation for its own sake.
• Securi…