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
Investigate Reporting Count Discrepancies
00:00
5 left

Investigate Reporting Count Discrepancies

MediumSQL · PostgreSQL

Problem

Compare Alabama Staffing reporting snapshot counts against database-derived confirmed placement counts by client and day for January 2024. Return both totals, the discrepancy, and a status that highlights matches, mismatches, and rows missing from one side.

Schema

Tables
  • clients
  • placements
  • reporting_snapshots

What This Tests

  • Joining aggregated reporting data to source-of-truth data
  • Using CTEs to separate metric definitions
  • Handling NULLs and missing rows correctly
  • Classifying discrepancies with CASE
Tablesclientsplacementsreporting_snapshots
Interviewer

Your question is Investigate Reporting Count Discrepancies. Start with the requirements and the three 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.