Product Manager - Spark

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 Product Manager, Spark Projects to join our Product Team and lead a new Supabase project type built for how agents use infrastructure.

Agents are creating an unprecedented amount of software, and every app, prototype, preview, and experiment needs a backend from the moment it’s created. Spark projects provision in a second, scale down when idle, and are cheap to enough to use liberally, guilt-free. while keeping the Supabase interface agents already know. Some of these projects will be small and short-lived while others will grow and graduate to larger instances on Supabase. This role owns establishing Spark as the default starting point for agent-built software and how projects grow from an early experiments into production workloads on Supabase.

What You’ll Be Responsible For

Own the product strategy and roadmap for Spark projects, from early MVP through general availability.

Make Spark effortless for agents and the platforms they run on, so a backend exists the moment an idea does.

Define the path from experiment to production, including how projects get claimed, upgraded, and grown into the full Supabase platform.

Shape packaging and pricing with Engineering, Growth, and Finance so Spark is economical at very large scale.

Partner closely with Supabase for Platforms customers to understand their needs and bring Spark to them first.

Define what success looks like, instrument it end to end, and let the data guide what gets built next.

You Might Be a Good Fit If You

Have 5+ years of product management on developer tools or infrastructure, or are an ex-founder with strong product instincts.

Have a strong point of view on agent-driven development and how it changes what developers and platforms need from a backend.

Know your way around AI Evals, controlled experimentation, and data analysis.

Are biased toward speed and would rather ship, learn, and iterate than perfect a spec.

Build with what you own and form opinions through first-hand use.

Use AI tools to compress research, drafting, and feedback synthesis so you can focus on judgment calls.

Work async by default, making decisions in writing in a fully remote team.

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.