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 Flash Sale Notification Ranker

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

ShopNow is a large e-commerce marketplace that runs short flash sales across electronics, fashion, and home goods. The notifications team wants an ML-driven system that decides who to alert, when, and through which channel so a flash sale reaches millions of users without overloading downstream systems or spamming low-intent users.

Scale

SignalValue
DAU45M
Monthly active users opted into notifications120M
Peak flash-sale campaigns/day300
Largest campaign audience18M eligible users
Peak send rate target1.2M notifications/min
Candidate users per campaign5M-18M
Per-user decision latency (online path)p99 < 120ms
User/item feature freshness< 5 min for user activity, < 15 min for inventory/pricing

Task

Design an end-to-end ML system for flash-sale notifications. Address the following:

  1. Clarify the product goal, success metrics, and key constraints, including user fatigue and backend protection.
  2. Propose a multi-stage architecture for audience selection, ranking, and send-time/channel decisions.
  3. Define the offline and online data pipelines, labels, and feature store strategy.
  4. Choose models for each stage and explain the tradeoffs versus simpler heuristics.
  5. Describe the serving architecture, including rate limiting, batching, fallbacks, and capacity planning.
  6. Explain how you would evaluate the system offline and online, and how you would detect drift, training-serving skew, and operational failures.

Constraints

  • Inventory is limited and can sell out within minutes; stale recommendations are costly.
  • Notification providers enforce per-minute throughput caps and occasional regional throttling.
  • The system must respect user opt-in status, quiet hours, and compliance rules by country.
  • Cost matters: most campaigns should run on CPU-heavy infrastructure, not always-on GPU serving.
  • The business wants incremental revenue lift, but guardrails must limit unsubscribe rate, complaint rate, and backend traffic spikes.