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
SQL Metrics by Business Unit
00:00
5 left

SQL Metrics by Business Unit

MediumSQL · PostgreSQL

Problem

Write SQL to analyze claim or operational data and summarize key metrics by business unit or time period.

Using the supplied claims and business_units tables, summarize records dated in 2025 by business unit and calendar month. Include claims whose business unit is not found in the reference table.

Output

  1. One row per business unit and month
  2. Columns: business_unit, claim_month, claim_count, total_incurred, and avg_processing_days
  3. Include only periods containing at least one 2025 claim, ordered by business_unit, then claim_month

Output details

  • Order both business_unit and claim_month in ascending order.
  • Label claims whose business unit is missing from the reference table as Unassigned.
  • Use an inclusive lower bound of DATE '2025-01-01' and an exclusive upper bound of DATE '2026-01-01'.
  • Replace a null total_incurred sum with numeric 0.
  • Round avg_processing_days to two decimal places, leaving it NULL when no processing-day values exist.

Schema

claims
ColumnTypeDescription
claim_idPKINTUnique claim identifier
business_unit_idINTReference to the responsible business unit
claim_dateDATEDate the claim was recorded
incurred_amountNUMERIC(12,2)Amount incurred for the claim
processing_daysINTNumber of days used to process the claim
business_units
ColumnTypeDescription
unit_idPKINTUnique business unit identifier
unit_nameVARCHAR(100)Business unit name
Tablesclaimsbusiness_units
Interviewer

Whenever you're ready, walk me through your approach or go straight to the code. The requirements and the two tables are in the Question tab.

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.