Lead Product Manager, Consumer Platform

Mindbody

1d•$170,000 - $210,000

About The Position

Every consumer experience Mindbody ships is built on top of our consumer platform. The platform is the shared foundation that lets our front-end squads deliver reliable, consistent wellness experiences without rebuilding the plumbing every time. This role exists to answer a deceptively simple question: what does the consumer platform need to become so that front-end squads can move fast on solid ground — and how do we get there from a legacy monolith without breaking the surfaces that depend on it today? This is a senior individual-contributor role for a product leader who is equally comfortable in two rooms: designing API contracts and service boundaries with a senior backend engineering team, and making the cross-surface platform calls that keep multiple consumer squads pulling in the same direction. You'll own the consumer platform roadmap, partner closely with engineering and your downstream partner squads, and be measured on how much faster and more reliably the rest of consumer can build because of the foundation you've shaped.

Requirements

A track record shipping platform, API, or infrastructure products — ideally ones other product teams build on top of. You understand what makes a platform a multiplier rather than a bottleneck.
Genuine technical fluency. You hold your own with senior backend engineers on API design, service boundaries, and architecture tradeoffs; you can read and reason about system design and earn engineering trust on the merits.
Cross-surface product judgment. You've owned decisions spanning multiple teams or product surfaces and you're comfortable being the connective tissue — making the call that serves the whole even when it isn't the easy local answer.
Experience modernizing legacy systems. You've decomposed a monolith or migrated a platform evolutionarily, and you know how to manage deprecation and dependencies without breaking the teams that rely on you.
Strong influence without authority. You make platform decisions that affect peer squads while keeping those relationships strong — lowering the temperature in contentious tradeoffs rather than raising it.
Metric-anchored decision-making. You define clear success metrics, including for inherently internal platform work, and you connect platform outcomes to commercial impact.
The seniority to operate independently alongside a senior engineering team. 6+ years of product management experience, with meaningful time on platform, API, or infrastructure products. Consumer product experience is a strong plus.

Nice To Haves

Consumer product experience is a strong plus.

Responsibilities

Own the consumer platform strategy and roadmap. Define the capabilities the platform must provide so consumer surfaces can build reliable, consistent consumer experiences faster — and sequence the highest-ROI investments for a cross-functional engineering team.
Drive the evolution of the consumer API. Consolidate and redesign API contracts to reduce surface area and developer cognitive load; decompose the legacy Consumer API monolith into domain-driven services; deprecate legacy endpoints — evolving the architecture rather than rebuilding it from scratch.
Influence cross-surface platform and architecture decisions. Collaborate with Engineering counterpart on shared-infrastructure questions that span the consumer squads, partnering with surface PMs on their product roadmaps while holding the line on a coherent platform.
Partner deeply with a senior backend engineering team. Earn trust at the architecture level — engage credibly in contract design, service boundaries, and technical tradeoffs — and turn that partnership into shipped, stable platform capabilities.
Sequence migration without breaking the surfaces. Manage the path from monolith to modern services so front-end squads are continuously unblocked, never disrupted; treat deprecation as a product to be managed, not a cleanup task.
Treat the squads as your customers. Spend regular time with the other consumer PMs and engineers who build on the platform — the way a customer-facing PM spends time with customers — to ground roadmap decisions in real developer needs.
Define and move the metrics that matter. Own platform adoption (% of consumer requests flowing through the platform) and connect platform health to the downstream outcomes it unblocks: surface velocity, reliability, and conversion.