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

Modernize Hadoop to Spark Pipelines

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

Your question is Modernize Hadoop to Spark Pipelines. 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

ShopWave, a mid-size retail marketplace, currently runs nightly Hadoop MapReduce jobs on HDFS to process order, inventory, and clickstream data for reporting. The platform has grown to support near-real-time operational dashboards and faster analytics, so the data team wants to redesign the pipeline using Spark while preserving batch reliability and adding streaming support.

You are asked to design a production-ready data platform that can process both historical and incremental data using a modern big data stack.

Scale Requirements

  • Batch volume: 6 TB/day across orders, inventory, and customer events
  • Streaming volume: 80K events/sec peak from web and mobile applications
  • Latency target: batch outputs available by 6:00 AM; streaming data queryable within 3 minutes
  • Retention: raw data for 180 days, curated warehouse tables for 3 years
  • Data size: average event payload 1.5 KB JSON

Requirements

  1. Design a pipeline that ingests data from OLTP databases, application event streams, and third-party CSV drops.
  2. Use Spark for distributed transformation, including joins, deduplication, schema enforcement, and aggregations.
  3. Support both batch ETL and stream processing paths into a central analytics store.
  4. Orchestrate dependencies, retries, and backfills for daily and hourly jobs.
  5. Implement data quality checks for null keys, duplicate records, schema drift, and late-arriving data.
  6. Provide a strategy for partitioning, storage format, and incremental processing.
  7. Describe monitoring, alerting, and failure recovery for production operations.

Constraints

  • Existing environment is AWS-based with limited appetite for managing large Hadoop clusters.
  • Team size is 3 data engineers and 1 platform engineer.
  • Budget increase is capped at $20K/month.
  • PII fields must be encrypted at rest and deleted within 7 days of a valid privacy request.