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.
Define how each launch is measured before it ships. Set clear goals that measure how a change actually moves developer activation, docs comprehension, agent task success, or API adoption.
Keep engineering, design, and leadership aligned. 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. Technical enough to read an architecture doc, follow a design discussion, and ask the right questions.
Shipped a public SDK, CLI, dashboard, or API that external developers depend on. Equally adept at API design, docs IA, and dashboard flows.
Understand the landscape is evolving. Familiar with how coding agents (such as Claude, Codex and Cursor) consume SDKs, docs, and APIs, and how to optimize for developers using them.
Biased toward speed. Ship something imperfect and learn rather than spend another sprint refining a spec.
Build with what you own. Install the CLI, call the Management API, read the docs end-to-end, and write real code against supabase-js.
Use AI to move faster. Use AI tools to compress the slow parts of the job and have real opinions on what makes an interface agent-friendly.
Work async by default. Make decisions in writing and move work forward without meetings.