远程工作雷达

产品经理 - 分支

Product Manager - Branching

职能支持全球可投
公司Supabase
薪资未公开
工作地点Remote, Global
地域资格全球可投
时区要求无特别要求
用工类型FullTime
发布时间26 天前
数据来源Ashby
前往企业招聘页投递 →
全球可投:该职位未限制候选人所在地区。仍需注意薪资可能按地区折算,以及实际签约方式(正式雇佣 / 独立合同)。

关于 Supabase

Supabase 是基于 Postgres 的开发平台,由开发者为开发者打造。我们提供完整的后端解决方案,包括数据库、认证、存储、边缘函数、实时功能和向量搜索。所有服务深度集成,专为增长而设计。

Supabase 是一个开源的 Postgres 开发平台,每天有 1000 多万开发者和数千家企业的依赖。我们正在招聘一名分支产品经理,负责从笔记本电脑到生产环境的完整流程:本地开发 https://supabase.com/docs/guides/local-development 使用 CLI,迁移和种子数据,配置即代码,每个 pull request 的隔离分支 https://supabase.com/docs/guides/deployment/branching,GitHub 集成 https://supabase.com/docs/guides/deployment/branching/github-integration 来测试它,并推广到生产环境 https://supabase.com/docs/guides/deployment/managing-environments。现在,代理程序越来越多地驱动这一工作流:它们并行打开分支,持续运行迁移,并需要秒级反馈。这条路径必须同时适用于人和代理。

你将负责以下事项

- 与全范围的客户沟通。独立开发者第一次使用 CLI,初创公司为每个 pull request 设置分支,为数百万最终用户提供环境的平台,以及需要从开发到预发布再到生产的明确路线的企业团队。他们提出功能需求。你需要找到需求背后的真实问题,这些需求决定了产品路线图。

- 让各个部分感觉像一个统一的工作流。CLI、迁移、种子数据、配置、分支和 Git 集成必须对开发者来说是一个路径。你决定一个工具何时结束,下一个工具何时开始,而这个思维模型由你来维护。

- 对每次发布的成果负责,并在发布前定义衡量标准。指标、阈值和后续分析都由你来确定:开发者首次迁移的时间、分支采用率、通过审核工作流发布的团队占比。发布启动了度量,而后续分析决定了下一步决策。

- 负责每个决策背后的问题陈述和商业形态。你收集客户证据,明确约束条件(供应延迟、计算容量、每个环境的成本、环境可以容纳多少生产数据),并设定每个目标需要达到的水平。每个环境都需要计算资源,因此你需要做出决策。

查看英文原文

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. dump-and-restore, why branching is cheap and merging stateful systems isn't, and how much of a workflow can live in a config file before developers stop reading it. Familiarity with the Postgres ecosystem (migrations, extensions, tooling) is a bonus.

- You're biased toward action. You break big bets into pieces that ship early, treat each release as a test of your assumptions, and deliver carefully enough that this quarter's launch doesn't become next quarter's support burden. You measure speed by how fast the outcome arrives.

- You build with what you own. You run the workflow yourself: a project running locally, migrations and seeds under version control, a branch opened off a pull request, and a promotion to production you'd trust on a Friday.

- You use AI to move faster. You reach for AI tools to cut the slow parts and spend the time you save on judgment calls.

- You work async by default. You make decisions in writing and move threads 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.

本页面信息整理自 Ashby,版权归原发布方所有。职位可能随时关闭,投递请以原始页面为准。 本站只做信息聚合展示,不参与招聘流程,也不向求职者收取任何费用。

该公司其他在招职位

← 返回全部职位