Product Manager - Strategic Partner Integrations (Bay Area based)

Supabase; United States; A distancia; USD 140.000 - 210.000; Jornada completa

Ventajas ofrecidas por este puesto de trabajo

Fully Remote

ESOP

Tech Allowance

Health Benefits

Annual Off-Sites

Flexible Work

Professional Development

Descripción de la vacante

Supabase is seeking a senior product leader to own a focused portfolio of strategic Partners and drive high-quality integrations on our developer platform. You will work closely with developers and Partner teams to shape roadmaps, balance ownership and openness, and ship end-to-end solutions that scale with adoption.

The role requires hands-on collaboration in architecture discussions, strong API/identity flow experience, and a bias toward shipping iteratively in a fully remote environment.

Formación

• 7+ years of product management on developer tools.
• Experience shipping APIs, auth or developer-facing platform surfaces end-to-end.
• Ability to read architecture docs and participate in design discussions.
• Comfort with async, written communication and remote collaboration.

Responsabilidades

• Own a focused portfolio of strategic Partners and ensure high-quality integrations.
• Stay close to developers, gather feedback, and translate it into the roadmap.
• Decide the right integration model and align roadmaps with Partners.
• Collaborate with Partner teams to ship integrations and participate in architecture reviews.
• Set quality bars and build docs, tooling, and guardrails to scale adoption.
• Define success metrics and drive adoption and reliability.

Conocimientos

Product management

Developer tools

Architecture reading

Ex-founder

API integration

Herramientas

APIs

Descripción del empleo

About Supabase

Supabase is the Postgres development platform, built by developers for developers. We provide a complete backend solution including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search. All services are deeply integrated and designed for growth.

More than 10 million developers build on it, from solo founders shipping over a weekend to teams and builders via Vercel, Lovable and Stripe, and every one of them reaches Supabase through a surface: an API, an auth flow, an SDK, or a Partner’s product with Supabase integrated.

The current and next wave of software leans on those surfaces harder than any before it.

Agents now act on behalf of developers and end users, authentication has to work machine-to-machine as seamlessly as it once worked human-to-human, and independent platforms increasingly need to authenticate, delegate, and coordinate with each other without a person in the loop. For a platform built on Postgres with Auth, Compute, Storage and generated Data APIs at its core, the surfaces where Supabase meets Partners and their systems are some of the most important avenues that we own - this role owns these surfaces.

This role owns a focused portfolio of those Partners. Not the platform as a whole, but a small number of strategic Partners whose integrations you are accountable for making excellent. Success here is a product measure, not a commercial one: the integration is high quality, the developers who use it are well served, and it keeps improving. That means living close to those developers, obsessing over where the integration fails them, and turning what you learn into the roadmap. It is a product and engineering job first, because the best integrations are won in architecture reviews and pull requests, not in meetings.

What You’ll Be Responsible For

• Owning the success of a focused portfolio of strategic Partners, a small number of them rather than the platform as a whole. You are accountable for the outcome of each partnership: a high-quality integration that the developers who use it reach for, and that keeps getting better.
• Living close to the developers who use these integrations. Talking to them constantly, finding where each integration breaks down in real use, and building the roadmap from that signal rather than from a Partner’s wishlist.
• Deciding the right integration model for each Partner: what Supabase owns, what the Partner owns, what you build jointly, and what stays open and Partner-agnostic, reading whether the two roadmaps run together or diverge and choosing accordingly.
• Working hands-on with each Partner’s product and engineering counterparts to ship. Holding your own in an architecture review and a code-level design discussion, and turning strategy into shipped, high-quality integrations rather than long conversations.
• Setting the quality bar for what a great integration looks like, and building the mechanisms (documentation, tooling, guardrails, versioning) that hold every Partner to it as adoption scales.
• Defining what success looks like for each integration and measure it honestly: adoption by the developers who use it, integration quality, and reliability in real use. Using those signals to decide how deep to go with each Partner and where to push the integration next.

You Might Be a Good Fit If You:

• Have 7+ years of product management on developer tools, or are an ex-founder with strong product instincts, and are technical enough to read an architecture doc, follow a design discussion, and ask the right questions.
• Have shipped integration or platform surfaces that other companies’ systems build against, owning APIs, auth or identity flows, or developer-facing platform surfaces end to end, and can reason at the product level about how two independent systems should authenticate and exchange data: where to be open, where to be strict, and where trust lies in these integrations. Familiarity with more recent primitives like workers/agent sandboxes and developer-tooling products, or with machine-to-machine authentication, is a bonus.
• Are biased toward speed, and would rather ship something imperfect (but secure) while learning than spend another month polishing a spec.
• Build with what you own, using the surfaces on your roadmap the way a Partner would: standing up an auth flow, calling the Data API, deploying a database, wiring Supabase into another product. You form opinions through first-hand use.
• Comfortable using AI tools to compress the slower parts of the role, like research, drafting, and synthesising feedback, so you spend more time on judgment calls.
• Work async by default. Supabase is fully remote, so you make decisions in writing and move work forward without meetings.

What We Offer

• Fully Remote
• ESOP
• Tech Allowance
• Health Benefits
• Annual Off-Sites
• Flexible Work
• Professional Development

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.

• ~400 team members
• 60+ countries
• 20+ languages spoken
• Over $1B raised (including our $500M Series F)
• 540,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.