Site Reliability Engineer

<h3><strong>About <a href="https://jobicy.com/company/supabase" target="_blank" rel="noopener">Supabase</a></strong></h3> <p>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.</p> <h3><strong>About the Role</strong></h3> <p>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.</p> <p>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.</p> <p>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.</p> <h3><strong>What You'll Own</strong></h3> <ul> <li> <p>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</p> </li> <li> <p>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</p> </li> <li> <p>Strengthen the incident-to-improvement pipeline: connecting postmortem findings to operational readiness gaps, identifying repeat failure patterns, and driving systemic fixes</p> </li> <li> <p>Act as the reliability expert teams pull in for architecture reviews, failure mode analysis, dependency mapping, and resilience design</p> </li> <li> <p>Identify and quantify operational toil across the org, and build or advocate for automation that eliminates it</p> </li> <li> <p>Help teams design sustainable on-call practices: alert quality, escalation paths, runbook coverage, and noise reduction</p> </li> <li> <p>Track and report on org-wide operational maturity, surfacing systemic gaps and driving remediation</p> </li> </ul> <h3><strong>You Might Be a Good Fit If You</strong></h3> <ul> <li> <p>Have 7+ years of experience in SRE, production engineering, or reliability-focused roles, including experience <strong>shaping SRE practices and driving adoption across engineering teams</strong></p> </li> <li> <p>Have a software engineering mindset — you write code and build tools, not just configure them</p> </li> <li> <p>Have hands-on experience defining and operationalizing SLOs/SLIs at scale, including error budget policies that actually influenced engineering decisions</p> </li> <li> <p>Have deep experience with incident response, postmortem facilitation, and turning incident learnings into systemic improvements</p> </li> <li> <p>Have worked with large-scale multi-tenant systems (bonus: managed database platforms or Postgres)</p> </li> <li> <p>Are proficient with cloud infrastructure (AWS preferred) and infrastructure-as-code (Pulumi preferred, Terraform/CDK also acceptable)</p> </li> <li> <p>Communicate clearly and persuasively — this role requires influencing without authority across a distributed org</p> </li> <li> <p>Have experience in async or globally distributed teams</p> </li> <li> <p>Are energized by making other teams more effective rather than being the one who fixes everything</p> </li> </ul> <h3><strong>Nice to Have</strong></h3> <ul> <li> <p>Experience with Kubernetes-based platform operations</p> </li> <li> <p>Familiarity with OpenTelemetry, VictoriaMetrics, Grafana, or similar observability tooling</p> </li> <li> <p>Experience building developer-facing reliability tooling (SLO dashboards, ORR frameworks, toil tracking, DORA metrics)</p> </li> </ul> <h3></h3> <h3><strong>What We Offer</strong></h3> <ul> <li> <p><strong>Fully Remote</strong></p> <p>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.</p> </li> <li> <p><strong>ESOP</strong></p> <p>Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.</p> </li> <li> <p><strong>Tech Allowance</strong></p> <p>Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.</p> </li> <li> <p><strong>Health Benefits</strong></p> <p>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.</p> </li> <li> <p><strong>Annual Off-Sites</strong></p> <p>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.</p> </li> <li> <p><strong>Flexible Work</strong></p> <p>We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.</p> </li> <li> <p><strong>Professional Development</strong></p> <p>Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.</p> </li> </ul> <h3><strong>About the Team</strong></h3> <p>Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.</p> <ul> <li> <p>~400 team members</p> </li> <li> <p>60+ countries</p> </li> <li> <p>20+ languages spoken</p> </li> <li> <p>Over $1B raised (including our $500M Series F)</p> </li> <li> <p>540,000+ community members</p> </li> </ul> <p>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.</p>