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 ML-Driven SMS Notification Delivery

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

ShopPulse is a large commerce platform that sends promotional, transactional, and reminder SMS notifications. The business wants an ML-driven system that decides who to message, when within a fixed delivery window, and in what priority order so millions of users can be reached efficiently without hurting user experience or carrier deliverability.

Scale

SignalValue
DAU45M
SMS-eligible users18M
Daily notification campaigns2,500
Peak campaign audience12M users
Peak send rate220K SMS/sec across providers
Historical events/day9B user events
End-to-end decision latency budget150ms per online eligibility request
Delivery window30 minutes to 6 hours

Task

Design an end-to-end ML system for high-volume SMS notifications. Your design should address:

  1. How to frame the problem and define the prediction tasks for candidate selection, ranking, and send-time optimization.
  2. The end-to-end architecture, including offline training, online/batch serving, feature storage, and feedback logging.
  3. A multi-stage decision system (retrieval/eligibility → ranking/prioritization → re-ranking or policy layer) that can handle millions of recipients inside a strict time window.
  4. Model choices for each stage, with tradeoffs around latency, freshness, interpretability, and operational complexity.
  5. Offline and online evaluation, including business metrics, user-experience guardrails, and experimentation strategy.
  6. Failure modes at scale: feature drift, training-serving skew, provider outages, duplicate sends, and miscalibrated models.

Constraints

  • Must respect user consent, quiet hours, country-specific SMS regulations, and per-user frequency caps.
  • Some campaigns are hard-deadline notifications; others are promotional and can be throttled or skipped.
  • Delivery providers have variable throughput, cost, and failure rates by geography.
  • Real-time user activity is available within ~2 minutes; some conversion labels arrive with 24-72 hour delay.
  • The system should minimize unnecessary sends because SMS cost is material and over-messaging increases unsubscribe risk.