Software Engineer - Functions (Compute)

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.

Compute is our newly launched microVM architecture for running agentic workloads, operating alongside our existing Edge Functions service for server-side TypeScript functions distributed globally at the edge.

We want developers to be able to build truly global applications by distributing both compute and data globally. Infrastructure concerns like regions, cold starts, CPU and memory provisioning should fade into the background so developers can focus on iterating on business logic, and fast, flexible runtimes a growing range of agent-driven code.

We are looking for experienced and passionate engineers to help us go further in this vision.

What You’ll Own

• Help build & architect the Supabase Compute platform, built on Firecracker microVMs.

• Implementing monitoring, alerting, and OpenTelemetry tracing across the runtime, then using that visibility to drive optimizations that improve latency and reliability of the service.

• Working closely with the Firecracker, Deno, and other open-source teams, contributing to upstream and relaying our users' requirements.

• Participating in an on-call rotation to keep Compute healthy in production.

• Help manage and improve features like scheduled functions, background tasks, WebSockets streaming, ephemeral file storage, and custom routing.

• Integrating Compute more tightly with the rest of the Supabase stack — Auth, Postgres, Storage, and Realtime.

• Expanding the Compute runtime to support more use cases (AI inference, MCP servers, hosting simple websites, URL shorteners).

• Improving the DX of developing and debugging Compute locally through the Supabase CLI, including DevTools integration, logging, and production parity.

What You’ll Bring

• At least 5 years of backend or systems engineering experience, with strong fluency in Rust and TypeScript.

• Experience with Firecracker, V8 Isolates, Deno, and related runtime isolation technologies .

• Experience operating infrastructure at scale — Kubernetes, AWS (EC2/Lambda/MicroVM), Cloudflare Workers, Redis, or comparable systems.

• A strong vision for how compute and data can be pushed to the edge.

• Bonus: experience building developer-facing CLIs or front-end tooling that sits on top of an infrastructure product.

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.