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 Multi-Account Reconciliation Breaks

HardSQL & Data Manipulation00:00
Practice interviewer
In session
5 left
00:00

Your question is Investigate Multi-Account Reconciliation Breaks. 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.

Reconciliation Break Investigation

Problem

You are given a reconciliation break across multiple accounts and funding sources. Explain how you would use SQL to isolate the mismatch, identify the accounts driving the variance, and separate missing records, duplicate postings, timing differences, and null mapping issues.

Scope

Focus on the SQL investigation pattern you would use in PostgreSQL: how you would align the data grain, compare expected versus posted amounts, and drill from summary variance down to transaction-level exceptions.

What You Can Assume

  • The data is split across source, posted, and adjustment records.
  • Some rows may be missing a funding source or account mapping.
  • The mismatch may be caused by duplicates, late postings, or reversals.
  • You should explain how to make the investigation auditable and repeatable.

What Your Answer Should Cover

  • How you would structure the SQL investigation.
  • How you would compare totals at the correct grain.
  • How you would surface unmatched and conflicting rows.
  • How you would prioritize the largest breaks for follow-up.