All remote jobs

Site Reliability Engineer

Review the role, location requirements, compensation details, and application process before deciding whether this opportunity fits your next career move.

Remote from
🌐 Anywhere
Salary
Undisclosed
Employment
Full Time
Experience
Open level
Published
Apply before
14 Nov 2026
Listing views
29
Application actions
0
Application toolkit

Make your next move.

Prepare your resume, explore your fit, and draft a cover letter for this opportunity.

AI Summary

The role, at a glance.

Supabase is hiring a senior Site Reliability Engineer to establish and scale reliability practices across its globally distributed Postgres platform. The role partners with service teams on customer-centered SLIs/SLOs, error-budget policies, operational readiness reviews, incident learning, and sustainable on-call operations. It requires substantial hands-on production engineering expertise, including cloud infrastructure, infrastructure as code, observability, automation, and resilient-system design. This is an influential individual-contributor role in an async environment, focused on enabling engineering teams to own their services’ reliability rather than centrally operating their infrastructure.

Role DNA

A quick view of the complexity, pace, ownership and collaboration implied by the job description.

Job Complexity

5/5
EasyHard

Pace & Pressure

5/5
RelaxedFast-paced

Autonomy Level

5/5
GuidedFull ownership

Communication Load

5/5
IndependentCollaborative
AI insightThis is a senior, cross-functional SRE position requiring 7+ years of reliability experience and demonstrated ability to influence technical standards across teams. The engineer must combine deep hands-on technical judgment with organizational change leadership in a fast-moving distributed environment.

Salary analysis

Estimated compensation compared with the broader US market for similar roles.

Estimated job median (per year)Market rate
$190,000
US market range (per year)$160k–$230k
AI insightThe yearly pay period is inferred from the job context; it was not explicitly stated by the employer. No employer salary was disclosed. Annual compensation is inferred as the most plausible cadence for a senior full-time Site Reliability Engineer role; the displayed USD market estimate is an AI estimate for a US-market senior SRE with platform reliability and cross-functional leadership responsibilities.

Core skills

Skills and capabilities most closely associated with this opportunity.

Sample interview questions
How would you help a service team define SLIs and SLOs that reflect customer experience rather than infrastructure health alone?

I would start by mapping the customer-critical journeys and identifying measurable success and failure events, such as successful database requests, authentication completion, or storage operation latency. I would pair those signals with clear exclusions and data-quality checks, then propose targets based on historical performance, user impact, and the team’s capacity to respond. Finally, I would connect the SLO to an error-budget policy so it drives prioritization decisions rather than remaining a dashboard-only metric.

Describe how you would conduct an Operational Readiness Review for a new platform service.

I would use a consistent review framework covering ownership, service objectives, dashboards, alert quality, runbooks, dependencies, capacity assumptions, deployment and rollback safety, graceful-degradation behavior, and on-call escalation paths. I would involve the service owners early so the review is collaborative rather than a late-stage gate. The output would be an actionable set of risks, owners, due dates, and accepted exceptions, with recurring patterns fed back into the ORR standard.

A recurring incident has affected several teams, but each postmortem identifies a different immediate trigger. How would you drive a systemic improvement?

I would compare the incidents for shared contributing conditions, such as weak dependency contracts, missing saturation signals, poor rollback controls, or unclear ownership. I would quantify the impact and frequency, then facilitate a cross-team review focused on the common failure mode rather than assigning blame. The remediation would include a prioritized technical change, updated operational standards, and a way to verify that the change reduced recurrence.

How do you reduce alert fatigue while preserving fast detection of meaningful customer impact?

I would inventory alerts by page volume, acknowledgement behavior, actionability, and correlation with actual user impact. Alerts that lack a clear operator action should be removed, converted to tickets, or replaced with higher-level symptom alerts. I would also improve routing, deduplication, runbook coverage, and SLO-based paging so on-call engineers are interrupted primarily for conditions requiring timely intervention.

How would you influence reliability improvements when you do not directly own the teams’ infrastructure or roadmaps?

I would build trust through practical engagement: helping teams diagnose issues, providing reusable tooling and clear frameworks, and demonstrating the customer and engineering cost of reliability gaps with data. I would make adoption easy by offering templates for SLOs, readiness reviews, and incident follow-up. Where tradeoffs are necessary, I would use error-budget and incident evidence to help leaders and teams make informed prioritization decisions.

This analysis is generated from the job description. Salary estimates, role characteristics and sample answers are guidance, not employer-provided facts.
Opportunity details

About this role.

About Supabase

Supabase is the Postgres development platform, built by developers for developers. We provide a complete backend solution including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search. All services are deeply integrated and designed for growth.

About the Role

Supabase manages millions of Postgres instances and is growing. We have strong teams across observability, release engineering, and incident management — and we’re concentrating our reliability efforts into a dedicated SRE practice that ties the discipline together across the platform.

You’ll be embedded within Service Operations, and your primary job is to make every engineering team more reliable — not by owning their infrastructure, but by establishing the practices, frameworks, and feedback loops that let them own reliability themselves. You’ll work across the org: sometimes setting the standard, sometimes pair-programming a fix, sometimes helping a team define their error budget, sometimes telling them it’s exhausted.

This role is ideal for someone who has a strong vision for how SRE should work and thrives in async, fast-paced environments where influence matters more than authority.

What You’ll Own

  • Partner with service teams to define meaningful SLIs and SLOs grounded in customer experience, and build the error budget policies that turn them into engineering decisions

  • Own and evolve the Operational Readiness Review (ORR) process — conducting reviews for new services and major changes across observability, alerting, runbooks, capacity, and graceful degradation

  • Strengthen the incident-to-improvement pipeline: connecting postmortem findings to operational readiness gaps, identifying repeat failure patterns, and driving systemic fixes

  • Act as the reliability expert teams pull in for architecture reviews, failure mode analysis, dependency mapping, and resilience design

  • Identify and quantify operational toil across the org, and build or advocate for automation that eliminates it

  • Help teams design sustainable on-call practices: alert quality, escalation paths, runbook coverage, and noise reduction

  • Track and report on org-wide operational maturity, surfacing systemic gaps and driving remediation

You Might Be a Good Fit If You

  • Have 7+ years of experience in SRE, production engineering, or reliability-focused roles, including experience shaping SRE practices and driving adoption across engineering teams

  • Have a software engineering mindset — you write code and build tools, not just configure them

  • Have hands-on experience defining and operationalizing SLOs/SLIs at scale, including error budget policies that actually influenced engineering decisions

  • Have deep experience with incident response, postmortem facilitation, and turning incident learnings into systemic improvements

  • Have worked with large-scale multi-tenant systems (bonus: managed database platforms or Postgres)

  • Are proficient with cloud infrastructure (AWS preferred) and infrastructure-as-code (Pulumi preferred, Terraform/CDK also acceptable)

  • Communicate clearly and persuasively — this role requires influencing without authority across a distributed org

  • Have experience in async or globally distributed teams

  • Are energized by making other teams more effective rather than being the one who fixes everything

Nice to Have

  • Experience with Kubernetes-based platform operations

  • Familiarity with OpenTelemetry, VictoriaMetrics, Grafana, or similar observability tooling

  • Experience building developer-facing reliability tooling (SLO dashboards, ORR frameworks, toil tracking, DORA metrics)

What We Offer

  • Fully Remote

    We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.

  • ESOP

    Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.

  • Tech Allowance

    Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.

  • Health Benefits

    Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family’s health are important to us.

  • Annual Off-Sites

    Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It’s a highlight of our year.

  • Flexible Work

    We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.

  • Professional Development

    Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.

About the Team

Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.

  • ~400 team members

  • 60+ countries

  • 20+ languages spoken

  • Over $1B raised (including our $500M Series F)

  • 540,000+ community members

We move fast, build in public, and use what we ship. If it’s in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support—not replace—existing tools and communities.

Apply now >

This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.

Next step

Apply now.

Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.

Did you apply?Let us know, and we’ll help you track your application.

Continue on the employer website

Protect your personal information and never pay to secure an interview or job offer. .

Log in to save
One quick step before you apply

Sign in to continue.

Sign in or create a free account to continue to the employer's application.

Applying is free. After signing in, return to this job and select Apply Now.
Add alert
Jobs Talent AI Tools Salaries
Menu