Design a Grocery Checkout System
A grocery checkout is the software behind the till. It looks up what was scanned, works out the price after every deal and coupon, takes the money and prints the receipt. At Susquehanna it's one of the most commonly reported design prompts for software engineers. It shows up in the final-stage object-oriented round, which runs 45 to 60 minutes, and candidates from intern to senior describe getting some version of it.
This is a low-level design round, so there are no load balancers to draw. The interviewer starts from the overall shape and then pushes down into class structure and real code in a shared editor, usually C++ or Python. The coding section has the phone-screen version, a Premium question that prints a receipt, which fits in about 30 minutes. Here we build the onsite scope on top of it, adding weighed goods, a promotion engine, payments that can fail, lanes that share stock, and the inventory and profit extension.
SusquehannaPremium lesson · System design round
The Susquehanna design, worked end to end.
- The API and data modelSystem design
- The design, drawn out3 diagrams
- 4 deep divesWith the tradeoffs
$49 a year · all 100 companies · cancel anytime
From 20,000+ candidate reports, forum threads behind logins and write-ups in Chinese.
Susquehanna interview guideKnow what Susquehanna asks before you walk in.
13 coding · 2 system design · 26 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.