ScaleCrafts

Design an online auction

Let sellers list items and buyers place bids until the auction closes, with live price updates, like eBay.

Functional requirements

  • List an item with a starting price and end time
  • Place bids; the highest valid bid wins
  • Watchers see the current price live

Non-functional requirements

  • Bids are never lost or applied out of order
  • Price updates reach watchers in about a second
  • Auctions close exactly on time

Scale

  • 10M active auctions
  • 1K bids per second normally, 50K at closing peaks
  • Most bids arrive in the last minute

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 online auction”, that starts with: List an item with a starting price and end time; Place bids; the highest valid bid wins; Watchers see the current price live. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (10M active auctions; 1K bids per second normally, 50K at closing peaks; Most bids arrive in the last minute) 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: Bids are never lost or applied out of order; Price updates reach watchers in about a second; Auctions close exactly on time. 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 real-time, consistency and bidding 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.

Related problems

Loading your workspace…