Senior Site Reliability Engineer

About the role

The Senior Site Reliability Engineer will own the reliability of our MySQL and MongoDB footprint across Google Cloud, work alongside application engineers on performance and schema decisions, and contribute to the broader platform, observability with Prometheus, Loki, and Tempo; on-call; incident response.

Responsibilities

• Design, deploy, and operate highly available MySQL and MongoDB clusters across our cloud environments; replication, sharding, backups, point-in-time recovery, upgrades, and disaster recovery.
• Tune query performance, schema, and index strategy in partnership with application engineers and push fixes upstream into the application when that’s the right answer.
• Extend our observability stack — Prometheus, Loki, and Tempo — so the data tier is as well instrumented as the application tier, and traces actually reach the root cause.
• Participate in the Platform on-call rotation, lead incident response for data-tier issues, and write postmortems that drive durable change.
• Improve disaster recovery, security posture, and compliance for our database footprint — encryption, access control, audit logging, backup integrity.
• Evaluate and operate ScyllaDB/Cassandra and Elasticsearch where they fit the workload, and bring an opinion on when they don't.
• Write the automation, tooling, and operators that take repetitive work off the team’s plate.
• Use AI to compress incident response and root-cause analysis; building agents, automation, and developer-enablement tooling that scale the team’s reliability work.

Requirements

You’ve operated highly available MySQL and MongoDB in production at scale; replication, sharding, backups, point-in-time recovery, and failover drills you’ve actually run, not just designed on paper.

You diagnose database performance end-to-end; query plan, indexes, locking, OS, storage, network — and can point to specific incidents where you found and fixed root cause that others had missed.

You’ve shipped meaningful work on at least two of bare metal Linux, containerized workloads (Docker, Kubernetes, or similar), and a major cloud (GCP preferred; AWS or Azure equivalent is fine).

You instrument what you build. You’ve used Prometheus, OpenTelemetry, or comparable systems to close real incidents, and you’ve written the dashboard the next on-call engineer will actually open.

You write code that runs in production: Python, Go, Bash, or similar for automation, tooling, or operators. You don’t hand off scripting to someone else.

You communicate clearly under pressure and after the fact. Your postmortems are blameless, specific, and lead to changes that stick — and the people you’ve worked with describe collaborating with you as straightforward.

You bring an opinion on managed vs. self-managed databases, and can defend the trade-off based on availability, cost, and operational burden.

You have 7+ years in SRE, DevOps, platform, infrastructure, or database reliability roles, with at least 3 years owning production databases.

You have a BSc in Computer Science or equivalent practical experience.

ScyllaDB/Cassandra or Elasticsearch experience is a plus.

You’ve used AI tooling: copilots, agents, or custom automation to expedite incident response, root-cause analysis, or developer workflows.

Qualifications

7+ years in SRE, DevOps, platform, infrastructure, or database reliability roles, with at least 3 years owning production databases.

BSc in Computer Science or equivalent practical experience.

ScyllaDB/Cassandra or Elasticsearch experience is a plus.

You’ve used AI tooling: copilots, agents, or custom automation to expedite incident response, root-cause analysis, or developer workflows.

Skills

Operating highly available MySQL and MongoDB in production at scale; replication, sharding, backups, point-in-time recovery, and failover drills you’ve actually run, not just designed on paper.

Diagnosing database performance end-to-end; query plan, indexes, locking, OS, storage, network — and pointing to specific incidents where you found and fixed root cause that others had missed.

Shipping meaningful work on at least two of bare metal Linux, containerized workloads (Docker, Kubernetes, or similar), and a major cloud (GCP preferred; AWS or Azure equivalent is fine).

Instrumenting what you build; using Prometheus, OpenTelemetry, or comparable systems to close real incidents, and writing the dashboard the next on-call engineer will actually open.

Writing code that runs in production: Python, Go, Bash, or similar for automation, tooling, or operators; not handing off scripting to someone else.

Communicating clearly under pressure and after the fact; your postmortems being blameless, specific, and leading to changes that stick — and the people you’ve worked with describing collaborative interactions as straightforward.

Bringing an opinion on managed vs. self-managed databases, and defending the trade-off based on availability, cost, and operational burden.

Using AI tooling: copilots, agents, or custom automation to expedite incident response, root-cause analysis, or developer workflows.

Benefits

We provide competitive pay, equity with significant upside, and intentionally design our benefits to encourage healthy and well-balanced employees, flexible schedules and time off.

We even offer a sabbatical after every five years of service so you’re able to pursue and enjoy what matters most to you.

We wouldn’t be a technology company without a ping-pong table and free snacks in our break room.

Pay

Competitive compensation package with equity and significant upside potential.

Schedule

Flexible schedule and generous time off.