Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Get started

Design Ecommerce Recommendation Stack

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

Whenever you're ready, walk me through how you'd approach this.

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

Problem

Product Context

ShopSphere is a large ecommerce marketplace with personalized recommendation surfaces on the home page, product detail page, cart page, and post-purchase page. Users expect relevant products across a catalog with fast-changing inventory, promotions, and seasonal demand.

Scale

SignalValue
DAU35M
Peak recommendation QPS180K
Total catalog120M SKUs
In-stock active catalog18M SKUs
New or updated items/day4M
End-to-end p99 latency budget150ms
Recommendation slots/request20-50 items

Task

Design an end-to-end recommendation system from retrieval through ranking and serving. Address the following:

  1. Clarify the product goals, request types, and success metrics across recommendation surfaces.
  2. Propose a multi-stage architecture for candidate generation, ranking, and re-ranking, including how to handle cold start, inventory changes, and business rules.
  3. Design the offline and online data/feature pipelines, including training cadence, feature freshness, and how you avoid training-serving skew.
  4. Choose models for each stage and justify them against latency, scale, and maintainability constraints.
  5. Define how the system is served in production, including caching, fallback behavior, capacity planning, and latency allocation.
  6. Explain offline evaluation, online experimentation, monitoring, and the top failure modes you would expect at this scale.

Constraints

  • Out-of-stock items must never be shown.
  • Promotions and price changes should be reflected within 10 minutes.
  • 25% of daily traffic comes from logged-out or low-history users.
  • Cost matters: GPU use is allowed only for the heaviest stage if clearly justified.
  • The system must support regional compliance requirements, including filtering restricted items by market.
  • Merchandising teams need limited rule-based overrides for campaigns without fully bypassing relevance.