InterviewStack.io LogoInterviewStack.io

Data Quality and Edge Case Handling Questions

Practical skills and best practices for recognizing, preventing, and resolving real world data quality problems and edge cases in queries, analyses, and production data pipelines. Core areas include handling missing and null values, empty and single row result sets, duplicate records and deduplication strategies, outliers and distributional assumptions, data type mismatches and inconsistent formatting, canonicalization and normalization of identifiers and addresses, time zone and daylight saving time handling, null propagation in joins, and guarding against division by zero and other runtime anomalies. It also covers merging partial or inconsistent records from multiple sources, attribution and aggregation edge cases, group by and window function corner cases, performance and correctness trade offs at scale, designing robust queries and pipeline validations, implementing sanity checks and test datasets, and documenting data limitations and assumptions. At senior levels this expands to proactively designing automated data quality checks, monitoring and alerting for anomalies, defining remediation workflows, communicating trade offs to stakeholders, and balancing engineering effort against business risk.

MediumTechnical
82 practiced
In pivoting or crosstab reports, missing combinations often become NULL instead of 0. Describe how to transform pivot results in SQL (or Excel) so missing combinations are shown as zero, and how to implement this in BI tools that auto-pivot. Provide sample SQL/pivot examples.
EasyTechnical
93 practiced
Describe three deduplication strategies (heuristic matching, exact key dedupe, and deterministic primary-key enforcement). For each: explain implementation steps, pros/cons, and cases where it could lead to false positives or false negatives.
HardTechnical
117 practiced
Hard: Design a multi-region strategy to compute daily active users (DAU) per user's local day, taking into account DST transitions, users who travel, and users without a stored timezone. Specify how to store timestamps, timezone metadata, and how to implement queries that produce correct per-local-day aggregates at scale.
MediumTechnical
90 practiced
Two sources provide overlapping customer profiles. Source A has (customer_id, email, phone, updated_at), Source B has (external_id, email, phone, address, last_seen). Write an SQL-based consolidation logic that prioritizes non-null fields from the most recently updated source and falls back to the other source when fields are missing. Show sample rows and the expected merged output.
HardTechnical
70 practiced
Hard: Provide a SQL template and design recommendations that dashboards can use to guard against division-by-zero when computing rates across many groups (where many groups may have 0 impressions). Include both SQL and visualization-layer strategies to avoid misleading spikes due to tiny denominators.

Unlock Full Question Bank

Get access to hundreds of Data Quality and Edge Case Handling interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.