Data engineering interview questions · medium
How would you handle data type changes for an existing column?
How would you handle duplicate or corrupted data in a batch ETL job?
How would you handle nulls in a SQL join? Provide examples using COALESCE.
How would you identify duplicate records based on a composite key in SQL?
How would you optimize a query fetching sales data across multiple countries with billions of rows?
How would you optimize a query with multiple joins and subqueries?
How would you prevent small file problems in S3 when loading data into Redshift?
How would you retrieve the first and last order for each customer from a sales table?
Identify and remove duplicate records from a table, keeping the most recent record based on a timestamp column.
If manual partitions are created in a Hive data-warehouse table directory, and you query records from those partitions, will you see the data? If not, how can this be fixed?
Implement a CASE WHEN condition - medium difficulty
Indexing – Types and Benefits?
Indexing: When to Use and Avoid
Integration of Snowflake with external data sources such as S3, GCS, and Blob Storage?
Joins: Different types and their use cases
Kafka Partitioning: How would you ensure even load distribution across Kafka partitions in a high-volume system?
Lead and Lag in SQL Using PySpark DataFrame API
List the different types of joins in SQL.
Materialized View - explain and use cases
Normalization vs Denormalization
Type or paste your answer to any of these questions and our AI Coach scores it, highlights gaps, and rewrites it at FAANG quality. Free to try.
SQL is the most tested topic in data engineering interviews. Most companies dedicate an entire round to SQL, typically asking 3-5 questions covering window functions, CTEs, joins, optimization, and platform-specific features.
Focus on: window functions (RANK, ROW_NUMBER, LAG/LEAD), CTEs and recursive queries, query optimization and execution plans, indexing strategies, and platform-specific features for BigQuery, Redshift, or Snowflake depending on the company.
Yes. Data engineering SQL rounds emphasize analytical queries (window functions, aggregations), large-scale optimization (partitioning, indexing), and data warehouse concepts (star schema, slowly changing dimensions). Software engineering SQL tends to focus on CRUD operations and basic joins.
For a mid-level data engineering role, plan 2-4 weeks of focused SQL practice. Cover window functions, CTEs, optimization, and practice writing queries under time pressure. Use real interview questions from companies you're targeting.