About the role
Supabase is the open-source Postgres development platform. Over 7,000,000 developers — from indie hackers to teams inside Wells Fargo, Coinbase, Audi, and Capital One — build on Supabase, meeting the product through five surfaces: the SDKs, the docs, the dashboard, the Management API, and the CLI.
These interfaces now have a second audience: coding agents. Claude, Codex, Lovable, Bolt, and more now read the docs, call the SDKs, use the APIs, and drive the CLI on behalf of developers. As the PM for these surfaces, you will define how Supabase can be as readable, predictable, and trustworthy as possible, both to humans and agents alike.
What You Will Do:
Talk to customers across the full spectrum — from indie developers to AI-native platforms to enterprise teams — to find real blockers and ensure the right things are being built in the right order
Own the problem statement and requirements behind every interface bet, defining what to build next and why, in close collaboration with Engineering and Design
Set the bar for what "agent-friendly" means on Supabase — deciding how the SDK reads to a coding agent, how docs are retrieved and quoted, how APIs are discovered, and how the CLI behaves when automated
Define how each launch is measured before it ships, setting clear goals around developer activation, docs comprehension, agent task success, or API adoption
Keep engineering, design, and leadership aligned across every Supabase surface, communicating what's coming and why so it feels like one product
What we're looking for
7+ years of product management experience on developer tools, or an ex-founder with strong product instincts; technical enough to read an architecture doc and follow a design discussion
Have shipped a public SDK, CLI, dashboard, or API that external developers depend on — owning the surface, not just touching it; adept at API design, docs IA, and dashboard flows
Understand 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 — prefer shipping something imperfect and learning over endlessly 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 — compress research, drafting, and synthesis so more time goes to judgment calls; have built enough with agents to have real opinions on agent-friendly design
Work async by default — Supabase is fully remote, decisions made in writing, work moves forward without meetings