Design an e-commerce checkout
Let shoppers add items to a cart, check out and pay, while keeping stock counts right during big sales, like Amazon.
Functional requirements
- Add and remove items in a cart
- Check out with an address and payment method
- Order confirmation and status tracking
Non-functional requirements
- Never sell more than is in stock
- Checkout survives payment provider hiccups
- Carts never disappear
Scale
- 50M daily shoppers
- Black Friday peaks of 20K orders per second
- Carts are written far more often than orders
How you’ll be scored
11 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design an e-commerce checkout”, that starts with: Add and remove items in a cart; Check out with an address and payment method; Order confirmation and status tracking. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (50M daily shoppers; Black Friday peaks of 20K orders per second; Carts are written far more often than orders) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Never sell more than is in stock; Checkout survives payment provider hiccups; Carts never disappear. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe inventory, payments and consistency here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.