Product Manager, Sail Core

Sobre el puesto

<h2>Who we are</h2> <h3>About Stripe</h3> <p>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.</p> <h3>About the team</h3> <p>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.</p> <h2>What you'll do</h2> <p>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?</p> <h3>Responsibilities</h3> <ul> <li>Own the product strategy and roadmap for Stripe's frontend platform</li> <li>Drive the largest frontend modernization initiative at Stripe while holding the line on architectural quality</li> <li>Redefine frontend development with agentic tooling</li> <li>Define and track key metrics such as latency, build times, and reliability SLOs to make difficult trade-off decisions</li> <li>Be the product voice in deeply technical decisions such as API surface design, framework deprecation sequencing, extraction boundaries, and migration tooling</li> </ul> <h2>Who you are</h2> <p>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.</p> <p>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.</p> <h3>Minimum requirements</h3> <ul> <li>5+ years of product management experience, with at least 2 years on platform, infrastructure, or developer tools teams</li> <li>Strong technical fluency in frontend web development—you discuss JavaScript and TypeScript, React component models, build systems, and performance optimization with depth</li> <li>Experience driving large-scale migrations or platform transitions across multiple teams, including the sequencing, dependency management, and stakeholder alignment that make them succeed</li> <li>Demonstrated use of quantitative metrics to drive platform investment decisions—you've defined the metrics, not just tracked them</li> <li>Track record of partnering with engineering to make architectural trade-offs grounded in user impact</li> </ul> <h3>Preferred qualifications</h3> <ul> <li>Engineering background—you've written frontend code professionally and it still shapes how you think about product decisions</li> <li>Led or significantly contributed to a legacy extraction or monolith decomposition effort and understand viscerally why they're hard and where they get stuck</li> <li>Believe that fast software is the best software</li> <li>Naturally default to the platform solution over the one-off fix, but know when speed demands the opposite</li> <li>Explain what a cascading re-render is, why it matters, and what to do about it—to an engineer, a designer, and a VP, in three different ways</li> </ul>