Product Manager interview
at Stripe.

Tell-me-about-a-time stories on ownership, conflict, and impact — scored against this company's real values.

1. 01 Tell me about a time you put a specific user's problem ahead of an internally convenient roadmap, and what it cost you.
2. 02 Describe a product decision where you reasoned from first principles instead of copying what competitors or the industry did.
3. 03 Walk me through a time you owned a launch that went wrong and how you handled the fallout with users and stakeholders.
4. 04 Tell me about a time you had to align engineering, risk, and finance partners who fundamentally disagreed about a payments product tradeoff.

The hard screen for the craft itself — talked through out loud, not whiteboarded in your head.

1. 01 Walk me through what happens end-to-end when a customer's card is charged, naming the roles of the acquirer, card network, and issuing bank.
2. 02 How would you design the API and developer experience for a new subscription-billing feature so that integration feels effortless for developers?
3. 03 A merchant complains their authorization rate is lower than a competitor's; how would you diagnose whether it's a product, network, or fraud issue?
4. 04 How would you decide which webhook events to expose for a new product, and how would you handle idempotency and retries from the developer's perspective?

Open-ended design of the systems this company actually runs, with the interviewer probing your tradeoffs.

1. 01 Design a product that helps platforms onboard and pay out to thousands of sub-merchants, including KYC and money movement.
2. 02 Design a billing and invoicing product that correctly handles proration, failed payments, and dunning retries.
3. 03 Design the merchant-facing dashboard and metrics for a fraud product like Radar, balancing fraud caught against legitimate sales blocked.
4. 04 Design a webhook delivery product that merchants can trust for at-least-once, ordered, and verifiable event notifications.