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 Real-Time Event Processing Pipeline

MediumPipelines00:00
Practice interviewer
In session
5 left
00:00

Your question is Design Real-Time Event Processing Pipeline. 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

Context

PulseCart, a mid-size e-commerce platform, currently processes application events with hourly batch ETL into Snowflake. This architecture is sufficient for historical reporting, but it cannot support near-real-time fraud detection, inventory updates, or live operational dashboards.

You need to design a scalable real-time data processing system that ingests events from web, mobile, and backend services, validates and enriches them, and makes them queryable for analytics and downstream consumers within minutes.

Scale Requirements

  • Sources: Web SDK, mobile SDK, checkout service, order service, inventory service
  • Peak throughput: 250K events/second, 60K average
  • Event size: 1-3 KB JSON
  • Daily volume: ~12 TB raw compressed
  • Latency target: P95 end-to-end under 2 minutes
  • Retention: 30 days hot, 1 year cold archive
  • Availability: 99.9% pipeline uptime

Requirements

  1. Design ingestion for high-throughput event streams with replay capability and ordered processing where needed.
  2. Implement schema validation, deduplication, late-event handling, and dead-letter routing.
  3. Support real-time transformations for sessionization, order state changes, and inventory aggregates.
  4. Load raw and curated data into a warehouse for BI while also supporting downstream operational consumers.
  5. Define orchestration for streaming jobs, backfills, schema evolution, and recovery workflows.
  6. Propose monitoring for throughput, lag, latency, data quality, and cost.
  7. Explain how you would guarantee idempotency and minimize data loss during failures.

Constraints

  • AWS is the mandated cloud platform.
  • Team has strong SQL/Airflow skills but limited Kafka operations experience.
  • Incremental budget is capped at $35K/month.
  • PCI-sensitive payment fields must not be persisted in raw analytical storage.
  • Existing Snowflake dashboards must remain available during migration.