We’re looking for a creative, experienced DevOps engineer based in London to join our fintech startup at the ground floor. If you are excited about independence, impact, and contributing to the battle against scams and financial crime, read on to learn more ⬇️

About the role 🎭

Banks approve or reject payments with almost no context. We're building the intelligence layer that changes that — running real-time investigations on payments before they clear. The technical challenge is to keep this system running 24/7/365 with the reliability that banks demand, while the platform underneath evolves rapidly. Think enterprise resilience with startup velocity 🚀

What you’ll work on

• Own the reliability and operability of our production systems — monitoring, alerting, incident response, and post-incident learning
• Maintain and evolve our infrastructure-as-code estate (Terraform on GCP). Make it easy for engineers to ship safely and hard to ship dangerously
• Secure our infrastructure defaults to ensure that the easy path is the safe path
• Design and implement observability across our stack: metrics, traces, logs, and the dashboards and alerts that make them useful
• Drive incident response maturity, from detection through resolution to follow-up. You'll get an opportunity to shape what "good" looks like here
• Evaluate and introduce tooling for AI-native reliability challenges: monitoring non-deterministic systems, detecting drift in agent behaviour, and understanding failure modes that traditional APM doesn't cover
• Improve deployment pipelines and release processes

This is not a "keep the lights on" role. You'll be building the foundations that let a fast-moving team ship with confidence — and you'll have real influence over how we grow.

Why this is hard

We're a small team shipping to large banks. Our systems are critical infrastructure — when we're unavailable, real fraud investigations stop and real payments are delayed. To compound resilience further, our increasing footprint of production AI agents are non-deterministic by nature, which means traditional monitoring and alerting isn't enough. You'll need to use (or invent!) cutting-edge approaches to observability for systems where correct behaviour isn't always the same twice. And you'll be doing this as (likely) the first person in the role, which means building the culture and the tooling from scratch.

Our stack today:

• Infra: GCP, Terraform, Cloud Run (and soon, k8s!), managed GCP datastores
• Backend: Python, Kotlin
• CI/CD: GitHub Actions
• Monitoring: GCP Cloud Monitoring, Cloud Logging (we know we need more — that's where you come in)