About BancX

BancX enables banks, fintech's, and retailers to rapidly launch digital financial services through our Banking-as-a-Service (BaaS) platform. We run our 40+ Java Microservices on Kubernetes deployed via Helm and ArgoCD. Our platform has been designed to support multi cloud and bare metal deployments.

We are currently migrating from Azure to AWS with a Terraform-first infrastructure-as-code approach. Our architecture & design has been developed in conjunction with AWS MAP program architects and security professionals to ensure our approach is best practice and secure.

Your Role

Own and evolve BancX's multi-cloud infrastructure and take over from the founding team.

• Lead and own the migration into AWS

• Post AWS migration: replicate the new architecture back to Azure, establishing true multi-cloud capability with consistent IaC patterns

• Spec, build and support new features and enhancements to the platform's infrastructure

• Implement and maintain security controls: IAM, secrets management, certificate lifecycle, compliance requirements

• Support the infrastructure across all environments and cloud vendors

• Lead and run deployments and upgrades

• Ensure application and infrastructure monitoring and alerting is set up, maintained and actioned if there are issues. Stack: Prometheus, Thanos, Loki, Grafana, AlertManager

• Delegate and distribute work across the DevOps team and yourself

• CI/CD pipeline management (GitHub Actions with self-hosted runners)

• Drive continuous improvement in reliability, security, cost efficiency, and performance

• Establish and champion DevOps best practices

• Respond to and fix production incidents

Why This Role Matters

We enable our customers to launch digital banking products in months, not years. When our platform is fast and reliable, our customers can compete with traditional banks. When we scale efficiently, we make banking innovation affordable for startups.

Your infrastructure work directly impacts:

• How quickly customers can launch new products

• Whether they can handle Black Friday transaction spikes

• If they trust us with their most critical business operations

Requirements

• 7 – 10+ years of DevOps experience

• Infrastructure-as-Code mastery (Terraform strongly preferred, or equivalent depth with Pulumi/CloudFormation)

• Significant experience with at least one cloud provider: GCP, AWS, Azure

• Deep Kubernetes expertise, you've run production clusters at scale, not just deployed to them

• Experience working with mariadb / mysql & postgres

• Positive and solution-oriented mindset

• Communication: able to provide clear status updates and escalate risks with solutions

• Experience owning a project from concept to production, including spec, discussion, and execution

• Demonstrated ability to work closely with other parts of the organization

• Takes end-to-end accountability without being asked

• Self-motivated and self-managing, with strong organizational skills

Highly Desired

• AWS experience (EKS, RDS, MSK, Networking, IAM)

• GitOps / ArgoCD experience

• Observability stack experience (Prometheus, Grafana, Loki)

• Kafka or streaming platforms

• Regulated industry experience (banking, fintech, finance)

Why Join BancX?

We hire experienced engineers and trust them to own their domain. You'll have the autonomy to make technical decisions and the responsibility to own the outcomes. You're joining as we modernise our infrastructure. Modern tooling, clean architecture, Infrastructure-as-Code from day one.

As BancX scales, so does the infrastructure challenge. Customer expansion, new features, increasing transaction volumes: you'll be solving new problems, not just maintaining a steady state.

Who You Are

You're a fit if:

• You ask "why are we building this?" before "how should we build this?"

• You've stayed up at night worrying about customer impact during incidents

• You read product roadmaps to anticipate infrastructure needs

• You get excited when infrastructure enables a new product feature

• You measure success by business outcomes, not just uptime percentages