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
Regional Claims Summary with Data Quality Checks
00:00
5 left

Regional Claims Summary with Data Quality Checks

MediumSQL · PostgreSQL

Problem

Walk me through your analysis of this dataset.

Use the provided policyholder, claim, and payment data. Produce a regional claims summary that includes payment totals, closure timing, and records requiring data-quality review.

Output

  1. One row per region, including Unknown for claims without a usable region.
  2. Return region, claim_count, total_incurred, total_paid, average_days_to_close, and review_claim_count.
  3. Include all claims, sort by claim_count descending, then region ascending.

Output details

  • Sum each claim’s payment records once, and treat claims without payments as contributing 0 to total_paid.
  • Treat missing incurred_amount values as zero in total_incurred, including when all regional values are missing.
  • Calculate average_days_to_close from non-NULL closed_date values, retain negative durations, return NULL when none qualify, and round to two decimals.
  • Count a claim for review when incurred_amount is NULL, payments exceed incurred_amount, or closed_date precedes opened_date.

Schema

policyholders
ColumnTypeDescription
policyholder_idPKINTUnique policyholder identifier
policyholder_nameVARCHAR(100)Policyholder name
regionVARCHAR(50)Policyholder region
claims
ColumnTypeDescription
claim_idPKINTUnique claim identifier
policyholder_idINTRelated policyholder identifier
opened_dateDATEDate the claim was opened
closed_dateDATEDate the claim was closed
incurred_amountDECIMAL(12,2)Expected total claim cost
claim_statusVARCHAR(20)Current claim status
claim_payments
ColumnTypeDescription
payment_idPKINTUnique payment identifier
claim_idINTRelated claim identifier
payment_dateDATEDate of payment
payment_amountDECIMAL(12,2)Payment amount
payment_methodVARCHAR(20)Payment method
Tablespolicyholdersclaimsclaim_payments
Interviewer

Your question is Regional Claims Summary with Data Quality Checks. 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.