The opportunity
You own the platform primitives every Supabase product runs on: compute, disks, networking, the API gateway, capacity and regions. You own the enterprise surfaces built on top of them too, including read replicas , custom domains , PrivateLink and Bring Your Own Cloud.
What you'll do
You talk to customers across the full spectrum. Developers running a single: small project, growing startups whose bill is mostly compute and disk, enterprises walking through a network architecture review, and partners building on top of Supabase.
You own the problem statement and requirements behind every platform bet. You: define what we're building and why before engineering starts, name the cost, capacity and reliability constraints, and keep that clarity current through execution.
You decide what gets built, what gets deferred, and what gets cut. Every: quarter you're choosing between enterprise unlocks that open new markets, cost and performance wins for the long tail of projects, and net-new capabilities that change what Supabase can run. The priorities are yours, and so is defending them.
You own reliability as a product surface. You set service levels that track: what customers experience, hold teams to them, and show customers what it takes to run millions of databases.
You define how each launch is measured before it ships. The metric, the: threshold and the read afterwards are yours: whether a launch moved enterprise deal velocity, project economics, or platform reliability.
You keep engineering, design and leadership aligned. The platform touches: every other Supabase product, every region and every customer tier. You write down what's coming, why, and in what order, and you surface dependencies before they become blockers.
What they're looking for
- Have 8+ years of product management experience on developer tools, or are an: ex-founder who has built in this space. You're technical enough to read an architecture doc and follow a design discussion.
- Have shipped cloud infrastructure as a product. You've owned at least one of: compute, networking, storage, or multi-region and multi-tenant systems at a cloud, infrastructure or PaaS company, as the owner rather than a neighbouring team. You can judge the tradeoffs: instance sizing and capacity, disk and storage economics, scale-to-zero versus always-on, single-tenant versus shared, and the distance between "works in one region" and "works in twenty." Familiarity with how enterprises buy infrastructure (PrivateLink, BYOC, procurement) is a bonus.
- Have grown with an infrastructure product. You've owned infrastructure small: enough to hold in your head, and stayed with it until capacity, regions and cost became the real constraints.
- Are biased toward speed. You'd rather ship something imperfect and learn from it.
