Product Manager - Branching

Supabase · Remote, AnywhereRemotesenior

In short

▸Liderar el flujo de desarrollo desde local hasta producción con branch por PR, integración con GitHub y entornos aislados.
▸Ser el dueño del producto para equipos de todos los tamaños: indie devs, startups y empresas.
▸El rol es clave para hacer que las herramientas de desarrollo de Supabase funcionen bien tanto para humanos como para agentes autónomos.

English proficiency required for cross-team collaboration and documentation

In ~1 minute you get: who interviews you, the likely questions answered from your CV, and your CV tailored to this job. Free, no card.

What they ask for

✓7+ años de experiencia en PM de herramientas para desarrolladores
✓Experiencia comprobada en productos de flujo de trabajo: dev local, migrations, CI/CD, entornos preview
✓Capacidad para definir y defender el problema y el modelo mental del flujo completo
✓Habilidades para tomar decisiones de priorización bajo múltiples restricciones (costo, latencia, capacidad)
✓Capacidad técnica para entender código, CLI, Git y arquitectura de sistemas
✓Experiencia trabajando con ingenieros, diseño y liderazgo en entornos multidisciplinarios

Don't tick every box? That's normal — your free dossier shows your gaps and how to cover them in the interview.

PostgresCLIMigrationsSeed dataConfiguration as codeBranchingGitHub integrationEdge FunctionsRealtimeVector Search

Who should you write to at Supabase?

Your free dossier identifies the people who'd interview you — their background, what they value, and how to reach out so you stand out before applying.

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. Supabase is the open-source Postgres development platform that 10M+ developers and thousands of enterprises depend on every day. We're hiring a Branching PM to own the whole path a change takes from a laptop to production: local development https://supabase.com/docs/guides/local-development with the CLI, migrations and seed data, configuration as code, an isolated branch https://supabase.com/docs/guides/deployment/branching per pull request, the GitHub integration https://supabase.com/docs/guides/deployment/branching/github-integration that tests it, and the promotion to production https://supabase.com/docs/guides/deployment/managing-environments. Agents now drive a growing share of this workflow: they open branches in parallel, run migrations constantly, and need feedback in seconds. The path has to hold for people and agents alike. WHAT YOU'LL BE RESPONSIBLE FOR - Talking to customers across the full spectrum. Indie developers running the CLI for the first time, startups wiring up a branch per pull request, platforms that provision environments on Supabase for millions of their own end users, and enterprise teams who need a documented route from development to staging to production. They ask for features. You find the need behind the ask, and those needs set the roadmap. - Making the pieces feel like one workflow. The CLI, migrations, seeds, configuration, branches, and Git integration have to land on developers as one path. You decide where one tool ends and the next begins, and the mental model is yours to defend. - Owning the outcome of each launch, and defining how it's measured before it ships. The metric, the threshold, and the read afterwards are yours: time to a developer's first migration, branch adoption, the share of teams shipping through a reviewed workflow. Shipping starts the measurement, and the read decides the next call. - Owning the problem statement and the commercial shape behind every bet. You capture the customer evidence, name the constraints (provisioning latency, compute capacity, cost per environment, how much production data an environment can hold), and set each target at how good it needs to be. Every environment costs compute, so you decide what stays free to win a developer and what a company pays for. - Deciding what gets built, what gets deferred, and what gets cut. Every quarter you're choosing between local development ergonomics, partner platforms that run their whole user base on this workflow, enterprise release requirements, and the infrastructure work that all of it runs on. You know the path's SLOs and what spending the error budget costs the roadmap. The priorities are yours to defend, and the written non-scope settles most mid-flight asks. - Keeping engineering, design, and leadership aligned. Your roadmap runs through compute, storage, the CLI, the dashboard, and the GitHub integration. You write it down, surface dependencies before they become blockers, and keep decisions moving. YOU MIGHT BE A GOOD FIT IF YOU - Have 7+ years of product management experience on developer tools, or you're an ex-founder with strong product instincts. Technical here means hands-on: you follow a design discussion, get into the code when the answer lives there, with or without AI assistance, and form your requirements from what the system actually does. - You've shipped developer-workflow products. You've owned at least one of local development tooling, migrations, CI/CD, ephemeral or preview environments, or Git-integrated deploys. You understand the tradeoffs well enough to judge them: what belongs in a CLI vs. a dashboard, schema-only environments vs. environments with data, copy-on-write clones vs

Don't apply unprepared

We research who's interviewing you, tailor your CV and rehearse you live — first one free.