Data Engineering · with Answers

ETL Interview Questions with Answers (2026 Prep Guide)

8 min read5 easy · 7 medium · 5 hardLast updated: 22 Apr 2026

Expect rigour on schema evolution, data quality, and warehousing patterns alongside classic algorithms. Each question below is paired with a concise model answer. Explaining query plans and join strategies aloud separates strong candidates.

Part of the hub:ETL Interview Guide →
Start a personalised drillETL Questions Hub

Data-engineering interviews test pipeline reasoning, SQL depth, and system-design intuition in equal measure. In the with answers track specifically, interviewers weight ETL as a proxy for both depth and judgement — the combination that separates an offer from a "close but not this cycle" decision. Ownership of data quality, SLAs, and observability earns senior-level signal.

The fastest way to internalise ETL is deliberate practice against progressively harder scenarios. Begin with the fundamentals so you can discuss definitions, invariants, and trade-offs without fumbling vocabulary. Then move into scenario drills drawn from cases like E-commerce order funnels with late-arriving events. The goal isn't recall — it's the habit of restating a problem, surfacing assumptions, and narrating your decision process out loud.

Interviewers also listen for boundary awareness. When ETL appears in a panel, strong candidates acknowledge where their approach breaks: cost envelope, latency under load, consistency trade-offs, or organisational constraints. Interviewers weight partitioning, idempotency, and schema evolution heavily. Your answers should explicitly name the two or three dimensions on which the solution could flip, and which one you'd optimise given the user's priorities.

Finally, calibrate your preparation against actual panel dynamics. Rehearse each ETL answer out loud, time-box it to three minutes, and iterate based on recorded playback. Pair written study with two to three full mock interviews before the target loop. Clear reasoning about batch-vs-stream trade-offs is a strong differentiator. Showing up with clear structure, measurable examples, and one honest boundary beats a longer monologue on any rubric that actually exists.

Preparation roadmap

  1. Step 1

    Days 1–2 · Fundamentals

    Re-read the ETL basics end to end. If you can't explain it in 90 seconds to a smart non-expert, you're not ready for the panel follow-ups.

  2. Step 2

    Days 3–4 · Scenario drills

    Run six timed drills anchored in real cases — e.g. Media clickstream rollups feeding ML training sets. Verbalise your thinking; recorded audio beats silent practice.

  3. Step 3

    Days 5–6 · Panel simulation

    Two full-loop mock interviews with a peer or adaptive coach. Score yourself against a rubric: restatement, trade-offs, execution, communication.

  4. Step 4

    Day 7 · Weakness blitz

    Target your worst rubric cell from the mocks. Do three focused 20-minute drills specifically on that gap — not new content.

  5. Step 5

    Day 8+ · Cadence

    Hold a 30-minute daily drill plus one weekly mock until the target interview. Consistency compounds faster than marathon weekends.

Top interview questions

  • Q1.What's a non-obvious trade-off that only shows up in production with ETL?

    hard

    Tail latency and cold-start behaviour: both invisible in staging, both punishing when a real workload hits ETL.

    Example

    Real pipeline: Kafka → bronze (Delta) → silver (schema-validated) → gold (aggregated). Idempotency at each layer.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: What breaks first if the job runs on half the cluster?

  • Q2.How would you split preparation time between theory and practice for ETL?

    easy

    Front-load theory, back-load mocks. The last 5 days before an interview are for simulated loops, not new content.

    Example

    dbt example: `{{ incremental() }}` with `unique_key=[user_id, event_id]` reliably dedupes replayed CDC events.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: How do you detect and recover from duplicate writes in production?

  • Q3.What's the most common wrong answer interviewers hear about ETL?

    medium

    Over-indexing on one popular framework leaves blind spots — interviewers test whether you see the whole decision space for ETL.

    Example

    Imagine a 2 TB Spark job: setting `spark.sql.shuffle.partitions=400` and broadcasting a 10 MB dim table cut runtime from 45m to 6m.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: Walk me through the observability you would add before shipping this.

  • Q4.What resources accelerate ETL prep in the last 48 hours before an interview?

    easy

    One focused mock, a 30-minute drill on your weakest sub-topic, and a 10-question warm-up the morning of.

    Example

    Real pipeline: Kafka → bronze (Delta) → silver (schema-validated) → gold (aggregated). Idempotency at each layer.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: Where does your solution fail if data arrives out of order?

  • Q5.How do you recover after bombing a ETL question mid-interview?

    medium

    Reset with a one-sentence summary of your current thinking; it re-anchors both you and the interviewer.

    Example

    dbt example: `{{ incremental() }}` with `unique_key=[user_id, event_id]` reliably dedupes replayed CDC events.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: If latency had to drop 10x, what would you change first?

  • Q6.What's the difference between junior and senior expectations on ETL?

    hard

    At senior bars, fluent trade-off articulation out-weighs code speed — at junior bars, correctness with guidance is enough.

    Example

    Imagine a 2 TB Spark job: setting `spark.sql.shuffle.partitions=400` and broadcasting a 10 MB dim table cut runtime from 45m to 6m.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: How would the answer change if the table was 100x larger?

  • Q7.Imagine the constraints on ETL were halved. What would you change first?

    hard

    Re-examine the core data model first; assumptions baked into the model propagate through every downstream decision about ETL.

    Example

    Real pipeline: Kafka → bronze (Delta) → silver (schema-validated) → gold (aggregated). Idempotency at each layer.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: What breaks first if the job runs on half the cluster?

  • Q8.What would excellent performance look like a year into a role built around ETL?

    medium

    At 12 months, the signal is "we ask them to sanity-check anyone else's ETL work before ship". That's the north star.

    Example

    dbt example: `{{ incremental() }}` with `unique_key=[user_id, event_id]` reliably dedupes replayed CDC events.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: How do you detect and recover from duplicate writes in production?

  • Q9.What is ETL and why is it relevant to this interview round?

    easy

    Because ETL touches both theory and implementation, it's a compact way to check range in a 10–15 minute window.

    Example

    Imagine a 2 TB Spark job: setting `spark.sql.shuffle.partitions=400` and broadcasting a 10 MB dim table cut runtime from 45m to 6m.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: Walk me through the observability you would add before shipping this.

  • Q10.How would you explain ETL to a non-technical stakeholder?

    easy

    Start with the business outcome ETL enables, then outline the mechanism in one paragraph, and close with one concrete example.

    Example

    Real pipeline: Kafka → bronze (Delta) → silver (schema-validated) → gold (aggregated). Idempotency at each layer.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: Where does your solution fail if data arrives out of order?

  • Q11.Walk me through a common pitfall when using ETL under load.

    medium

    Premature optimisation on ETL is common — the fix is to measure first, then target the hottest contributor.

    Example

    dbt example: `{{ incremental() }}` with `unique_key=[user_id, event_id]` reliably dedupes replayed CDC events.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: If latency had to drop 10x, what would you change first?

  • Q12.How would you design a test plan for ETL?

    medium

    Cover three axes — correctness, edge-case robustness, and observability signal — then codify them as CI gates for ETL.

    Example

    Imagine a 2 TB Spark job: setting `spark.sql.shuffle.partitions=400` and broadcasting a 10 MB dim table cut runtime from 45m to 6m.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: How would the answer change if the table was 100x larger?

  • Q13.Design a scalable system that centres on ETL. What are the top 3 trade-offs?

    hard

    Start with capacity / latency / consistency trade-offs. Ownership of data quality, SLAs, and observability earns senior-level signal. For ETL, I'd anchor on the read/write ratio.

    Example

    Real pipeline: Kafka → bronze (Delta) → silver (schema-validated) → gold (aggregated). Idempotency at each layer.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: What breaks first if the job runs on half the cluster?

  • Q14.Describe a real-world failure mode of ETL and how you'd detect it before customers notice.

    hard

    Observability on ETL should cover both rate and distribution — alerting only on averages misses the tail that actually hurts users.

    Example

    dbt example: `{{ incremental() }}` with `unique_key=[user_id, event_id]` reliably dedupes replayed CDC events.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: How do you detect and recover from duplicate writes in production?

  • Q15.How do you prioritise improvements to ETL when time and budget are limited?

    medium

    Ship the smallest version that proves the theory; only invest further in ETL once measured gains justify it.

    Example

    Imagine a 2 TB Spark job: setting `spark.sql.shuffle.partitions=400` and broadcasting a 10 MB dim table cut runtime from 45m to 6m.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: Walk me through the observability you would add before shipping this.

  • Q16.What metrics would you track to know ETL is working well?

    medium

    A north-star outcome metric plus 2–3 leading indicators: that combination tells you both "are we winning" and "why" for ETL.

    Example

    Real pipeline: Kafka → bronze (Delta) → silver (schema-validated) → gold (aggregated). Idempotency at each layer.

    Common mistakes

    • Benchmarking on cold cache — production hits warm cache and the numbers invert.
    • Ignoring skew — one hot key balloons executors while the rest idle.

    Follow-up: Where does your solution fail if data arrives out of order?

  • Q17.What's the smallest proof-of-concept that demonstrates ETL clearly?

    easy

    Prefer a runnable Jupyter / REPL snippet with inputs and outputs over prose; interviewers can re-run it and probe immediately.

    Example

    dbt example: `{{ incremental() }}` with `unique_key=[user_id, event_id]` reliably dedupes replayed CDC events.

    Common mistakes

    • Ignoring skew — one hot key balloons executors while the rest idle.
    • Benchmarking on cold cache — production hits warm cache and the numbers invert.

    Follow-up: If latency had to drop 10x, what would you change first?

Interactive

Practice it live

Practising out loud beats passive reading. Pick the path that matches where you are in the loop.

Try this question liveRun the question through the adaptive AI coach — it grades structure, trade-offs, and communication.Start a mock interviewFull-loop mock with rubric scoring and a recorded replay — ready in under a minute.Get a personalised roadmapTell the coach your target, and get a day-by-day prep plan tuned to your gaps.

Explore by domain

Related roles

Related skills

Practice with an adaptive AI coach

Personalised plan, live mock rounds, and outcome tracking — free to start.

Start a personalised drillRun a mock round

Difficulty mix

This guide is weighted 5 easy · 7 medium · 5 hard — use it as a structured study sheet.

  • Crisp framing for ETL questions interviewers actually ask
  • A difficulty-balanced set: 5 easy · 7 medium · 5 hard
  • Real-world scenarios like Fintech transaction streams with exactly-once semantics — grounded in day-one operational reality