Interview Questions

Data Engineer Interview Questions

10 questions you are likely to meet in a Data Engineer interview. For each one: what a strong answer covers, and the free lesson that prepares it.

  • 10 Questions
  • 8 Skills
  • Reviewed 16 November 2026

How the Interview Usually Runs

Usually a SQL and Python round, a data modeling round, a pipeline design round and a behavioral round.

Foundations

The concepts interviewers check first.

  1. What is the difference between ETL and ELT?

    What a strong answer covers

    ETL transforms data before loading it into the warehouse; ELT loads raw data first and transforms it inside the warehouse, which modern cloud warehouses make cheap. ELT keeps raw history and suits tools such as dbt.

    Prepared InS4 · #52Data Engineering Basics, coming in Season 4

  2. What are the differences between a data warehouse, a data lake and a lakehouse?

    What a strong answer covers

    A warehouse stores structured, modeled data for analysis; a lake stores raw files of any type cheaply; a lakehouse adds tables, transactions and governance on top of lake storage to get both.

    Prepared InS4 · #52Data Engineering Basics, coming in Season 4

  3. Explain normalization, and when you would denormalize.

    What a strong answer covers

    Normalization splits data into related tables to avoid duplication and update errors. You denormalize, for example into a star schema, when read speed and simple analytics matter more than storage.

    Prepared InS4 · #45Database Design and PostgreSQL, coming in Season 4

Hands-on

How you would actually build or do it.

  1. How do you test data quality in a pipeline?

    What a strong answer covers

    Define checks on completeness, uniqueness, validity, consistency and freshness, run them at each stage, fail or quarantine bad data, alert the owner, and track quality KPIs over time.

    Prepared InS4 · #54Data Governance and Master Data Management, coming in Season 4

  2. How would you prepare SharePoint files and PDFs for a RAG system?

    What a strong answer covers

    Extract text with layout awareness and OCR where needed, clean it, chunk it with structure, attach metadata such as source, version, date and access rights, and schedule updates and deletions.

    Prepared InS9 · #108Building an Enterprise Knowledge Base, coming in Season 9

  3. What makes a pipeline idempotent, and why does it matter?

    What a strong answer covers

    Running it twice gives the same result as running it once, for example by overwriting partitions or using unique keys with upserts. It makes retries and backfills safe after failures.

    Prepared InS11 · #129FastAPI, coming in Season 11

Scenario

Open problems: design, debugging and judgment.

  1. A daily pipeline failed overnight and the dashboards are wrong. What do you do?

    What a strong answer covers

    Tell users the data is stale, read the logs to find the failing task, fix the cause, rerun safely, verify the numbers, and add a check or alert so the next failure is caught before people see it.

    Prepared InS4 · #53The Modern Data Stack, coming in Season 4

  2. Design a pipeline that keeps a vector index in sync with a changing document store.

    What a strong answer covers

    Detect changes with change data capture or modified dates, re-embed only changed documents, delete removed ones, keep version and access metadata, and monitor freshness and failures.

    Prepared InS9 · #108Building an Enterprise Knowledge Base, coming in Season 9

  3. Batch or streaming: how do you choose?

    What a strong answer covers

    Start from how fresh the data must be and what it costs. Batch is simpler and cheaper for daily reports; streaming suits fraud alerts or live monitoring where minutes matter.

    Prepared InS4 · #52Data Engineering Basics, coming in Season 4

Behavioral

Your experience, told with the STAR method.

  1. Tell me about a time you found a data problem others had missed.

    What a strong answer covers

    A STAR story: how you noticed it, how you proved it, the impact it had, and the check you added so it would not happen again.

    Prepared InS17 · #224Behavioral Interviews and Negotiation, coming in Season 17

Skills Checklist

What Data Engineer interviews test, each with the free lesson that teaches it. Tick what you can already explain.

0 of 8 ready
  • S4 · #45Database Design and PostgreSQL

  • S2 · #24File I/O and Parsing

  • S4 · #52Data Engineering Basics

  • S4 · #53The Modern Data Stack

  • S4 · #54Data Governance and Master Data Management

  • S4 · #55Ingesting Messy Documents

  • S9 · #100Vector Databases

    What is a Vector Database?
  • S9 · #108Building an Enterprise Knowledge Base

    What is Retrieval-Augmented Generation?

Your Next Step

Learn Everything These Questions Test

The Data Engineer path takes you there lesson by lesson, from zero, for free.

Prepare for the Interview, Free

Every ai2hired lesson is built from real AI job ads, and the last season is all about getting hired.