InterviewLegend

Design a Book Price Aggregator

Signature problem
Alex Chen50 min readAdded 106 real interview reports

A book price aggregator is a middleman. It holds no books of its own. It asks bookstores and distributors what they'd charge and picks the best answer. When the price is right, it buys the book for the customer. Think of a price comparison site that also places the order. The customer identifies the book by its ISBN, the 13-digit number that names one edition of one book.

Databricks isn't a bookstore, but this is one of the distributed prompts that comes up most often in its loops. It shows up in the technical phone screen and in the onsite design round. Sometimes it's framed as a bookstore pricing API with batch lookups, or as a book buying and selling service. The product is tiny. The hard parts all run through systems you don't control: hundreds of store APIs that answer slowly or not at all, and a payment provider that can fail between two calls.

The Databricks angle
The onsite version of this prompt can open with two premises: the bookstores are asynchronous, and the number of external calls is large. Both rule out one blocking call per store and invite cache questions. Rounds run about an hour, often in a shared Google Doc, so leave time for the order and payment step.

DatabricksPremium lesson · System design round

The Databricks design, worked end to end.

  1. The API and data modelSystem design · Signature problem
  2. The design, drawn out2 diagrams
  3. 5 deep divesWith the tradeoffs
Get the Databricks questions

$49 a year · all 107 companies · instant access

106 Databricks interview reports · guide updated

Databricks interview guide

Know what Databricks asks before you walk in.

22 coding · 5 system design · 28 behavioral questions

Get Premium$49 a year · Instant access
Or start freeNo card.

Get their questions first.

Had your Databricks interview?How we research

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.