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

Real-Time Fraudulent Click Filtering

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

Your question is Real-Time Fraudulent Click Filtering. 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

AdStream is a large ad network serving sponsored search and display ads across publisher apps and websites. You need to design an ML system that detects and filters fraudulent ad clicks in real time before they are billed to advertisers or used for downstream optimization.

Scale

SignalValue
DAU120M users
Peak ad impression QPS900K
Peak click-event QPS85K
Advertisers1.8M active
Publishers220K active
Devices / browsers seen per day300M+
End-to-end decision latency budget50ms p99
Historical labeled events~30B clicks over 180 days

Task

  1. Clarify the product goal and define what counts as fraudulent vs suspicious vs unknown traffic.
  2. Design the end-to-end architecture for real-time scoring, filtering, and post-hoc investigation.
  3. Propose a multi-stage decision system (fast rules / retrieval / ranking / re-review) and justify model choices at each stage.
  4. Explain the data pipeline, labels, feature store design, and how you avoid training-serving skew.
  5. Define offline and online evaluation, including delayed labels, false-positive cost, and advertiser trust guardrails.
  6. Identify major failure modes, monitoring, and rollback strategies.

Constraints

  • Fraud labels are delayed and noisy: chargebacks, manual reviews, and advertiser complaints may arrive days later.
  • False positives are expensive because blocking legitimate clicks hurts publisher revenue and advertiser delivery.
  • Some features must be computed in streaming fashion (IP velocity, device fingerprint frequency, publisher-level anomaly rates).
  • The system must support regional compliance requirements; raw IPs and user identifiers may have retention limits.
  • Cost matters: the highest-volume path should run primarily on CPU, with minimal per-event state lookups.
  • The platform must continue serving ads even if the ML scorer is degraded; define safe fallbacks.