Software Engineer - Postgres Tooling
- Location
- Remote, Global
- Posted
- November 19, 2026
- Source
- Ashby
Job description
About the Role
We’re looking for a Software Engineer, Postgres Tooling to join our CLI team and help build the open-source tools developers use to change their Postgres schemas safely. You’ll join as a co-maintainer of pg-delta, our schema diff and migration engine, and grow into leading it.
Given two databases, or a database and a folder of SQL files describing the schema you want, pg-delta works out the differences and generates the migration to get from one to the other. It powers supabase db diff , db pull , and declarative schemas, and it runs underneath Supabase’s platform, branching, and AI agent workflows. Every migration it generates is verified on a throwaway clone before it’s trusted, and it’s tested against 331 scenarios on PostgreSQL 14–18. We’re now working toward a stable, standalone 1.0 release for any Postgres developer, on Supabase or not.
This is a correctness-first role. The SQL this tool generates runs against production databases, so privilege safety and avoiding data loss are non-negotiable. It’s a great fit for someone who loves Postgres at the catalog level, enjoys compiler-style problems, and thrives in async, fast-paced environments.
What You’ll Be Responsible For
In this role, you’ll
- Co-maintain pg-delta: review and merge changes, including PRs written by AI agents, and grow into its lead maintainer.
- Own correctness: triage bug reports from GitHub and support, fix diff and dependency-ordering bugs, and extend test coverage across Postgres versions.
- Make sure generated migrations are privilege-safe and never silently lose data, by detecting destructive changes and rewriting them into safe equivalents where possible.
- Help take pg-delta to a stable 1.0: a public API with a semver contract, documentation, and broader coverage of Postgres extensions.
- Work with the open-source community: triage issues, review outside contributions, and say no gracefully when a request doesn’t fit.
- Work with the teams across Supabase that build on pg-delta, so migrations are generated and run the same way everywhere.
- Write the design docs and technical strategy that set the tool’s direction, working async across teams.
- Share the CLI team’s on-call rotation. Weekdays are covered follow-the-sun, and because we ship packaged software that users can roll back, pages are rare.
You Might Be a Good Fit If You
Must have
- Have 8+ years of experience as a software engineer, including deep, hands-on work with PostgreSQL .
- Know Postgres internals at the catalog level: pg_catalog , pg_depend , object ownership, grants and default privileges, RLS policies , and extension membership.
- Understand DDL and migration semantics: which changes take locks, which can’t run inside a transaction, how dependencies determine ordering, and how to spot a destructive change.
- Treat a migration that silently loosens access as a top-severity bug.
- Write strong TypeScript , and design tests for correctness, such as differential, property-based, or corpus testing across multiple Postgres versions.
- Are comfortable with compiler-style problems: dependency graphs, topological ordering, cycle handling, and diffing.
- Can confidently review complex changes in an intricate codebase, including AI-generated PRs.
- Have owned software in production with users in the loop: staged rollouts, error monitoring, and triaging real bug reports.
- Have led a technical project across several teams, from an ambiguous start to production.
- Communicate clearly in writing and thrive in async, globally distributed teams.
Nice to have, roughly in order of how much they’d help
- Have built or maintained schema diff or migration tooling (such as migra, pg-schema-diff, Atlas, pgroll, sqitch, Prisma Migrate, or Flyway/Liquibase), or worked with pg_dump internals.
- Open-source maintainer
experience
API contracts, semver, documentation, and community triage.
- Familiarity with Postgres extensions such as pg_cron, pgmq, pg_partman, vault, pg_net, pgvector, or PostGIS.
- Experience with Go .
- Contributions to Postgres itself, or authorship of a Postgres extension.
- Experience with Supabase or another managed Postgres platform.