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

Design Checkout Availability Risk Scorer

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

Your question is Design Checkout Availability Risk Scorer. 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

Product Context

ShopSphere is a large e-commerce marketplace. During peak events like Black Friday, the checkout flow is business-critical, and the company wants an ML-driven service that predicts checkout risk in real time so the platform can route users to safer payment, fraud, and fulfillment paths without hurting conversion.

Scale

SignalValue
DAU45M shoppers
Peak checkout starts180K/min
Peak QPS to risk service35K QPS
Payment methods120 globally
Merchants / sellers3.5M
Active SKUs220M
End-to-end checkout latency budget800ms p99
ML service latency budget60ms p99

Task

Design an end-to-end ML system that keeps checkout highly available during peak events while minimizing false declines and customer friction.

  1. Clarify the prediction target, decision points, and what actions the service can trigger during checkout.
  2. Propose the online and offline architecture, including feature computation, model training, serving, and fallback behavior under dependency failures.
  3. Design a multi-stage decision system if appropriate (for example: fast retrieval/rules triage → risk ranking → policy re-ranking / action selection).
  4. Define how you would evaluate the system offline and online, including business metrics and guardrails during Black Friday traffic spikes.
  5. Identify major failure modes such as feature drift, training-serving skew, hot keys, stale features, and cascading failures from downstream services.
  6. Explain capacity planning, regional failover, and how the system degrades gracefully when models or features are unavailable.

Constraints

  • The service sits on the critical path of checkout and must not become a single point of failure.
  • Labels are delayed and partially observed: chargebacks may arrive weeks later, while payment authorization failures arrive immediately.
  • Some features contain sensitive payment and user data; design for PCI/PII minimization and regional data residency.
  • Peak-event traffic can be 8-10x normal baseline within minutes.
  • A simpler fallback path must preserve checkout availability even if ML quality drops.