Product Lead - Infrastructure

About [Employer]

[Employer] is the open-source Postgres development platform. 10M+ developers and thousands of enterprises depend on it every day. Database, Auth, Storage, Edge Functions, Realtime and Vector Search run on one platform: the same compute, disks, network and control plane, in each region we operate.

[Employer]'s hardest problems live in that platform. We run millions of databases, and the count compounds each quarter. Our customers range from a developer on a free project to a regulated enterprise that routes traffic through PrivateLink and puts us through a security review before it signs. Reliability, capacity, cost, security and the enterprise features that close deals all come back to the same primitives. We're hiring a Product Lead to own them and build the product team behind them.

About the role

You lead product for the platform under every [Employer] product: compute, disks, networking, the API gateway, capacity and regions. You also own what enterprises build and buy on top of it: read replicas, custom domains, PrivateLink, Bring Your Own Cloud, and the security and compliance controls they need before they sign. You report to the Head of Product, set direction for the platform, and work alongside the leads for our other product lines. You lead the platform's product managers, including our infrastructure product lead, and you hire and develop the PMs who grow the team.

What you'll be responsible for:

• You build and lead the platform product team. You decide how to split the area, hire the PMs who own the rest of it, and coach them to own their roadmaps end to end. You set the bar for their work.
• You decide what gets built, what gets deferred, and what gets cut. Each quarter you choose between enterprise unlocks that open new markets, cost and performance wins for the long tail of projects, and new capabilities that change what [Employer] can run. The priorities are yours, and so is defending them.
• You own reliability and security as product surfaces. You set service levels that track what customers experience and hold teams to them. You decide which security and compliance commitments we make to enterprises, and you show customers what it takes to run millions of databases.
• You talk to customers across the full spectrum: developers running one small project, startups whose bill is mostly compute and disk, enterprise architects running a network or security review, and partners building on [Employer].
• You run the platform's planning. Your PMs write problem statements, requirements and launch metrics before engineering starts. After each launch, you check whether it moved enterprise deal velocity, project economics or platform reliability.
• You keep engineering, design and leadership aligned. The platform sits under each [Employer] product, region and customer tier. You write down what's coming, why, and in what order, and you raise dependencies before they block anyone.

You might be a good fit if you:

• Have 8+ years of product management experience on developer tools or infrastructure, or have founded a company in this space. You can read an architecture doc and hold your own in a design discussion.
• Have built and led a team of product managers. You've hired PMs, grown them into owners of their own areas, and made the hard call when someone wasn't working out. You've led leads who run their own teams. You did it while the product grew from something you could hold in your head to a business where capacity, regions and cost set the limits.
• Have shipped cloud infrastructure as a product. You owned at least one of compute, networking, storage, or multi-region and multi-tenant systems yourself, at a cloud, infrastructure or PaaS company. 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 gap between "works in one region" and "works in twenty." Knowing how enterprises buy and security-review infrastructure (PrivateLink, BYOC, compliance, procurement) is a bonus.
• Move fast and use AI to do it. You'd rather ship something imperfect and learn from it. You hand AI the slow parts of the job (research, drafting, synthesising feedback) and spend your time on judgment calls.
• Build with what you own. You stand up a read replica, put a custom domain in front of a project, route traffic through PrivateLink and deploy onto BYOC. Your opinions come from using the product.
• Work async by default. We're fully remote. You make decisions in writing and move work forward without meetings.

What We Offer

• Fully RemoteWe hire globally. We believe you can do your best work from anywhere. There are no [Employer] offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.
• ESOPEvery team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.
• Tech AllowanceUse this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.
• Health BenefitsSupabase 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-SitesOnce 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 WorkWe operate asynchronously and trust you to manage your own time. You know what needs to be done and when.
• Professional DevelopmentEvery team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.

About the Team

[Employer] 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.