Location
Remote, Global
Job Type
full-time
Work Format
🌍 Remote Worldwide
Salary
Not specified
Posted
October 13, 2026

Job Description

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

We're looking for a Postgres Deployment Engineer to join our team and elevate our PostgreSQL offerings.

You'll work hand-in-hand with the PostgreSQL team and play an instrumental role in technical decision-making and refining internal methodologies.

The focus of this role is around owning stability and deployment of our products. This role involves ongoing contribution and co-responsibility for builds/deployments via our public supabase/postgres GitHub repository. This repository bundles an array of features/products into docker images and AWS AMIs, giving users the ability to run Supabase on our cloud and locally. This role will function has developed as a bridge between product and infrastructure teams to improve the reliability of product deployments and upgrades.

In this role, your primary responsibilities will include:

  • Packaging software into our supabase/postgres repo to using either nix language with flakes, or debian packaging depending on our required target

  • Supporting the expansion of knowledge in Supabase toward our platform release system so that developers can self service more and more over time.

  • Expanding on our github actions, our team tooling, and our testing/release approaches

  • Timely PostgreSQL major, minor, and extension upgrades.

  • Engaging in proactive identification and resolution of production issues in customer deployments.

  • Contributing to the creation/maintaining of best practices, tools, and tests to ensure enhanced stability and decreased deployment risks over time.

What we need

This role demands the following pivotal qualities:

  1. PostgreSQL Expert: A profound understanding of PostgreSQL and its associated tools. Familiarity with extensions, performance optimization, and best practices is essential.

  2. Infrastructure: Proven expertise in infrastructure management, tooling, and optimization.

  3. Self-directed & Initiative: At Supabase, we value independence and proactive problem-solving. We anticipate you to be a dynamic self-starter, thriving in asynchronous collaboration across diverse teams. Your knack for spotting areas of improvement and commitment to realizing those enhancements will be key.

What you’ll do

  • Improve the utility and efficiency of our PostgreSQL offerings.

  • Work with relevant teams to understand the issues around postgres stability, and apply those insights to the build/test/deploy AMI and Docker releases.

  • Contribute to the enhancement of our public GitHub repositories, especially supabase/postgres.

  • Develop and expand tooling and solutions within the Supabase ecosystem.

  • Engage with customers routinely, ensuring our solutions resonate with their needs.

  • Address and resolve GitHub and Support issues.

Must haves

  • 3+ years experience with PostgreSQL and its ecosystem.

  • Knowledge of ansible, Nix package management system (including nix flakes), packer, docker, qemu/kvm, aws, and kubernetes deployments is essential. Need experience with linux and darwin/macos aarch64 targets, as we maintain ability to build for both architectures

  • Must have experience with conventional and nix-packaged builds of C/C++, Go, javascript, and Rust based projects

  • Exposure to public cloud platforms and deployment methodologies.

  • Eagerness to improve and expand our development tools/stack.

  • Comfortable with regular interactions with customers

  • Willingness to work on an “integrated” system and approach to packaging. For many reasons, we cannot apply nix packaging to every component in our stack, nor can we just adopt Nixos in production. We have successfully laid the foundation for integrating conventional and Nix-based systems, with carefully validated choices including using flakes, etc. So, you must be willing to work within and help optimize this paradigm toward our platform development.

  • Must be willing to take on co-responsibility for teaching our engineering team to learn, use and contribute to our Nix-based work, and help troubleshoot and solve issues around the whole platform/postgres stack.

Nice to haves

  • Experience with PostgREST, gotrue/supabase auth, and other Supabase stack components.

  • Contributions to significant, open-source projects in the PostgreSQL domain.

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.

🎯 Who is this job for?

Senior-level candidates are suitable for this role, with 3+ years of PostgreSQL experience and strong expertise in infrastructure, deployment, and production reliability. Required skills include PostgreSQL extensions and optimization, Linux, Nix and flakes, Debian packaging, Ansible, Packer, Docker, QEMU/KVM, AWS, Kubernetes, GitHub Actions, and cross-platform builds for x86_64 and aarch64. Candidates should be familiar with packaging and releasing C/C++, Go, JavaScript, and Rust projects, upgrading PostgreSQL, troubleshooting customer deployments, improving testing and release tooling, and collaborating independently across product, infrastructure, and customer-facing teams.

💬 Potential Interview Questions

How would you package PostgreSQL and its extensions using Nix flakes while integrating conventionally packaged components?

I would define reproducible flake inputs, package metadata, build dependencies, and platform-specific outputs, while consuming Debian or upstream artifacts where Nix packaging is impractical. I would validate ABI compatibility, runtime paths, licensing, and reproducibility in CI.

How would you design a release pipeline for PostgreSQL Docker images and AWS AMIs?

I would build immutable artifacts from pinned sources, run unit, integration, upgrade, and smoke tests, then publish versioned images and AMIs with provenance. Promotion should be staged, observable, and support rollback to the previous known-good release.

What is your approach to PostgreSQL major and minor version upgrades?

Minor upgrades should be tested and rolled out with minimal downtime, while major upgrades require compatibility analysis, extension validation, migration planning, and rollback or restore procedures. I would test realistic workloads and verify logical replication, backups, and application behavior before production rollout.

How would you validate PostgreSQL extensions in a packaged release?

I would build each extension against the target PostgreSQL version and architectures, verify control files and upgrade scripts, and run installation, regression, dump/restore, and upgrade tests. I would also check shared-library dependencies and ensure extensions work consistently in Docker and AMI environments.

How would you make GitHub Actions release workflows reliable and secure?

I would pin actions and dependencies, use least-privilege credentials, separate build and promotion stages, cache safely, and persist test artifacts and logs. Release jobs should be reproducible, idempotent, protected by approvals where appropriate, and capable of generating SBOMs and provenance.

How would you build software for Linux and Darwin on both x86_64 and aarch64?

I would define an explicit build matrix and use native runners or controlled cross-compilation environments, verifying compiler, linker, libc, and SDK differences. Every target would receive automated compilation, packaging, and runtime smoke tests rather than relying only on successful builds.

What would you investigate when a PostgreSQL deployment becomes unstable after an upgrade?

I would compare the release, configuration, extension versions, query plans, resource usage, and kernel or container changes against the previous deployment. I would preserve logs and metrics, reproduce the issue in a representative environment, mitigate customer impact, and document a tested corrective release.

How would you use Packer, Ansible, Docker, and QEMU/KVM together in the deployment process?

Docker would provide application and database image packaging, Packer would produce immutable AMIs, and Ansible would configure systems or orchestrate installation consistently. QEMU/KVM could provide isolated, architecture-specific validation environments for boot, provisioning, and integration tests.

How would you safely roll out a PostgreSQL release to customer deployments?

I would use staged promotion with canaries, health checks, telemetry, backup verification, and explicit compatibility gates for extensions and applications. The rollout should support pause and rollback, with clear customer communication and documented recovery procedures.

How would you help developers self-service PostgreSQL builds and releases?

I would provide documented commands, reusable workflows, local reproduction tools, standardized test harnesses, and clear ownership boundaries. The system should expose useful diagnostics and enforce quality gates automatically while allowing engineers to contribute safely to the public repository.

📋 Job Summary

Supabase, the open-source Postgres development platform, is hiring a Postgres Deployment Engineer for a fully remote, global role. You’ll package, test, deploy, and upgrade PostgreSQL products across Docker images and AWS AMIs while improving release tooling, GitHub Actions, infrastructure reliability, and customer deployments. The stack includes PostgreSQL, Nix and Debian packaging, Linux, Docker, AWS, Kubernetes, Ansible, Packer, QEMU/KVM, and builds for C/C++, Go, JavaScript, and Rust across x86_64 and aarch64. Salary is not disclosed; apply to work asynchronously with an open-source-first team, receive equity, generous benefits, professional development support, and help shape a critical global database platform.

Required Skills

PostgreSQL AWS Kubernetes Docker CI/CD GitHub Go

Never miss a JavaScript opportunity

Subscribe to get similar jobs and weekly insights delivered to your inbox

Hiring JavaScript developers?

Post your job to 9,200+ registered developers. Starting free.

See Pricing

Related jobs

Is this your listing? Claim or request removal