Reviewed by Aditya Kumar · Last reviewed 2026-03-24
To remove duplicates keeping the most recent by timestamp: WITH ranked AS (SELECT *, ROW_NUMBER() OVER (PARTITION BY key_columns ORDER BY timestamp_col DESC) rn FROM table_name) DELETE FROM table_name WHERE (key_columns, timestamp_col) IN (SELECT key_columns, timestamp_col FROM...
This medium-level SQL question appears frequently in data engineering interviews at companies like Goldman Sachs. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (partition, spark, sql) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
To remove duplicates keeping the most recent by timestamp: WITH ranked AS (SELECT , ROW_NUMBER() OVER (PARTITION BY key_columns ORDER BY timestamp_col DESC) rn FROM table_name) DELETE FROM table_name WHERE (key_columns, timestamp_col) IN (SELECT key_columns, timestamp_col FROM ranked WHERE rn > 1). Or create a new table: CREATE TABLE deduped AS SELECT FROM (SELECT *, ROW_NUMBER() OVER (PARTITION BY id ORDER BY updated_at DESC) rn FROM raw) t WHERE rn=1. In Spark: df.dropDuplicates(['id']).orderBy(col('ts').desc())—but dropDuplicates is non-deterministic; use Window: from pyspark.sql.window import Window; w = Window.partitionBy('id').orderBy(col('ts').desc()); df.withColumn('rn', row_number().over(w)).filter('rn=1').drop('rn'). Why it matters: Design choices compound at scale—wrong approach can cause 100× overhead. Scalability trade-offs: Profile before optimizing; validate on sample then full. Cost implications: Suboptimal choices multiply at billion-row scale.
Red Flag: Assuming pipeline success means data correctness. Pro-Move: 'We added row checksums and reconciliation—caught 0.02% drift that success status missed.'
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.