Senior Site Reliability Engineer

You’re a seasoned Site Reliability Engineer with years spent running production Kubernetes at scale, and you’re the kind of engineer who takes the initiative when something can be better — observability, resilience, a tricky upgrade, or the way the team thinks about security. You’re looking for a role where that initiative has room to turn into real improvements on a platform that customers trust with their most confidential data.

If multi-cluster Kubernetes, GitOps, logging, monitoring and NoSQL database management on Kubernetes are in your vocabulary, read on.

Here’s a breakdown of what you’ll do (not all of it, just the important stuff):

• Operate and continuously improve our Kubernetes production platforms, contributing to zero-downtime upgrades and multi-AZ resilience as team-wide goals.

• Grow into the team’s expert on our ELK-based log platform — centralised cross-cluster monitoring and anomaly detection — so every service owner can see, alert on and debug their workload without SRE hand-holding. Maintain and evolve our Prometheus alerting rules and Grafana dashboards alongside the team.

• Love automation. Chip away at operational toil — deployments, monitoring setup, internal reporting — building on the baseline the team already has, and ship reliably through our GitOps workflow (Flux, GitLab CI).

• Participate in our Standby and Daily Business rotation, lead incident response, run blameless post-mortems and drive the resulting action items to completion.

These are the essentials you’ll need to get an interview:

• Several years hands-on SRE, DevOps or Platform Engineering, including meaningful time running production Kubernetes at scale.

• Strong Kubernetes expertise with deep hands-on experience in at least one area — cluster lifecycle and upgrades, workload identity and RBAC, admission control, network policies, or custom resources and operators — and working familiarity with the rest.

• Proven depth in the ELK stack (or a very similar log platform) — pipelines, indexing, dashboards, alerting — with an interest in growing into the team’s observability expert. Working knowledge of Prometheus and Grafana.

• Comfortable with GitOps and CI/CD as a daily way of working (we run Flux and GitLab CI; equivalents like Argo CD, GitHub Actions or Jenkins are fine), and hands-on experience with Helm and Kustomize for managing manifests. Solid coding in Go, Python or Bash, with a love for automating away repetitive work.