Design Swiggy

Design an object-oriented food delivery platform (like Swiggy) with customer/restaurant/delivery partner registration, restaurant menu management with food type (Veg/Non-Veg/Vegan) and availability toggle, restaurant search by keyword/cuisine/distance, a cart enforcing a single-restaurant policy, order placement with full pricing breakdown (item total + distance-based delivery fee + ₹2 platform fee + 5% GST − coupon discount + tip), delivery partner assignment using the Strategy pattern (Nearest Partner / Highest-Rated Partner), and a 7-step order lifecycle.

The cart ensures all items come from a single restaurant. Orders compute delivery fee based on Haversine distance (₹15 for ≤2 km up to ₹60 for >10 km). Cancellation is allowed only before the delivery partner picks up the food. Delivery partners cycle through OFFLINE → AVAILABLE → ASSIGNED → PICKING_UP → EN_ROUTE → AVAILABLE. A coupon system supports flat and percentage discounts with min-order, max-cap, and usage-limit validation.

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Follow-up Questions(Questions an interviewer might ask)

Design Swiggy

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Follow-up Questions(Questions an interviewer might ask)

Design Swiggy

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Gather Requirements~3 min

Identify Classes & Entities~4 min

Define Relationships~3 min

Apply Design Patterns~4 min

Apply SOLID Principles~3 min

Code Organization~2 min

Follow-up Questions(Questions an interviewer might ask)

1How would you handle concurrent order assignment to prevent double-assigning a delivery partner?

2How would you implement dynamic delivery fees / surge pricing during peak hours?

3How would you support multi-restaurant orders (order from 2+ restaurants in one checkout)?

4How would you add real-time order tracking with live delivery partner location?

5How would you implement a recommendation engine for restaurants and dishes?

Key Topics

Asked At

Design Swiggy

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Gather Requirements~3 min

Identify Classes & Entities~4 min

Define Relationships~3 min

Apply Design Patterns~4 min

Apply SOLID Principles~3 min

Code Organization~2 min

Follow-up Questions(Questions an interviewer might ask)

1How would you handle concurrent order assignment to prevent double-assigning a delivery partner?

2How would you implement dynamic delivery fees / surge pricing during peak hours?

3How would you support multi-restaurant orders (order from 2+ restaurants in one checkout)?

4How would you add real-time order tracking with live delivery partner location?

5How would you implement a recommendation engine for restaurants and dishes?

Key Topics

Asked At