185. Design Restaurant Ranking for Food Delivery

The brief

Design Restaurant Ranking for Food Delivery. Rank the stores that can deliver now by the chance of an order: session labels, live ETA and supply features, a multi-task ranker, new-merchant exploration, switchbacks: one-hour boards for junior, senior and staff, with theory. Work from the scoping questions below. State assumptions for any unspecified load, guarantee or target, then trace your design end to end. Explain one difficult case and a credible alternative; the worked example is a reference, not a required implementation.

• Set the scope: Where do we rank restaurants? What makes a ranking good for diners, stores and couriers?
• Define the contract: How many diners, stores and dinner-peak requests? How fast must the ranked feed return?
• Test the boundaries: How quickly must store closures and kitchen backlog show up? Which order signals can we learn from? How do we rank new diners and new restaurants? Which marketplace rules override the model?

Constraints

Explicit scope and guarantees

Resolve the scoping questions for Restaurant Ranking for Food Delivery. Separate stated behavior from assumptions, and identify what is outside your design.

Supported operating targets

Declare relevant volume, latency, freshness, quality or cost targets with units. Show calculations or an evaluation plan that can test them; unspecified targets are your assumptions, not hidden pass criteria.

Failure and boundary behavior

Explain how your guarantees hold in a difficult case relevant to this subject. Address: How do we rank new diners and new restaurants? Which marketplace rules override the model?

What to cover

1. 01

   Scope and behavior contract

   Identify users, required behavior and exclusions. Answer: Where do we rank restaurants? What makes a ranking good for diners, stores and couriers?

2. 02

   State and interfaces

   Define the information owned by the system and the inputs, outputs and errors at its boundaries. Resolve: How many diners, stores and dinner-peak requests? How fast must the ranked feed return?

3. 03

   Capacity and operating targets

   Estimate the dominant workload and resource demand with units and explicit assumptions. For a learned system, also state how quality is measured and what data is available.

4. 04

   Architecture and central flow

   Draw or describe the responsibilities needed for Restaurant Ranking for Food Delivery. Trace a representative request, event or job from its input to a visible result; identify durable state owners.

5. 05

   Failure and boundary walkthrough

   Walk through a difficult case step by step, including detection and recovery. Consider: How quickly must store closures and kitchen backlog show up? Which order signals can we learn from? How do we rank new diners and new restaurants? Which marketplace rules override the model?

6. 06

   Tradeoffs and operations

   Compare a credible alternative using your chosen workload and guarantees. Explain a remaining risk, a signal to watch and when you would change the design.

Worked designs

Explore the architecture and decisions, then build on an example with Coach.

Official design

Design Restaurant Ranking for Food Delivery

Rank the stores that can deliver now by the chance of an order: session labels, live ETA and supply features, a multi-task ranker, new-merchant exploration, switchbacks: one-hour boards for junior, senior and staff, with theory.

Explore the design

Review rubric

AI feedback uses these criteria. Scores are practice feedback.