
Enable job alerts via email!
Generate a tailored resume in minutes
Land an interview and earn more. Learn more
A high-growth SaaS company is looking for a Senior SaaS Platform Reliability Engineer to enhance reliability practices across their platform. In this fully remote role within UK time zones, you'll contribute hands-on to reliability improvements, working alongside product teams to define SLIs and SLOs. The ideal candidate will possess strong experience in Azure, Kubernetes, and automation, and is expected to actively engage in incident response. This position offers various benefits including health insurance and a flexible work setup.
Once For All is a high-growth, cloud-based SaaS subscription business helping organisations manage supply chain governance, risk management, and compliance. We support over 250,000 customers across the UK, across more than 20 public and private sector industries, including construction, transport, retail, hospitality, education, facilities management, manufacturing, and central and local government.
Join our engineering team as a Senior SaaS Platform Reliability Engineer, taking a foundational role in establishing and maturing reliability engineering practices across our SaaS platform.
This is not an advisory or oversight-only role. You will personally contribute to reliability improvements, working in partnership with our SCRUM-based product teams and our DevOps and Cloud engineering teams to ensure those improvements are delivered safely into production.
You will help define SLIs, SLOs, and error budgets for tier-1, customer-facing services, and contribute to how reliability trade-offs are made and communicated. The role focuses on improving and evolving existing systems—observability, alerting, performance tooling, automation, and testing—rebuilding components where necessary to better support SLO-driven reliability.
This role is fully remote, working within UK time zones.
To be explicit:
This is not a strategy-only role. You will personally contribute reliability improvements, working alongside product and platform teams to see them delivered into production.
Expect to spend ~60–80% of your time building and operating, including:
Instrumentation, dashboards, and alerting
Automation to reduce operational toil
Release safety mechanisms and guardrails
You will be an active on-call contributor for tier-1 services and lead incident response end-to-end (triage → mitigation → permanent fix → postmortem).
You will write production code (not only infrastructure-as-code) to improve reliability, availability, and performance.
You will build on and improve existing observability, alerting, performance, automation, and test systems, rebuilding components where necessary rather than starting from scratch.
Success in this role is measured by outcomes, such as:
Clear and trusted SLO reporting
Reduced alert noise
Improved p95 / p99 latency
Fewer production regressions and rollbacks
Define user-centric SLIs and SLOs for critical customer journeys.
Define and maintain error budgets, and work with sprint teams to guide how error budgets are understood and spent.
Provide visibility and expertise to support reliability-focused trade-offs while sprint teams remain accountable for delivery.
Own reliability outcomes for tier-1, customer-facing services.
Evaluate, design, and improve end-to-end observability across metrics, logs, and traces.
Improve existing alerting to focus on customer impact rather than infrastructure noise.
Continuously refine signals to improve detection, reduce false positives, and minimise alert fatigue.
Actively participate in and lead major incident response when required.
Run blameless postmortems focused on systemic improvement.
Track and improve MTTR, MTTD, and incident recurrence over time.
Identify operational toil and reduce it through engineering and automation.
Improve and extend existing automation and operational tooling.
Treat reliability issues as software problems, not process gaps.
Contribute to zone- and region-aware architectures on Azure and AKS.
Perform capacity planning and load testing aligned to SLOs.
Improve p95 and p99 latency, throughput, and behaviour under failure conditions.
Improve safe release mechanisms including canary, blue/green, and progressive delivery.
Strengthen detection and rollback strategies for faulty releases.
Partner with teams to improve test coverage where it directly protects production reliability.
Contribute to infrastructure as code using Terraform or Bicep.
Help enforce standards and guardrails via policy as code.
Support platform security through managed identity, secrets management, least privilege, and network segmentation.
Raise reliability standards across engineering teams through hands-on collaboration and guidance.
Help teams adopt SLOs, observability, and safer operational practices pragmatically.
We value real-world reliability problem solving over titles or years of experience. Candidates should be able to describe specific production incidents they contributed to and the lasting improvements they delivered.
Intro & role overview with Talent.
Technical deep dive covering reliability trade-offs, Azure, AKS, and real incident experience.
Practical exercise:
Define SLIs/SLOs for a sample service
Propose an alerting strategy focused on customer impact
Design a safe release and rollback plan
Collaboration & influence interview with Engineering.