/job/site-reliability-engineer

Staff Site Reliability Engineer

Production reliability, observability, incident response, performance, and automation for systems people depend on.

Back to careersDiscuss this role

The mandate.

Own the outcome, stay close to the implementation, and improve the system around the work.

Make reliability an engineering discipline: define service objectives, automate operational work, improve system resilience, and create incident practices that make the organisation safer rather than quieter.

The role stays close to code and architecture. It should reduce toil and failure modes, not become a permanent escalation queue.

Impact
Material
Agency
High
Management
Context, then space
Bureaucracy
Low

What this role owns.

Responsibilities written as outcomes and systems, not a shopping list of meetings.

  1. OWN-01

    Define and evolve SLOs, error budgets, service health indicators, and reliability reporting with product and engineering teams.

  2. OWN-02

    Design observability across metrics, logs, traces, alerting, and user journeys so pages are actionable and failures are diagnosable.

  3. OWN-03

    Lead incident command, blameless reviews, and follow-through on systemic corrective work.

  4. OWN-04

    Build automation for deployment, recovery, capacity, performance, and repetitive operational workflows.

  5. OWN-05

    Partner with software and platform teams on resilience, disaster recovery, cost, scalability, and safe change management.

What this needs.

  • Strong Linux, cloud, Kubernetes, networking, and distributed-systems fundamentals.
  • Production coding ability in Go, Python, Java, or another systems language; shell scripts alone are not the reliability strategy.
  • Experience with Prometheus, Grafana, OpenTelemetry, Datadog, Dynatrace, Splunk, or comparable observability systems.
  • Calm incident leadership and the ability to communicate clearly with engineers, leaders, customers, and support teams.
  • A track record of reducing toil and recurrence through software, architecture, and operating-model changes.

What success looks like.

  • Customer-impacting incidents become less frequent, shorter, and easier to understand.
  • Alerts map to user impact and an actionable response instead of creating background anxiety.
  • Operational toil decreases while safe deployment velocity increases.
  • Teams use SLOs and post-incident learning to make real prioritisation decisions.

Compensation target.

Top-quartile ranges for this scope. Ranges are base salary; equity and bonus may be additional. The cash/stock split is negotiable.

EMEA
€180k–€245kBase salaryTop-quartile EMEA target
US remote
$215k–$280kBase salaryRemote US target
US major hubs
$265k–$315kBase salarySan Francisco, Seattle, New York, and comparable markets

Who you need to be

  • At least 7+ years of software, infrastructure, platform, or Site Reliability Engineering experience.

  • Operated high-traffic production systems with clear service objectives, on-call ownership, and incident response.

  • Built observability and operational automation instead of only configuring monitoring tools.

  • Led incidents and post-incident improvements while creating a blameless reliability culture.

  • Strong programming, Linux, cloud, Kubernetes, networking, and distributed-systems fundamentals.

Looks compatible.

Real impact, useful autonomy, and enough technical depth to finish the job.

Discuss this role