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 Instagram Stories Recommender

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

Instagram Stories is a high-frequency surface where users quickly consume ephemeral content from accounts they follow and accounts Instagram may recommend. Design an end-to-end ML system that ranks Stories for each viewer when they open the Stories tray or advance to the next Story.

Scale

SignalValue
DAU600M Instagram users viewing Stories daily
Peak QPS2.0M Story ranking requests/sec globally
Active Story inventory~180M live Stories in a 24-hour window
New Stories/day~1.2B
Candidate set before ranking5K-20K per request
End-to-end p99 latency budget120ms

Task

Design the recommendation system and explain the major tradeoffs. Address the following:

  1. Define the product objective, request types, and key functional/non-functional requirements.
  2. Size the system and propose a multi-stage architecture for retrieval, ranking, and re-ranking.
  3. Choose models and features for each stage, including how you handle follow-graph signals, freshness, and cold start.
  4. Describe the online serving path versus offline training/data pipelines, including Meta-specific infrastructure assumptions where relevant.
  5. Define offline and online evaluation, experiment design, and rollout strategy.
  6. Identify major failure modes such as feature drift, training-serving skew, stale content, and monitoring gaps.

Constraints

  • Stories expire after 24 hours, so freshness matters more than long-tail historical content.
  • The system must respect privacy, user blocks/mutes, integrity filters, and age/region policies before final ranking.
  • Most requests happen in bursts during app opens, so tail latency and cache effectiveness are critical.
  • Cost matters: the heaviest model cannot run over the full live Story inventory on every request.
  • New users and new creators may have little interaction history, but the system must still produce a high-quality tray.