Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
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
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess 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
Build my plan

Real-Time Notification System for Millions

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

Your question is Real-Time Notification System for Millions. 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

Design a real-time notification system capable of engaging millions of users without degrading service reliability.

Clarify the product and reliability requirements before proposing an end-to-end ML system. Cover event ingestion, notification candidate generation, ranking and re-ranking, delivery orchestration, and user controls. Explain how you would separate online decisions from batch computation, evaluate engagement without encouraging notification spam, and protect core services during traffic spikes or model failures.

Address scale assumptions, latency and availability targets, data freshness, model training and serving, observability, experimentation, feature drift, training-serving skew, and rollback or fallback behavior.