Stripe.
Payments, billing, Connect payouts and financial infrastructure APIs for internet businesses.
its questions lean on
- idempotency
- webhooks
- API design
- ledgers and money correctness
- observability
The rounds, as candidates describe them
- CodingA practical coding round that adds requirements part by part.source ↗
- Bug squashFind and fix a bug in an unfamiliar open-source codebase.source ↗
- IntegrationA multi-part problem built against an API, run end to end.source ↗
- System design and behaviouralA system design round and a behavioural round on past projects.source ↗
Reported by candidates
From public interview write-ups; each links its source.- Design Webhook DeliverySystem designW02 · DAY 04 · Webhook Delivery System →W02 · DAY 02 · Idempotency in Practice →W03 · DAY 04 · Dead Letters and Poison Pills →reported in:LeetCode Discuss · Stripe UAE Backend Engineer (2023) ↗
- Design a Metrics Monitoring and Alerting SystemSystem designIP-15 · Design a Metrics Monitoring and Alerting System →W10 · DAY 02 · Observability →reported in:LeetCode Discuss · Staff Eng offers incl. Stripe, system design screen (2020) ↗
- Design a News FeedSystem designIP-07 · Design a News Feed →SQ-10 · Twitter/X →reported in:Aced (Exponent) · Stripe Software Engineer, "Design Twitter" phone interview (2026) ↗
- Design a Subscription and Usage-Based Billing CalculatorLow-level designW08 · DAY 04 · Late-Arriving Data and Correctness →IP-20 · Design a Payment System →reported in:Aced (Exponent) · Stripe Software Engineer, online assessment (2026) ↗
Likely, from what they build
Our pick, not a report: questions that fit Stripe's products.- Design a Payment SystemSystem designIP-20 · Design a Payment System →SQ-18 · Razorpay Payment Gateway →W05 · DAY 02 · Distributed Transactions — The Saga Pattern →
- Design a Rate LimiterSystem designIP-02 · Design a Rate Limiter →W01 · DAY 03 · Rate Limiting at Scale →W09 · DAY 02 · Noisy Neighbor Prevention →
- How do idempotency keys make payment API retries safe?ConceptW02 · DAY 02 · Idempotency in Practice →W02 · DAY 01 · Timeout Hell →
- Design a Double-Entry LedgerSystem designIP-20 · Design a Payment System →W03 · DAY 05 · Audit Log System →W03 · DAY 02 · Transactional Outbox →
- Design a Card Payment NetworkSystem designSQ-04 · Visa/Mastercard Global Payment Network →IP-20 · Design a Payment System →
- Design a Digital WalletSystem designIP-20 · Design a Payment System →W05 · DAY 01 · Consistency Models →
Study path
Every lesson the questions above point to, once, in order.
- 01W02 · DAY 04Webhook Delivery System
- 02W02 · DAY 02Idempotency in Practice
- 03W03 · DAY 04Dead Letters and Poison Pills
- 04IP-15Design a Metrics Monitoring and Alerting System
- 05W10 · DAY 02Observability
- 06IP-07Design a News Feed
- 07SQ-10Twitter/X
- 08W08 · DAY 04Late-Arriving Data and Correctness
- 09IP-20Design a Payment System
- 10SQ-18Razorpay Payment Gateway
- 11W05 · DAY 02Distributed Transactions — The Saga Pattern
- 12IP-02Design a Rate Limiter
- 13W01 · DAY 03Rate Limiting at Scale
- 14W09 · DAY 02Noisy Neighbor Prevention
- 15W02 · DAY 01Timeout Hell
- 16W03 · DAY 05Audit Log System
- 17W03 · DAY 02Transactional Outbox
- 18SQ-04Visa/Mastercard Global Payment Network
- 19W05 · DAY 01Consistency Models
Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.