Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
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
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess 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
Build my plan

Validate Dashboard Data Before Launch

EasyPipelines00:00
Practice interviewer
In session
5 left
00:00

Your question is Validate Dashboard Data Before Launch. 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).

You need to log in / sign up to chat or submit.

Problem

Context

MetricFlow, a B2B SaaS company, builds executive dashboards in Tableau on top of Snowflake. Today, product and finance metrics are loaded through nightly ELT pipelines orchestrated by Apache Airflow, but dashboard validation is mostly manual and inconsistent, causing metric mismatches before launches.

You need to design a production-ready validation pipeline that verifies dashboard data accuracy before a new dashboard or metric goes live. The solution should validate source-to-dashboard consistency, freshness, completeness, and business logic correctness, while fitting into the existing Snowflake + dbt + Airflow stack.

Scale Requirements

  • Sources: PostgreSQL OLTP, Stripe exports in S3, Segment event logs in Kafka
  • Volume: 250M event rows/day, 40M transactional rows/day, 12 TB warehouse data
  • Dashboards: 180 Tableau dashboards, 1,200 metric tiles
  • Validation window: complete pre-release validation in < 20 minutes
  • Freshness SLA: dashboard tables must be < 2 hours old
  • Historical checks: compare against 90 days of prior metric values

Requirements

  1. Design a validation pipeline that runs automatically before dashboard publication.
  2. Validate schema, row-count completeness, null rates, duplicate keys, and referential integrity across raw, staging, and mart layers.
  3. Reconcile critical business metrics (for example: revenue, active users, conversion) between source systems, dbt models, and final dashboard queries.
  4. Detect anomalies versus historical baselines and block release when thresholds are exceeded.
  5. Support idempotent reruns, backfills for historical dashboard versions, and auditable validation results.
  6. Expose validation status to analysts and trigger alerts for failures.

Constraints

  • Existing stack must remain: Snowflake, dbt Core, Airflow 2.x, Tableau.
  • Team size is 3 data engineers and 2 analytics engineers.
  • Budget allows only modest incremental compute; avoid always-on clusters.
  • Finance dashboards are SOX-relevant, so validation logs must be retained for 1 year.
  • No manual sign-off should be required for low-risk dashboard updates if all checks pass.