> Markdown version of [/jobs/ext/4666286-lead-site-reliability-engineer](https://www.wearedevelopers.com/jobs/ext/4666286-lead-site-reliability-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Lead Site Reliability Engineer

- **Company:** Zego
- **Location:** London, United Kingdom
- **Experience:** Expert
- **Salary:** £65,702
- **Contract:** Permanent contract
- **Skills:** Clean Code Principles, Artificial Intelligence, Amazon Web Services, Systems Engineering, Encodings, Python (Programming Language), Reliability Engineering, Runbook, Software Engineering, Datadog, AI Platforms, Kubernetes
- **Published:** November 11, 2026
- **Apply:** https://www.adzuna.co.uk/jobs/details/5961467935

## About the Role

* Deep SRE experience: SLI and SLO definition, error budget management, and ownership of incident response through to blameless retrospectives.
 * Fluency with AI as an engineering tool rather than a chat window: building agents and automation, working with MCP servers or equivalent, and judgement about where an agent can act and where a human stays in the loop.
 * Strong software engineering in Python, writing tested, maintainable code that other engineers can run and extend.
 * Observability depth with OpenTelemetry and Datadog.
 * AWS at scale, and Kubernetes based platforms managed through Infrastructure as Code.

## Description

You will build the Site Reliability Engineering function at Zego, embedding reliability, observability and operational excellence as core engineering concerns - AI is the primary lever for doing that at scale, not a bolt on.

 * You will be our dedicated SRE, working alongside Systems Engineering and embedded with Product and Engineering across roughly 120 engineers. Teams own their services and their own on-call. You own the framework, the instrumentation and the AI tooling that makes that ownership work.
 * You will make teams good at running what they build: alert quality over alert volume, runbooks an agent can execute rather than prose that describes, and diagnostics good enough that an engineer or an agent reaches resolution without an SRE in the room.
 * You will be the primary advocate for reliability with Product and Engineering, making the case with data rather than assertion, so platform health is prioritised alongside delivery commitments., * Define and land the reliability standard: SLIs, SLOs, error budgets and production readiness criteria that teams apply to their own services, with adoption measured rather than assumed.
 * Encode standards into automation rather than enforcing them by hand. Guardrails in CI, agents that check reliability and observability posture on pull requests, and safe defaults in shared infrastructure so the reliable path is the easy path.
 * Build SRE capability on Zego's AI platform, extending our MCP servers and agents, and making the estate legible to them through machine readable runbooks, structured telemetry and diagnostics an agent can act on.
 * Own observability as a practice, including instrumentation design, signal quality, cardinality and cost.
 * Raise the standard of incident response end-to-end, from detection and triage through to retrospectives that produce change. Put AI to work where it pays off most, stripping toil out of incidents so responders can focus on judgement
 * Measure toil, publish it, and remove it through tooling that others can run without you.