Product Manager - Interfaces

What you will do

• Talk to customers across the full spectrum. From indie developers wiring up a side project, to AI-native platforms generating Supabase apps for their own users, and to enterprise teams integrating the Management API into their internal control planes, you will find the real blockers and ensure we are building the right things, in the right order.
• Own the problem statement and requirements behind every interface bet. Define what we should build next (and why) to make Supabase the best developer experience in the world, collaborating closely with Engineering and Design.
• Set the bar for what "agent-friendly" means on Supabase. Decide how the SDK reads to a coding agent, how the docs are retrieved and quoted, how APIs are discovered, and how the CLI behaves when something automated is driving it. For you "AI-friendly" will not be a slogan but a reality, proven by specific changes you mill make and measure.
• Define how each launch is measured before it ships. You will set clear goals that measure how a change actually moves developer activation, docs comprehension, agent task success, or API adoption—and you’ll use that insight to guide what we do next.
• Keep engineering, design, and leadership aligned. Engineering and design teams across every Supabase surface ship into the experience you own. Communicate what's coming, why, and in what order, and make sure it feels like one product, not five.

Who you are

• 7+ years of product management experience on developer tools, or an ex-founder with strong product instincts. You're technical enough to read an architecture doc, follow a design discussion, and ask the right questions.
• You've shipped a public SDK, CLI, dashboard, or API that external developers depend on. Not features that happened to touch an SDK; you owned the surface. You’re equally adept at API design, docs IA, and dashboard flows, and you've made the trade-offs between them in production.
• You understand the landscape is evolving. You’re familiar with how coding agents (such as Claude, Codex and Cursor) consume SDKs, docs, and APIs, and how to optimize for developers using them.
• You're biased toward speed. You'd rather ship something imperfect and learn than spend another sprint refining a spec.
• You build with what you own. You install the CLI, call the Management API, read the docs end-to-end, and write real code against supabase-js. You develop opinions through first-hand use, not screenshots.
• You use AI to move faster. You use AI tools to compress the slow parts of the job (research, drafting, synthesizing feedback) so you spend more time on judgment calls, and you've built enough with agents to have real opinions on what makes an interface agent-friendly.
• You work async by default. Supabase is fully remote. You make decisions in writing and move work forward without meetings.