Product Manager - Multigres

Supabase Supabase · Data AI · Remote · Product

Product Manager for Supabase's Multigres, a new multi-tenant Postgres architecture. This role owns the full Postgres surface, including Multigres, OrioleDB, Postgres observability, connection pooler, and the Data API. The PM will talk to developers, lead Multigres to production adoption, define requirements and success metrics, prioritize across engineering teams, and align the roadmap. The role requires 7+ years of PM experience on developer tools or ex-founder experience, technical aptitude, and a bias for speed. Familiarity with Postgres is a bonus. The company uses AI tools to move faster.

What you'd actually do

  1. Talk to developers across the full spectrum. Startups shipping their first AI app, enterprises migrating off managed databases, engineers debugging connection pool exhaustion at 3am. Find the real blockers and bring them into every prioritisation and scoping call.
  2. Lead Multigres to production adoption. Define what success looks like for customers: the migration path, the rollout story, and the metrics that confirm it's working. Multigres is Supabase's biggest infrastructure bet; you own whether it lands.
  3. Own the problem definition, requirements, and success metrics for every capability we ship. Surface feasibility, migration complexity, and rollout risk before engineering commits. Set the metric before the team starts building, then track it after launch.
  4. Prioritise across competing surfaces. Every quarter you're choosing between platform reliability investments, developer-experience improvements, and enterprise requirements across five engineering teams. Make the call and defend it.
  5. Keep engineering, design, and leadership aligned on the roadmap. Postgres sits under Auth, Storage, Realtime, and every other Supabase product. Communicate what's coming, why, and in what order, to five engineering teams and the rest of the company.

Skills

Required

  • 7+ years of product management experience on developer tools
  • Technical enough to read an architecture doc, follow a design discussion, and ask the right questions
  • Shipped products where the database behavior is the experience
  • Biased toward speed
  • Work async by default

Nice to have

  • Familiarity with the Postgres ecosystem (extensions, tooling, community)

What the JD emphasized

  • Multigres
  • Postgres
  • developers
  • engineering teams