About this job
<h3>About <a href="https://jobicy.com/company/supabase" target="_blank" rel="noopener">Supabase</a></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>About the Role</h3>
<p>We're looking for a <strong>Release Engineer (SRE)</strong> to join our <strong>Release Engineering</strong> team (part of EngOps) — a production-operations expert who brings an SRE mindset to how Supabase ships and runs, making deploys safe, observable, and recoverable at scale.</p>
<p>Release Engineering's scope has grown well beyond build-and-ship: we increasingly own the operational reliability of the systems that deploy and run Supabase. In this role you'll treat our deployment pipelines, pre-production signal, and the control plane itself as production systems — with SLOs, error budgets, and on-call ownership — and you'll be the person teams lean on when reliability is on the line.</p>
<p>This is not a "gatekeeper" role. You'll make the reliable path the easy path: standardising how we deploy, instrumenting what we ship, and ensuring that when something breaks, we detect it quickly and recover quickly.</p>
<h3>What You'll Be Responsible For</h3>
<p>In this role, you'll:</p>
<ul>
<li>
<p>Own the reliability of Supabase's deployment and release systems, and the control plane they run on, against clear SLOs and error budgets</p>
</li>
<li>
<p>Turn pre-production into a trustworthy signal — standardizing and instrumenting today's fragmented, ad-hoc deployment workflows</p>
</li>
<li>
<p>Drive disaster-recovery readiness, including making environments reproducibly deployable from scratch (untangling undocumented secrets, unclear configuration ownership, and circular service dependencies)</p>
</li>
<li>
<p>Build and operate health and SLO monitoring for critical user flows, using synthetic testing to catch regressions before customers do</p>
</li>
<li>
<p>Reduce mean-time-to-detect and mean-time-to-recover for deploy-related incidents — which account for a large share of our incident load</p>
</li>
<li>
<p>Participate in on-call, lead blameless postmortems, and turn findings into runbooks, alerting, and automation that remove toil</p>
</li>
<li>
<p>Improve deployment observability and auditability — a clear record of what shipped where, when, and by whom</p>
</li>
<li>
<p>Document operational procedures — break-glass paths, access models, and runbooks — so reliability knowledge isn't tribal</p>
</li>
</ul>
<h3>Reliability & Operations</h3>
<ul>
<li>
<p>Define and track SLAs, SLOs, error budgets, and DORA delivery metrics — with meaningful alerting over noise</p>
</li>
<li>
<p>Ensure deployments fail fast and safely when health checks degrade</p>
</li>
<li>
<p>Harden access and break-glass workflows (e.g. scoped self-service) so the right people can act in an incident without unsafe workarounds</p>
</li>
<li>
<p>Partner with product engineering and platform teams to align release practices with reliability and availability targets</p>
</li>
</ul>
<h3>You Might Be a Good Fit If You</h3>
<ul>
<li>
<p>Have 5+ years in SRE, production operations, platform engineering, or release engineering</p>
</li>
<li>
<p>Have operated production systems at scale and carried on-call for them</p>
</li>
<li>
<p>Are fluent in SLAs, SLOs, error budgets, DORA metrics, and operational KPIs — and the observability tooling behind them (Prometheus, Grafana, Alertmanager, or similar)</p>
</li>
<li>
<p>Have led incident response with tooling like <a href="http://incident.io" rel="nofollow ugc noopener" target="_blank">incident.io</a> (or PagerDuty / Opsgenie), run blameless postmortems, and driven down MTTD/MTTR</p>
</li>
<li>
<p>Operate confidently on AWS (multiple accounts, IAM, VPC) in production</p>
</li>
<li>
<p>Are comfortable with infrastructure-as-code (Pulumi, Terraform) and Kubernetes</p>
</li>
<li>
<p>Script and automate to eliminate toil rather than absorb it</p>
</li>
<li>
<p>Communicate clearly with both infrastructure specialists and product engineers</p>
</li>
<li>
<p>Thrive in async, globally distributed teams</p>
</li>
<li>
<p>Are comfortable navigating ambiguity and iterating toward better systems over time</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>