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 https://github.com/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 https://github.com/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.