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 a Clickstream Processing System

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

Design a clickstream data processing system to handle log data.

Asked in the System Design stage. Treat this as a practical design exercise: clarify requirements, estimate scale, and explain how the system processes events reliably from ingestion through downstream analytics and ML features.

Address the following:

  1. Define the event schema, ingestion interfaces, partitioning strategy, and delivery guarantees.
  2. Design real-time and batch processing paths, including deduplication, ordering, late events, replay, and schema evolution.
  3. Explain storage choices for raw, cleaned, aggregated, and query-optimized data.
  4. Describe how processed clickstream data supports anomaly detection or other ML use cases, including feature generation and serving.
  5. Cover monitoring, privacy, access control, disaster recovery, and cost controls.

Assume illustrative scale during the discussion: approximately 50,000 events per second at peak, 100 TB of compressed raw events per day, and a five-minute freshness target for streaming aggregates. State which assumptions would change your design.