Supabase is a company that runs Postgres for over 7 million developers, providing a robust foundation for various applications. The Product Manager for the Postgres Platform will be responsible for leading the adoption of Multigres, defining success metrics, and prioritizing across competing engineering demands to ensure alignment and successful product delivery.
Responsibilities:
- 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
- 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
- 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
- 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
- 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
Requirements:
- 7+ years of product management experience on developer tools, or an ex-founder with strong product instincts
- Technical enough to read an architecture doc, follow a design discussion, and ask the right questions
- Shipped products where the database behaviour is the experience
- Knowledge of how connection limits, query planning, and extension behaviour translate to customer pain
- Familiarity with the Postgres ecosystem (extensions, tooling, community) is a bonus
- Biased toward speed; prefer to ship something imperfect and learn rather than spend another sprint refining a spec
- Ability to know when to stop planning and start building
- Use the products on your roadmap: running queries, testing the connection pooler, prototyping against the Data API
- Develop opinions through first-hand use
- Use AI tools to compress the slow parts of the job (research, drafting, synthesising feedback)
- Work async by default; make decisions in writing and move work forward without meetings