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 Facebook Ads CTR Predictor

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 machine learning system that predicts whether a Facebook user will click on an ad shown in Feed, Stories, or Reels. The prediction is used inside Meta’s ads delivery stack to help rank eligible ads for each impression while balancing relevance, advertiser value, and strict latency constraints.

Scale

SignalValue
DAU2.2B Facebook/Instagram users exposed to ads
Peak ad impression opportunities12M requests/sec globally
Eligible ads per auction before pruning50K-200K
Ads active in last 30 days150M creatives/campaigns
New/updated ads per day8M
End-to-end p99 latency budget120ms
Training events/day60B impressions, 900M clicks

Task

Design an end-to-end ML system for click-through-rate prediction in Meta ads ranking. Address the following:

  1. Clarify the prediction target, product goals, and how CTR fits into the overall ads auction and ranking objective.
  2. Propose a multi-stage architecture from candidate retrieval/pruning to ranking and optional re-ranking, including what runs online vs batch.
  3. Define the data pipeline: labels, delayed feedback handling, feature engineering, training cadence, and how you avoid training-serving skew.
  4. Choose models for each stage and justify tradeoffs across quality, latency, interpretability, and serving cost.
  5. Explain offline evaluation, online experimentation, calibration, and business guardrails.
  6. Identify major failure modes at Meta scale, including feature drift, stale features, cold start, and infrastructure degradation.

Constraints

  • The system must support ads from new advertisers and new creatives with little or no click history.
  • User features should be fresh within minutes; campaign budget and pacing signals may update sub-minute.
  • Raw creative understanding models can run offline, but not synchronously in the serving path for every request.
  • The system must be highly available and degrade gracefully to simpler models if feature services or deep rankers are slow.
  • Predictions must be calibrated because downstream auction logic consumes probabilities, not just relative scores.