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
Monthly Claims Trend and Anomaly Detection
00:00
5 left

Monthly Claims Trend and Anomaly Detection

HardSQL · PostgreSQL

Problem

Analyze monthly claim payment trends in Global Healthcare Exchange data and identify provider-month anomalies in Q1 2024. Your query should keep months with no approved claims, summarize approved activity by provider and month, compute each provider's average monthly paid amount across the quarter, and classify each month as Anomaly or Normal using a 20% threshold from that average.

Schema

ghe_providers
ColumnTypeDescription
provider_id
provider_name
ghe_claims
ColumnTypeDescription
claim_id
provider_id
member_id
claim_date
status
paid_amount
ghe_calendar_months
ColumnTypeDescription
month_start
month_label
Tablesghe_providersghe_claimsghe_calendar_months
Interviewer

Your question is Monthly Claims Trend and Anomaly Detection. 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.