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 Apple Card Fraud Detection

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

Design an ML system for Apple Card authorization fraud detection. The system scores each card-present or card-not-present transaction in real time and decides whether to approve, step up with additional verification, or decline, while minimizing false declines for legitimate customers.

Scale

SignalValue
Apple Card active users35M
Peak authorization QPS120K
Average QPS45K
Transactions per day~3.8B authorization events/month
Merchant population60M+ merchants globally
Device graph size500M+ Apple devices/accounts/cards linked entities
End-to-end decision latency budget200ms p99
Feature freshness target<5s for streaming counters

Task

  1. Clarify the product and risk requirements: what actions the system can take, acceptable fraud loss, and customer experience constraints.
  2. Size the system and propose an end-to-end architecture for training, feature computation, and online serving.
  3. Design a multi-stage decision pipeline (fast rules / candidate risk retrieval / ML ranking / policy layer) and justify model choices per stage.
  4. Define the online vs batch feature strategy, including how you would build an online/offline feature store and avoid training-serving skew.
  5. Propose offline and online evaluation, thresholding, and rollout strategy, including how to handle delayed labels and concept drift.
  6. Identify key failure modes, monitoring, and fallback behavior under partial outages or model degradation.

Constraints

  • The system must return a decision in under 200ms p99, including feature fetches and network overhead.
  • Fraud labels are delayed and partially observed due to chargebacks, disputes, and manual investigations.
  • The system must satisfy financial compliance, auditability, and explainability requirements for adverse actions.
  • Customer friction is expensive: unnecessary declines or step-ups hurt trust and transaction conversion.
  • Some features are only available in batch; others must be computed from streaming events in near real time.
  • The design should support global traffic bursts (e.g., holiday shopping) and regional failover without materially increasing fraud loss.