Get AI match insights
See your fit score & personalized tips.
Own the product strategy and roadmap for Stripe's frontend platform, driving the largest modernization effort while defining and tracking latency, build‑time and reliability metrics, and serving as the product voice in deep technical decisions.
8+ years of product management experience (including at least 2 years on platform, infrastructure or developer‑tools teams), strong fluency in frontend web tech (JS/TS, React, build systems), and a proven record of leading large‑scale migrations using quantitative metrics.
The role shapes the core developer experience for 50+ product teams, ensuring fast, reliable frontend infrastructure that underpins Stripe’s Dashboard and the broader ecosystem, directly impacting millions of merchants.
A systems‑thinking product leader who dives into architecture, partners closely with engineers on trade‑offs, and thrives on building platform solutions that improve developer productivity and performance.
Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone's reach while doing the most important work of your career.
Sail Core builds Stripe's frontend platform—the data layer, navigation, observability, and developer tooling that 50+ product teams use to ship web applications, with the Dashboard being the largest. We are responsible for enabling a stellar developer experience for frontend engineers at Stripe. We're hiring a deeply technical product manager to own the platform strategy, drive cross-company modernization initiatives, and set the standard for frontend excellence at Stripe.
How should a platform team decide what to build when 50 teams depend on you and each one thinks their request is the most urgent? When do you invest in long-term architectural health versus shipping the migration that unblocks next quarter's goal? How do you make 9,000 files at initialization become a fast, traceable, joyful developer experience—without breaking production for millions of merchants along the way?
You think in systems, not features. You go deep on architecture, you don't delegate to engineering. You're the person who reads the RFC before the meeting, asks why the error response looks like that, and frames migrations in terms of user outcomes, not just engineering milestones. You treat developer experience as part of the product, not a byproduct.
We're looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement.
