Your question is Handling Nulls in Dashboard Metrics. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Explain how you handle NULL values in SQL-backed visualizations without changing the meaning of the data. Focus on when to preserve missing values, when to replace them, and how aggregate functions behave in PostgreSQL.
NULL semanticsCOALESCECOUNT(*), COUNT(column), AVG(), and SUM()CASE WHEN to expose missingness in dashboard outputsIn a Synechron visualization workflow, the interviewer is looking for practical SQL judgment: can you make a chart readable without converting missing data into false business signals?