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 ETL Pipeline for Exactly-Once Processing

HardPipelines00: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

Context

FinTechCorp, a financial services company, processes millions of transactions daily. Currently, their ETL pipeline employs at-least-once semantics, leading to duplicate entries in their data warehouse (Snowflake) and complicating downstream analytics. The VP of Data Engineering has mandated a redesign to achieve exactly-once processing semantics to enhance data integrity and reliability.

Scale Requirements

  • Throughput: 1M transactions per second during peak hours.
  • Latency: Data should be available for querying in Snowflake within 2 minutes of ingestion.
  • Storage: Approximately 20 TB of data daily, requiring efficient storage management and cost control.

Requirements

  1. Implement a streaming ingestion layer that guarantees exactly-once delivery of transaction records.
  2. Utilize a message broker (e.g., Apache Kafka) with idempotent producers to prevent duplicates.
  3. Design a transformation layer that applies business logic while maintaining data integrity.
  4. Ensure data is loaded into Snowflake with proper deduplication and error handling mechanisms.
  5. Establish monitoring and alerting for data quality issues, including duplicate detection and processing failures.

Constraints

  • Team: 5 data engineers, limited experience with Kafka.
  • Infrastructure: AWS-based, leveraging existing resources (EC2, S3, Snowflake).
  • Budget: $30K/month for cloud services, including storage and compute.