The opportunity
We’re hiring a Product Manager to own the platform primitives every Supabase product runs on, including internal features like compute , disks , networking, and the API gateway, and external features like read replicas , custom domains , PrivateLink , and Bring Your Own Cloud.
What you'll do
Talk to customers across the full spectrum. Indie developers running a single: nano project, fast-growing startups whose costs are dominated by compute and disk, enterprises walking through a network-architecture review, and partners building on top of Supabase. Find the real blockers and bring them back to the roadmap.
Own the problem statement and requirements behind every platform bet. Capture: the customer evidence behind each decision, name the cost, capacity, and reliability constraints, and give the team a target it can hit.
Decide what gets built, what gets deferred, and what gets cut. Every quarter: you're choosing between enterprise unlocks blocking deals, reliability and cost wins for the long tail of projects, and net-new capabilities that change what Supabase can run. Set the priorities and defend them.
Define how each launch is measured before it ships. Set the metric, agree on: the threshold, and track it after launch. Know whether a feature moved enterprise deal velocity, project economics, or platform reliability. Use that to sharpen the next call.
Keep engineering, design, and leadership aligned. The platform touches every: other Supabase product, every region, and every customer tier. Write the roadmap, surface dependencies before they become blockers, and keep decisions moving.
Have 7+ years of product management experience on developer tools, or an: ex-founder with strong product instincts. You're technical enough to dive in: read an architecture doc, follow a design discussion, ask the right questions.
What they're looking for
- Have shipped cloud infrastructure as a product. You've owned at least one of: compute, networking, storage, or multi-region/multi-tenant systems at a cloud, infra, or PaaS company. You understand the tradeoffs well enough to judge them: instance sizing and capacity, disk and storage economics, scale-to-zero vs. always-on, single-tenant vs. shared, the gap between "works in one region" and "works in twenty." Familiarity with how enterprises buy infrastructure (PrivateLink, BYOC, procurement) is a bonus.
- Are biased toward speed. You'd rather ship something imperfect and learn than: spend another sprint refining a spec.
- Build with what you own. You run real workloads on the products you own: standing up a read replica, putting a custom domain in front of a project, terminating traffic through PrivateLink, deploying onto BYOC.
- Use AI to move faster. You use AI tools to cut the slow parts so more time goes to judgment calls.
