OrioleDB Developer (AMER)Active

The opportunity

We're looking for an engineer to drive the evolution of OrioleDB and its collaboration with the upstream PostgreSQL community. OrioleDB is a next-generation storage engine for PostgreSQL, and this role sits at the intersection of database internals, open source community work, and Supabase's managed Postgres platform.

What you'll do

  • New OrioleDB features. Design and implement new capabilities in OrioleDB —: for example, native index access methods (GiST, GIN, HNSW for pgvector), disaster recovery tooling, and other storage-engine-level features that expand what OrioleDB can do.

  • Stability. Strengthen OrioleDB's reliability through deeper test coverage,: fault injection, crash and recovery testing, and improvements to CI infrastructure. Ensure regressions are caught early and that OrioleDB behaves predictably under stress, replication, and failure scenarios.

  • Upstream collaboration. Contribute changes directly to PostgreSQL core. Part: of OrioleDB lives as a patch on top of PostgreSQL — moving the right pieces upstream shrinks what we maintain ourselves and benefits the wider community. This happens through PostgreSQL's open development process: the pgsql-hackers mailing list, public code review, and commitfests.

  • Supabase integration. Work with Supabase's Postgres team to ensure OrioleDB: fits naturally into Supabase's managed offering and roadmap.

  • Design, implement, and test new OrioleDB features and integrate them cleanly: with PostgreSQL's planner, executor, and surrounding subsystems.

  • Build out and maintain test infrastructure: regression suites, fuzzing, randomized testing, crash and recovery testing, and CI pipelines.

What they're looking for

  • Identify and prepare patches suitable for upstreaming to PostgreSQL core.
  • Improve performance, resilience, monitoring, and operational tooling for production use.
  • Debug and resolve complex issues in low-level C code, including in storage,: replication, indexing, and query execution paths.
  • Participate in design discussions, architecture reviews, and code reviews —: both inside Supabase and in the PostgreSQL community.