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
Detect Account, Field, and Duplicate Errors
00:00
5 left

Detect Account, Field, and Duplicate Errors

MediumSQL · PostgreSQL

Problem

How would you approach validating a large, inconsistent dataset to ensure accuracy?

Use source_transactions as the dataset being validated and valid_accounts as the reference data. Write a query that returns every invalid source record and identifies the applicable data quality issues.

Output

  1. One row per invalid source record, ordered by source_id ascending
  2. Columns: source_id, account_code, validation_status, issue_count, account_check, duplicate_record
  3. Exclude records that have no detected validation issue

Output details

  • Flag account_code as missing when NULL, unmatched when absent from valid_accounts, inactive when is_active is FALSE, otherwise matched.
  • Flag missing transaction_date values as issues.
  • Flag amount as an issue when NULL or less than or equal to 0.
  • Flag status as an issue when NULL or not one of posted, pending, or void.
  • Mark records sharing identical account_code, transaction_date, amount, and status values as duplicate records, including matching NULLs.
  • Set validation_status to INVALID and calculate issue_count as the number of flagged account, date, amount, status, and duplicate issues.

Schema

source_transactions
ColumnTypeDescription
source_idPKINTUnique identifier for the source record
account_codeVARCHAR(20)Account identifier supplied by the source dataset
transaction_dateDATEDate associated with the transaction
amountNUMERIC(12,2)Transaction amount
statusVARCHAR(20)Source transaction status
valid_accounts
ColumnTypeDescription
account_codePKVARCHAR(20)Reference account identifier
account_nameVARCHAR(100)Reference account name
is_activeBOOLEANWhether the account is currently active
Tablessource_transactionsvalid_accounts
Interviewer

Your question is Detect Account, Field, and Duplicate Errors. Start with the requirements and the two 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.