Data engineering interviews have changed. Five years ago, you could get by knowing some SQL and Spark. Today, senior DE panels run 5–7 rounds covering everything from streaming architecture to cost optimisation.
This guide is based on patterns from hundreds of real DE interview questions. Here's what you'll actually face — and how to prepare.
What Interviewers Test (And Why)
Most DE interviewers are trying to answer three questions:
- Can you build things that work? (technical depth)
- Do you understand the tradeoffs? (engineering judgement)
- Have you seen things break? (production experience)
Every question format maps to one of these. Once you recognise the pattern, your answer structure becomes obvious.
The 5 Core Question Formats
1. Explain the Mechanism
"How does Kafka guarantee exactly-once delivery?"
These test depth. Interviewers want you to go beyond surface definitions. The pattern:
- Start with the problem it solves
- Explain the mechanism (idempotent producers + transactional API + consumer offsets)
- Name the trade-off (latency, complexity)
If you can explain why a mechanism exists, you demonstrate real understanding rather than memorised facts.
2. Design Decision
"You need to move 50TB of historical data from S3 to BigQuery. How do you approach this?"
Not a trick question — there's no single right answer. They want to see:
- You ask clarifying questions (SLAs? Schema drift? Budget?)
- You propose options with trade-offs, not a single "best" path
- You think about failure modes before they ask
3. Spot the Bug
"This dbt model is producing duplicate rows in your fact table. What are you looking for?"
These test debugging instincts. Walk through your mental model:
- State your hypothesis first
- Show how you'd verify it (query, log check, explain plan)
- Fix and prevent recurrence
The fix is less important than the diagnostic process.
4. Trade-off Analysis
"Kafka vs Kinesis — when would you choose each?"
The trap is picking a side too quickly. Strong answers:
- Acknowledge the actual question (operational burden vs managed service? volume? latency?)
- Give concrete scenarios where each wins
- Name what you'd need to know before deciding
5. Scenario Analysis
"Your nightly batch job has been running 4 hours instead of the usual 45 minutes. What do you do?"
Pure production experience. They want triage instincts:
- Where do you look first? (resource contention, data skew, upstream volume spike)
- How do you communicate while investigating?
- What's your rollback / stop-loss if it doesn't finish?
The Topics That Get DE Interviews Passed or Failed
Based on question bank data, here's where candidates most commonly struggle:
SQL Window Functions
Not ROW_NUMBER() basics — the subtle stuff:
- Frame clauses (
ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) PARTITION BYon high-cardinality columns (performance)- Combining window functions with aggregates without CTEs
Pipeline Orchestration
Most candidates know what Airflow does. Fewer can articulate:
- Idempotency design — why
execution_datematters - Backfill strategies and their risks
- How to handle upstream dependency failures without cascading failures
Slowly Changing Dimensions
Type 2 SCDs still appear in ~60% of senior DE panels. The common gaps:
- When to use Type 1 vs Type 2 vs Type 4
- The surrogate key pattern and why natural keys break Type 2
- How SCD2 interacts with fact table design
Data Quality
This is increasingly a first-class concern. Beyond "add tests":
- How do you validate at ingestion vs transformation vs serving?
- Reconciliation patterns between source and warehouse
- What happens when quality checks fail mid-pipeline?
How to Practise Effectively
Passive reading doesn't build interview recall. The research on this is clear: you need retrieval practice — attempting to answer questions from memory, then reviewing.
What works:
- Write out your answer, then compare to a model answer
- Score yourself on specifics (did you mention the mechanism? the trade-off? the failure mode?)
- Focus on weak topics, not comfortable ones
What doesn't:
- Re-reading notes
- Watching tutorial videos without coding
- "I'll wing the SQL"
Most candidates under-prepare for the system design component. It's the hardest to cram but the highest signal for senior roles. Block dedicated time for it.
The One Question to Ask Yourself Before Every Answer
"Am I explaining the why, or just the what?"
Interviewers can Google the what. They're hiring you for the judgement to know when and why — and that only comes through in answers that include trade-offs, failure modes, and real examples.
Want to practice all of this? polydomainai has 1,200+ AI-scored DE interview questions across every topic above. You get instant feedback on your answers with rubric scoring — not just "correct/wrong" but why your answer was strong or missed the mark.