Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Get started
Validating Dashboard Data Accuracy
00:00
5 left

Validating Dashboard Data Accuracy

MediumSQL · PostgreSQL

Problem

Describe your process for validating data accuracy when building a dashboard for executive stakeholders.

Use the provided source and dashboard tables to demonstrate the validation process for monthly completed-transaction metrics. Return every month represented by either table and classify whether the dashboard values match the source calculations.

Output

  1. One row per reporting month with metric_month, source revenue and count, dashboard revenue and count, revenue variance, and validation_status.
  2. Include missing and unexpected months, and classify each row as MATCH, MISMATCH, MISSING_DASHBOARD_MONTH, or UNEXPECTED_DASHBOARD_MONTH.
  3. Order by metric_month ascending.

Output details

  • Return columns in this order: metric_month, source_revenue, dashboard_revenue, revenue_variance, source_transaction_count, dashboard_transaction_count, validation_status.
  • Calculate source metrics from rows where status equals completed, summing amount and counting every transaction.
  • Represent source months as the first calendar day of each transaction month, while preserving dashboard metric_month values exactly.
  • Compute revenue_variance as dashboard revenue minus source revenue, returning NULL whenever either revenue value is NULL.
  • Classify matching months as MATCH only when both revenues and both counts are equal, including zero values.
  • Preserve numeric precision without rounding, and retain NULL values rather than converting them to zero.

Schema

source_transactions
ColumnTypeDescription
transaction_idPKINTUnique source transaction identifier
transaction_dateDATEDate of the transaction
amountNUMERIC(12,2)Transaction amount
statusVARCHAR(20)Transaction processing status
dashboard_monthly_metrics
ColumnTypeDescription
metric_monthPKDATEMonth represented by the dashboard metric
reported_revenueNUMERIC(12,2)Revenue displayed in the dashboard
reported_transaction_countINTTransaction count displayed in the dashboard
refreshed_atTIMESTAMPTimestamp of the dashboard metric refresh
Tablessource_transactionsdashboard_monthly_metrics
Interviewer

Your question is Validating Dashboard Data Accuracy. Start with the requirements and the two tables in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.