Engineering 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 had to move an excellent engineer off a project they loved for the good of the team or users.
2. 02 Describe how you resolved a serious conflict between two engineers on your team while keeping delivery on track.
3. 03 Walk me through a time you led your team through significant ambiguity and how you balanced macro optimism with micro pessimism.
4. 04 Tell me about a time you raised the rigor or quality bar on your team and how you handled the resistance.

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

1. 01 Walk me through how you'd guide a team designing an idempotent money-movement service, and where you'd push hardest on correctness.
2. 02 How do you ensure financial correctness and reliability standards are upheld in code your team ships without becoming a bottleneck?
3. 03 A live scenario: an engineer wants to skip the idempotency design to hit a deadline; how do you respond in the moment?
4. 04 How would you set up on-call, incident review, and reliability practices for a team owning a payments-critical service?

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

1. 01 Design a double-entry ledger service and explain how you'd staff, sequence, and de-risk its delivery as a manager.
2. 02 Design a webhook delivery platform and walk through the architectural tradeoffs you'd want your team to debate.
3. 03 Design an analytics pipeline for payment metrics and explain how you'd ensure it stays auditable and reconcilable.
4. 04 Design a fraud-detection system at a high level and describe how you'd balance ML, infra, and risk ownership across the team.