Opportunity

Senior Partner PM at Supabase - Dev Tools Growth in Columbus

Location Columbus
Company Supabase
Source jobicy
Posted 2026-11-06 15:59:11

Career & Market Insight

This is a high-impact, high-ownership role at a late-stage startup (Series F, $1B+ raised) that is squarely in the developer-tools space — one of the fastest-growing and most valued sectors in tech right now. Supabase has 10M+ developers on its platform, giving this PM real scale and visibility.

Career development signals:

  • You'll own the entire partnership lifecycle — architecture, roadmap, quality, and metrics — developing a rare combination of technical PM, platform strategy, and developer relations skills.
  • Deep exposure to auth/identity flows, API design, and machine-to-machine authentication — skills increasingly critical as AI agents proliferate.
  • Working directly with engineering counterparts at strategic partners (think Vercel, Stripe-caliber companies) builds a high-value professional network fast.

Compensation context: No salary is listed, but senior PM roles at a Series F dev-tools company in the Bay Area typically range from $180,000–$260,000 base plus meaningful equity (ESOP is explicitly offered). At this stage, the equity could be substantial.

Green flags: Async culture, genuine technical expectations (not just coordination), product-first success metrics (not commercial), and a company still early enough that your work shapes product direction.

Red flags to probe: "Small number of strategic partners" could mean limited scope if those partners don't grow. The SF travel requirement adds friction for non-Bay Area candidates. Clarify travel frequency expectations before accepting.

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 measuring 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.

  • Are based in the San Francisco Bay Area or can travel there regularly.

  • 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.

  • Are 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

    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.

  • ESOP

    Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we're building together.

  • Tech Allowance

    Use this budget to set up your ideal work environment — laptop, monitor, headphones, or whatever helps you do your best work.

  • Health Benefits

    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.

  • Annual Off-Sites

    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.

  • Flexible Work

    We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.

  • Professional Development

    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.

  • ~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.

Frequently Asked Questions

Is this role truly fully remote or is there an office requirement?
The role is fully remote with no Supabase office, but candidates must be based in or able to travel regularly to the San Francisco Bay Area for partner meetings and collaboration. A global coworking allowance is provided.
What level of technical expertise is required for this product manager role?
You need to be technical enough to participate in architecture reviews, follow code-level design discussions, and hands-on test integrations — such as standing up auth flows and calling APIs. 7+ years in developer tools PM or an ex-founder background is expected.
Does Supabase offer equity to employees?
Yes, every team member receives ESOP (equity ownership) in the company as part of the standard compensation package, in addition to other benefits.
How many partners will I be responsible for in this role?
The role focuses on a "small number" of strategic partners rather than the full partner platform, allowing for deep ownership and accountability over each integration's quality and roadmap.
What does the async work culture look like at Supabase?
Supabase operates async by default — decisions are made in writing and work moves forward without meetings. The team spans 60+ countries, so asynchronous communication is built into how the company functions day to day.
UdreamJob
Curated By

UdreamJob

Remote work & career advice that actually works.

Similar Opportunities