Product Manager - Administration & GovernancePosted today

The opportunity

Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.

What you'll do

  • Own the product strategy and roadmap for internal innovation, from a: company’s first IT-approved rollout to adoption across teams and business units.

  • Make getting started self-service, whether someone creates a project in: Supabase, through an internal developer portal, or with an agent. Give builders the access and infrastructure they need without a ticket for every project.

  • Steer scattered usage into a manageable company-wide platform. Give companies: one view of everything they run on Supabase. Shape how ownership, delegated access, and boundaries work so teams can move independently as usage grows.

  • Partner closely with platform, IT, security, and finance teams to understand: what it takes to approve Supabase and keep it approved. Translate their needs into practical identity, policy, audit, and spend controls that don’t slow builders down.

  • Define the path from experiment to production, including project ownership,: access, and the guardrails that change as an application becomes important to the business.

  • Work with Engineering, Design, Sales, and Customer Success to turn early: customer rollouts into a repeatable experience, rather than a new custom integration for every company.

What they're looking for

  • Define what success looks like, instrument it end to end, and let the data: guide what gets built next—from time to first project and self-service adoption to production usage and expansion across the company.
  • Have 7+ years of product management on developer tools, infrastructure, or internal developer platforms.
  • Have built self-service products that developers love and platform or IT: teams trust. You understand both the person trying to ship an app and the team responsible for how it runs.
  • Can reason about identity, permissions, organization boundaries, and usage: attribution, and turn those systems into workflows people can actually understand.