Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Design Cold-Start Product Recommendations

MediumSystem Design00:00
Practice interviewer
In session
5 left
00:00

Your question is Design Cold-Start Product Recommendations. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Product Context

ShopNow is a large e-commerce marketplace. Design the recommendation system for the home feed and product-detail-page modules, with a specific focus on handling cold start for both new users and newly listed items.

Scale

SignalValue
DAU35M
Peak recommendation QPS180K
Active catalog120M products
New items/day2.5M
Users with <5 historical events28% of DAU
End-to-end p99 latency budget150ms

Task

  1. Clarify the product goal and define success metrics for recommendations under cold-start conditions.
  2. Propose an end-to-end architecture covering retrieval, ranking, and re-ranking for both warm and cold users/items.
  3. Design the data and feature pipeline, including what can be computed batch vs near-real-time.
  4. Choose models for each stage and explain how they address new-user and new-item cold start.
  5. Define offline and online evaluation, including segment-level analysis for cold-start cohorts.
  6. Identify major failure modes such as feature drift, training-serving skew, popularity collapse, and stale item metadata.

Constraints

  • New products must become eligible for recommendation within 10 minutes of listing.
  • Logged-in users may have rich history, but guest users often have only session context, geo, device, and referrer.
  • Serving cost must stay below $0.001 per recommendation request.
  • Some item attributes from sellers are noisy or missing at listing time.
  • The system must support policy filters: out-of-stock items, blocked sellers, and regional compliance restrictions.

Your design should explicitly discuss how to avoid over-relying on popularity for cold start, how to balance exploration vs exploitation, and how to keep training and serving features consistent.