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

Real-Time Message Delivery Prioritization

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

Scenario

You are designing the ML layer for a real-time chat application with one-to-one and group messaging. The core transport system already handles basic send, ack, and retry semantics, but delivery quality varies across device state, network conditions, and recipient availability. Your team wants an ML system that predicts delivery risk in real time so the app can choose retry strategy, push escalation, and queue prioritization to improve delivered-within-seconds rate without breaking message ordering. This directly impacts user trust and engagement on the messaging surface.

Scale

SignalValue
DAU900M
Peak message send QPS3.5M
Peak delivery-attempt QPS12M
Group chats share of messages18%
Max common group size512 members
p99 decision latency budget25ms
Feature freshness target< 60s

Question

How would you design this end-to-end ML system so it can score delivery risk and choose delivery actions in real time at scale, while preserving message ordering guarantees and handling delayed labels, feature drift, training-serving skew, and online failures?