What you'll work on

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.

You Will

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.
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.
Write clear technical documentation, design notes, and upstream proposals.
Have co-responsibility for troubleshooting, analyzing, supporting and maintaining OrioleDB Postgres and bundled extensions in production deployments. This can include answering support ticket requests, an on-call rotation, and supporting our team members in troubleshooting and fixing live customer production databases.

An existing PostgreSQL core contributor or have equivalent experience in Database internals.
An expert C programmer with 8+ years of production experience with focus on low-level systems programming.
Deeply familiar with PostgreSQL’s codebase, build system, and extension APIs.
Have experience designing or implementing database storage engines, index structures, or query execution components.
Comfortable contributing to community‑driven, upstream open source projects.
Proficient in debugging and profiling complex C code in a database context.
Able to write clear technical documentation and explain design trade‑offs.
A strong communicator, committed to an open and collaborative development process.