The opportunity
Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.
What you'll do
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.
What they're looking for
- 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.
