OrioleDB开发工程师
OrioleDB Developer
关于 Supabase
Supabase 是一个基于 Postgres 的开发平台，由开发者为开发者打造。我们提供完整的后端解决方案，包括数据库、认证、存储、边缘函数、实时功能和向量搜索。所有服务深度集成，专为成长而设计。
关于该职位
我们正在寻找一名工程师，推动 OrioleDB https://www.orioledb.com 的发展及其与上游 PostgreSQL 社区的合作。OrioleDB 是 PostgreSQL 的下一代存储引擎，该职位位于数据库内部、开源社区工作和 Supabase 的托管 Postgres 平台的交汇点。
由于生产支持和值班职责，该职位需要与美洲时区有较强的重叠时间。
你将参与的工作
- 新的 OrioleDB 功能。在 OrioleDB 中设计并实现新功能——例如，原生索引访问方法（GiST、GIN、pgvector 的 HNSW），灾难恢复工具，以及其他扩展 OrioleDB 能力的存储引擎级功能。
- 稳定性。通过更深入的测试覆盖率、故障注入、崩溃和恢复测试，以及 CI 基础设施的改进，增强 OrioleDB 的可靠性。确保回归问题尽早被发现，并确保 OrioleDB 在压力、复制和故障场景下行为可预测。
- 上游协作。直接向 PostgreSQL 核心提交更改。OrioleDB 的一部分作为 PostgreSQL 的补丁存在——将合适的部分向上游移动可以减少我们维护的内容，并使更广泛的社区受益。这通过 PostgreSQL 的开放开发流程实现：pgsql-hackers 邮件列表、公开代码审查和 commitfests。
- Supabase 集成。与 Supabase 的 Postgres 团队合作，确保 OrioleDB 自然地融入 Supabase 的托管产品和路线图。
你将：
- 设计、实现和测试新的 OrioleDB 功能，并将其干净地与 PostgreSQL 的规划器、执行器和周围子系统集成。
- 构建和维护测试基础设施：回归套件、模糊测试、随机测试、崩溃和恢复测试，以及 CI 管道。
- 识别并准备适合向 PostgreSQL 核心上游提交的补丁。
- 提升性能、弹性、监控和生产使用的操作工具。
- 调试和解决低级 C 代码中的复杂问题，包括存储、复制、索引和查询执行路径。
- 参与设计讨论、架构评审和代码审查。
查看英文原文
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 an engineer to drive the evolution of OrioleDB https://www.orioledb.com 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.
This role requires strong working overlap with Americas time zones due to production support and on-call responsibilities.
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.
- Contribute to troubleshooting, analyzing, supporting and maintaining OrioleDB 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.
YOU ARE:
- 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.
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.