Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
OrioleDB Deployment Engineer
- Remote from
- 🌐 Anywhere
- Salary
- Undisclosed
- Department
- DevOps & Infrastructure
- Employment
- Full Time
- Experience
- Open level
- Published
- Apply before
- 6 Dec 2026
- Listing views
- 15
- Application actions
- 0
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
About this role.
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 OrioleDB Deployment Engineer to join our OrioleDB Team and help elevate our OrioleDB offering. You’ll work closely with the OrioleDB team, playing an instrumental role in technical decision-making and refining internal methodologies.
This role is ideal for someone who thrives in async, fast-paced environments and is excited about building developer tools that scale to millions.
What You’ll Be Responsible For
Package software into our
supabase/postgresrepo using Nix (with flakes), and help us transition our packaging from traditional to Nix packaging more over time.Manage OrioleDB release lifecycles, ensuring timely major, minor, and extension upgrades.
Expand platform release systems to allow developers to increasingly self-service.
Optimize CI/CD and tooling, specifically expanding GitHub Actions, team tooling, and testing/release approaches.
Resolve production issues by proactively identifying and fixing problems in customer deployments.
Maintain best practices and tests to ensure enhanced stability and decreased deployment risks.
co-owning the integration of OrioleDB into the supabase product
You Might Be a Good Fit If You
Have 3+ years of experience with PostgreSQL and its ecosystem, including extensions and performance optimization.
Are an Infrastructure Expert with proven experience in management, tooling, and optimization.
Are proficient in the Nix package management system (including flakes) alongside Ansible, Packer, Docker, QEMU/KVM, AWS, and Kubernetes.
Have experience building for multiple architectures, specifically Linux and Darwin/macOS aarch64 targets.
Are comfortable with polyglot environments, including builds for C/C++, Go, JavaScript, and Rust-based projects.
Communicate clearly across both technical and non-technical audiences, especially when interacting with customers.
Have experience in async or globally distributed teams and value independent, proactive problem-solving.
Are willing to mentor, taking on responsibility for teaching the engineering team to use and contribute to our Nix-based work.
Have experience with integration of emerging features into widely used managed hosted product platforms
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.
200+ team members
40+ countries
15+ languages spoken
$496M raised
430,000+ community members
30,000+ memes posted (and counting)
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.
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.
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
4/5Autonomy Level
5/5Communication Load
4/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would first map current build inputs, dependencies, artifacts, and release steps. Then I would create reproducible Nix derivations and flakes for the highest-value components, validate them in CI across supported architectures, and migrate incrementally while retaining a rollback path. Documentation and reusable templates would help other engineers adopt the workflow.
I would define versioned release criteria, automated compatibility tests, upgrade and rollback procedures, artifact provenance, and staged rollout checks. I would also automate release notes and validation through CI, monitor post-release health signals, and maintain clear ownership for major, minor, and extension upgrades.
I would begin by assessing impact, gathering relevant logs, deployment versions, configuration, and database metrics, then attempt to reproduce the issue in a controlled environment. I would communicate status and mitigations clearly, identify the root cause, deploy a tested fix or workaround, and add regression coverage plus operational documentation.
I would use a reproducible build definition with platform-specific inputs isolated where necessary. CI would build and test each target independently, verify dependency availability and binary compatibility, and publish artifacts only after architecture-specific validation. I would also document local development paths for both platforms.
I would pair practical enablement with small adoption steps: clear examples, starter templates, focused documentation, and short working sessions tied to real team tasks. I would encourage contributions through review feedback and make common workflows easy to run in CI, so learning produces immediate operational value.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
