Product Lead, Infrastructure

ABOUT SUPABASE Supabase is the open-source Postgres development platform that 10M+ developers and thousands of enterprises depend on every day. Database, Auth, Storage, Edge Functions, Realtime and Vector Search all run on one platform: the same compute https://supabase.com/docs/guides/platform/compute-add-ons, the same disks https://supabase.com/docs/guides/platform/database-size, the same network and control plane, in every region we operate. Supabase's hardest problems live in that platform. Millions of databases, growth that compounds every quarter, and a customer base running from a developer on a free project to a regulated enterprise routing traffic through PrivateLink https://supabase.com/docs/guides/platform/privatelink. Reliability, capacity, cost and the enterprise features that close deals all come back to the same primitives. We're hiring a Product Lead to own them. ABOUT THE ROLE 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 https://supabase.com/docs/guides/platform/read-replicas, custom domains https://supabase.com/docs/guides/platform/custom-domains, PrivateLink and Bring Your Own Cloud. You report to the Head of Product and set direction for the whole area alongside the leads for our other product lines. You're the only product person on the platform today, and the team grows under you as the area does. WHAT YOU'LL BE RESPONSIBLE FOR: - 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. YOU MIGHT BE A GOOD FIT IF YOU: - 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. - Build with what you own. You stand up a read replica, put a custom domain in front of a project, terminate traffic through PrivateLink, deploy onto BYOC. You develop opinions through first-hand use. - Use AI to move faster. You lean on AI for the slow parts of the job (research, drafting, synthesising feedback) so you spend more time on judgment calls. - Work async by default. We're fully remote. You make decisions in writing and move work forward without meetings. 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.