← Back to Job Board

Container Engineer

Supabase

Official advert: Supabase · jobs.ashbyhq.com

Remote, open to applicants in Kenya. An international employer - before you accept, check whether you would be an employee or a contractor, the pay currency, and how tax is handled.

Remote, Global · remote

Posted 18 Nov 2026

Apply

About

Supabase is hiring a remote, global Container Engineer to help operate and evolve its internal multi-tenant, multi-region managed Kubernetes platform. The role covers platform reliability and operations, production software engineering, and tooling/ecosystem architecture, including on-call incident response. Candidates need 5+ years of relevant production infrastructure experience and deep expertise in at least one of tooling and ecosystem, software engineering, or operational/SRE practice.

How to apply

Create a free account to apply

Sign up and add a short profile, then see how to apply and open the official advert. We'll track every application for you, alert you to jobs like this one, and you'll apply faster next time.

About two minutes, and you come straight back to this job. Cazini never charges to apply.

Responsibilities

  • Regardless of the skill set, all team members carry a share of the team's on-call rota, responding to platform incidents and driving them to resolution and follow-up.
  • Define SLIs/SLOs and error budgets for the container platform itself, and build error-budget policies that actually gate platform changes.
  • Own the Operational Readiness Review (ORR) process for new platform capabilities and major changes.
  • Design and track metrics for platform uptime, and increase observability into the platform by capturing the right metrics, logs, and traces across the platform layers.
  • Drive the incident-to-improvement pipeline: facilitate blameless postmortems, connect findings to readiness gaps, spot repeat failure patterns, and push through systemic fixes.
  • Build and maintain the platform's automation, controllers, operators, and internal tooling — writing production code and shipping it, not just wiring together existing tools.
  • Design and implement the platform-side CI/CD and rollout primitives that speed up platform deployments while working within proper change and release management.
  • Implement and maintain security automation for the platform: intrusion detection, automated remediation, and patch management.
  • Identify and quantify operational toil, and build the automation that removes it rather than just documenting it.
  • Contribute to the platform's continual testing automation — the test suites and pipelines that validate platform releases are fit for purpose before they reach tenants.
  • Act as a platform reliability and architecture expert — contribute to failure-mode analysis, dependency mapping, and resilience design for multi-tenant container workloads.
  • Evaluate and evolve the platform's tooling ecosystem (orchestration, runtime, networking, isolation, and observability stack) with a clear, opinionated view on trade-offs.
  • Improve system architecture to reduce infrastructure cost while balancing security, reliability, and performance across tenants.
  • Guide teams building on the platform to design sustainable on-call practices for their own services: alert quality, escalation paths, runbook coverage, and noise reduction.

Qualifications

  • Have 5+ years in platform engineering, container/Kubernetes platform operations, SRE, or production infrastructure, and have operated production systems at scale and carried on-call for them.
  • Are genuinely deep in at least one — ideally two — of the three strength areas below (and tell us which is your center of gravity):
  • Tooling & ecosystem — know the container/orchestration landscape well: Kubernetes, containerd and the OCI/CRI standards, and the surrounding CNCF ecosystem (e.g. Argo CD/Argo Rollouts for GitOps and progressive delivery; Cilium/eBPF networking and the Gateway API; Karpenter/KEDA-style autoscaling; a
  • Software engineering — write real production code (Go and/or a comparable systems language) and can build controllers, operators, and platform APIs — stepping back to the underlying problem and building the right solution when no off-the-shelf tool fits.
  • Operational / SRE practice — are fluent in SLOs, error budgets, and operational KPIs; have led incident response and blameless postmortems; and have driven down MTTD/MTTR for systems you operated.
  • Have worked with large-scale multi-tenant systems and understand isolation as a spectrum — from namespaces, RBAC, network policies, and resource quotas through to stronger primitives such as virtual clusters (e.g. vCluster) or VM-class runtimes.
  • Operate confidently on AWS (multiple accounts, IAM, VPC) and are comfortable with infrastructure-as-code (Pulumi preferred; Terraform/CDK also fine) and Kubernetes.
  • Script and automate to eliminate toil rather than absorb it.
  • Communicate clearly with both infrastructure specialists and product engineers, and thrive in async, globally distributed teams.
  • Are comfortable navigating ambiguity and iterating toward better systems over time.
  • Experience building and operating a multi-tenant Kubernetes platform that internal teams deploy onto.
  • Familiarity with policy engines (Kyverno, or OPA/Gatekeeper) and cost-attribution tooling (OpenCost/Kubecost) for per-tenant chargeback/showback.
  • Experience with managed database platforms or Postgres.
  • Familiarity with OpenTelemetry, Prometheus/VictoriaMetrics, Grafana, or similar observability tooling.

Similar jobs

Get new it jobs by email

Free, one email a day at most, unsubscribe any time.