Software Engineer - Branching

We’re building a high-performance CI/CD execution platform similar to runners used by tools like Buildkite, GitHub Actions, and Blacksmith CI. Our platform executes developer pipelines reliably at scale, integrates deeply with source control, and automates build, test, and deployment workflows.

In this role, you will design and build the distributed systems responsible for running CI/CD pipelines securely and efficiently. This includes orchestrating ephemeral compute environments, managing build isolation, scheduling jobs across fleets of workers, and ensuring reliability at scale.

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

• Design and improve the core orchestration engine that manages the lifecycle of creating, merging, and rebasing Supabase Branches.

• Provision ephemeral sandboxed execution environment on EKS / ECS for running untrusted build workloads from connected git repositories with securely managed secrets.

• Implement job scheduling that scale to thousands of concurrent builds.

• Optimize and reduce pipeline runtimes with caching, artifact storage, and dependency reuse.

• Manage retry, timeout, cancellation, and failure-propagation logic to ensure pipelines behave predictably under failure conditions.

• Instrument the full pipeline lifecycle with observability tooling to surface traces, metrics, and structured logs to the end user.

• Develop configuration files (JSON / TOML) and integrations (Terraform / Pulumi) that allow teams to easily define, trigger, and inspect pipelines in code.

You Might Be a Good Fit If You

• Have strong software engineering skills (Go and Typescript required);

• Have 3+ years of experience building and operating cloud infrastructure or distributed systems at scale;

• Have cloud Infrastructure knowledge - familiarity with AWS constructs is required, past experience using the AWS SDKs and IaC tools (Pulumi, Terraform, etc) to build and operate infrastructure is strongly preferred.

• Have a production operations mindset - track record of building reliable, observable, and maintainable systems

• Have an ownership mindset - you thrive in being able to operate independently with high-level guidance

• Communicate clearly across both technical and non-technical audiences

• Have experience in async or globally distributed teams

• Are energized by solving real-world problems for developers

• Are comfortable navigating ambiguity and moving quickly

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.