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 Enterprise Data Lake Architecture

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

Your question is Design Enterprise Data Lake Architecture. 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

Northstar Health, a multi-region healthcare analytics company, currently lands CSV extracts from transactional systems directly into Snowflake using nightly batch jobs. The platform now needs a governed data lake architecture to support raw retention, replayable ingestion, lower-cost storage, and mixed workloads for BI, data science, and compliance audits.

You are asked to design a modern AWS-based data lake that separates raw, curated, and serving layers while preserving lineage and data quality across batch and near-real-time sources.

Scale Requirements

  • Sources: 120 operational databases, 40 SaaS APIs, and 15 event streams
  • Ingestion volume: 12 TB/day batch data + 80K events/sec streaming peak
  • File/object count: ~9 million new objects/day
  • Latency targets: batch data available in curated zone within 2 hours; streaming data queryable within 10 minutes
  • Retention: raw zone for 7 years, curated zone for 2 years, serving aggregates indefinite
  • Consumers: 300 BI users, 40 data scientists, 25 downstream applications

Requirements

  1. Design lake zones for raw/bronze, clean/silver, and business-ready/gold datasets.
  2. Support both CDC/batch ingestion and streaming ingestion with replay capability.
  3. Enforce schema evolution, partitioning strategy, deduplication, and idempotent loads.
  4. Implement data quality checks for completeness, freshness, null rates, and referential integrity.
  5. Orchestrate transformations and backfills without impacting production SLAs.
  6. Expose curated data to Snowflake and Athena while maintaining a central metadata catalog.
  7. Provide lineage, auditability, and access controls for PHI-sensitive datasets.

Constraints

  • Must run primarily on AWS using managed services where possible.
  • Incremental budget cap: $60K/month excluding Snowflake compute.
  • Compliance: HIPAA and regional data residency requirements.
  • Team size: 5 data engineers, 1 platform engineer; operational simplicity matters.
  • Existing consumers depend on nightly warehouse tables and cannot tolerate breaking schema changes.