Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Design Personalized Home Feed Ranking

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

Your question is Design Personalized Home Feed Ranking. 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

ShopLoop, a mobile commerce app, wants to launch a new personalized Home Feed that recommends products, collections, and promotions to returning and new users. The feed is the first screen after app open and is expected to drive product discovery, CTR, and downstream purchases.

Scale

SignalValue
DAU35M
Peak feed request QPS180K
Active product catalog120M items
New/updated items per day4M
Avg session length9 minutes
Feed requests per session6
End-to-end p99 latency budget250ms

Task

Design an end-to-end ML system for this new Home Feed feature. Your design should address:

  1. Requirements and success criteria: define the core user and business goals, plus functional and non-functional requirements.
  2. System sizing: estimate serving throughput, candidate set sizes, feature-store load, and training data volume.
  3. Architecture: propose a multi-stage system for candidate generation, ranking, and re-ranking, including what runs online vs batch.
  4. Modeling choices: select models for each stage and explain why they fit the latency, scale, and freshness constraints.
  5. Evaluation and launch: define offline metrics, online experiments, guardrails, and rollout strategy.
  6. Reliability and failure modes: discuss cold start, feature drift, training-serving skew, stale inventory, and monitoring.

Constraints

  • Inventory and price change frequently; recommendations must avoid out-of-stock or stale-price items.
  • 25% of daily users are low-history or anonymous users.
  • The team has a moderate serving budget: heavy GPU inference is allowed only for a small re-ranking stage, not full-catalog scoring.
  • User-level data must comply with privacy requirements; some features may only be retained for 30 days.
  • The product team wants fresh trends and promotions reflected within 15 minutes, not just daily retrains.