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

Scale Facebook Feed Recommendations

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

Design the recommendation infrastructure for Facebook Feed, where users open the app and expect a personalized, low-latency ranked feed of posts, reels, photos, links, and suggested content from friends, Groups, Pages, and recommended creators. The system must support global traffic across regions while keeping recommendations fresh and relevant.

Scale

SignalValue
DAU1.2B
Peak feed request QPS2.5M
Active content catalog3B eligible posts/reels over recent windows
New content/day250M
Candidate pool before ranking50K-200K per request
End-to-end latency budget (p99)150ms
RegionsNorth America, Europe, APAC, LATAM

Task

Design an end-to-end ML system that can serve Facebook Feed recommendations globally at low latency.

  1. Define the functional and non-functional requirements, including freshness, availability, and personalization goals.
  2. Propose a multi-stage recommendation architecture from candidate generation to ranking and re-ranking, and explain how it scales across regions.
  3. Choose models and features for each stage, including how you would handle cold start, sparse feedback, and rapidly trending content.
  4. Design the training and serving stack, including batch vs streaming pipelines, feature storage, model deployment, and fallback behavior.
  5. Define how you would evaluate the system offline and online, and how you would monitor drift, training-serving skew, and production failures.

Constraints

  • Fresh content should become eligible within 2-5 minutes of creation.
  • User interaction features should be updated near real time.
  • The system must tolerate regional outages and degrade gracefully.
  • Serving cost matters: the most expensive models cannot run on every candidate.
  • Must support policy filtering before final response (integrity, privacy, blocked entities, age/language constraints).