Staff Site Reliability Engineer

Mbianchi; Amsterdam; Hybrid; EUR 180,000 - 245,000; Full time

Job summary

Mbianchi is seeking a senior reliability engineer to own service health and automate operational work across cloud-native environments. You will define SLOs, build robust observability, and lead blameless incident reviews to reduce toil and improve system resilience.

The role stays close to code and architecture, emphasizing practical improvements over escalation queues. Strong Linux, cloud, and Kubernetes fundamentals are essential.

Qualifications

• 7+ years of software, infrastructure, or SRE experience.
• Proven ability to operate high-traffic production systems with on-call ownership.
• Experience building observability and automation rather than mere monitoring.

Responsibilities

• Define and evolve SLOs, error budgets, and resilience metrics with product and engineering teams.
• Design observability across metrics, logs, traces, alerts, and user journeys.
• Lead incident command and blameless reviews, plus follow-up on systemic improvements.
• Build automation for deployment, recovery, capacity, performance, and repetitive tasks.
• Partner with software and platform teams on resilience, disaster recovery, cost, and safe change management.

Skills

Linux fundamentals

Cloud

Kubernetes

Networking

Distributed systems

Go

Python

Java

Incident leadership

Tools

Prometheus

Grafana

OpenTelemetry

Datadog

Dynatrace

Splunk

Job description

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

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.

• OWN-01 Define and evolve SLOs, error budgets, service health indicators, and reliability reporting with product and engineering teams.
• OWN-02 Design observability across metrics, logs, traces, alerting, and user journeys so pages are actionable and failures are diagnosable.
• OWN-03 Lead incident command, blameless reviews, and follow-through on systemic corrective work.
• OWN-04 Build automation for deployment, recovery, capacity, performance, and repetitive operational workflows.
• 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.

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

EMEA €180k–€245k Base salary Top-quartile EMEA target

US remote $215k–$280k Base salary Remote US target

US major hubs $265k–$315k Base salary San 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.