Product Manager - AI at Supabase
Ideal for a technical product manager with over seven years of experience in developer tools or an ex-founder with strong product instincts. You should have a c
Work type: remote
Location: Remote
Type: Full-time
Summary
Ideal for a technical product manager with over seven years of experience in developer tools or an ex-founder with strong product instincts. You should have a clear point of view on how infrastructure can be optimized for AI agents and a desire to build in a remote-first, async-heavy environment.
**Key highlights**
Supabase is hiring a fully remote product manager to own the strategy for AI agent tooling and MCP servers. You will receive equity ownership through an ESOP program and a tech allowance to support your remote workspace while influencing the roadmap for a platform used by millions of developers.
**You might be a good fit if you...**
- Use AI coding tools daily and understand the technical primitives required for agent-native products.
- Can interpret architecture documentation and engage in high-level technical discussions with engineers.
- Prefer shipping imperfect iterations to gather real-world feedback over spending excessive time on perfect specifications.
- Have experience defining success metrics for developer-facing products and tracking performance post-launch.
Job Description
## About the role:
Supabase is the backend more than 7 million registered developers reach for when they want to ship fast: database, auth, storage, and APIs in one platform. AI coding assistants now account for a meaningful share of the development happening on Supabase: agents writing migrations, provisioning infrastructure, and querying databases through the [MCP server](https://supabase.com/docs/guides/ai-tools/mcp) and [agent skills](https://supabase.com/docs/guides/ai-tools/ai-skills). When agents have the wrong context or defaults, the result is a broken schema or a misconfigured policy. Getting the abstractions right is the whole job. You own the MCP server, agent skills, and the evals that tell you whether any of it is working.
## What You'll Be Responsible For:
- Rethink the PM job when most users are agents. Defaults, error messages, breaking changes, naming, deprecations, docs: every product decision behaves differently when an AI coding tool sees it before a human does. Apply that lens to your own roadmap and to product decisions across Supabase.
- Talk to customers across the full spectrum. Indie developers shipping side projects, startups choosing an AI stack, enterprise teams running agents in production. Find the blockers and bring them back to the roadmap.
- Own the problem statement and requirements behind every agent tooling bet. Define what we're building and why before engineering picks up a spec. Capture the evidence behind each decision, name the constraints, and give the team a target it can hit.
- Decide what gets built, what gets deferred, and what gets cut. Every quarter you're choosing between agent plugin requests, MCP improvements, discoverability work, and reliability — and defending those calls when stakeholders push back.
- Define how each launch is measured before it ships. Set the metric before engineering starts: developer activation, task completion, and AI eval scores. Track whether it moved after launch and use that to sharpen the next call.
- Keep engineering, design, and leadership aligned. Agent tooling spans the MCP server, CLI, SDK, and dashboard. Communicate the roadmap, surface dependencies early, and keep stakeholders pointed in the same direction.
## You Might Be A Good Fit If You:- Have 7+ years of product management experience on developer tools, or an ex-founder with strong product instincts. You're technical enough to dive in: read an architecture doc, follow a design discussion, ask the right questions.
- Have a clear point of view on what makes infrastructure agent-friendly. You use AI coding tools and agent harnesses daily, track what Anthropic, OpenAI, and the AI community ship week to week, and have opinions about the primitives developers need to build agent-native products. You've shipped something that put those opinions to the test.
- Are biased toward speed. You'd rather ship something imperfect and learn than spend another sprint refining a spec. You know when to stop planning and start building.
- Build with what you own. You use the products on your roadmap: connecting to Supabase through the MCP server, building with the CLI, testing how agents respond to different tool configurations. You develop opinions through first-hand use.
- Use AI to move faster. You use AI tools for research, drafting, and synthesising feedback. More time goes to judgment calls.
- Work async by default. Supabase is fully remote. You make decisions in writing and move threads forward without meetings.
### What We Offer
We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.
Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.
Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.
Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family’s health are important to us.
Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It’s a highlight of our year.
We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.
Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.### About the Team
Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.
- 500,000+ community members
We move fast, build in public, and use what we ship. If it’s in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support—not replace—existing tools and communities.### Hiring Process
We keep things simple, async-friendly, and respectful of your time:
1. Apply – Our team will review your application.
2. Intro Call – A short video chat to get to know each other.
3. Interviews – Up to four calls with:
4. Team Leads
5. Future teammates
6. Someone cross-functional from product, growth, or engineering (depending on the role)
7. Someone from our leadership/founding team
8. Decision – We may follow up with a final question or go straight to offer.
All communication is remote and we aim to move fast.
View this job on nocollar jobs