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
Test Coverage and SQL Logic
00:00
5 left

Test Coverage and SQL Logic

HardSQL · PostgreSQL

Problem

How would you ensure you have good test coverage when working with SQLLite queries that increment and decrement a score using a WHERE condition?

Use the provided PostgreSQL tables to apply eligible score changes and return the affected scores. Coverage should account for increments, decrements, zero and NULL amounts, disabled changes, invalid operations, missing scores, and NULL current scores.

Output

  1. Return one row per updated score with score_id, new_score, net_change, and applied_change_count.
  2. Include only scores changed by eligible requests.
  3. Order by score_id ascending.

Schema

scores
ColumnTypeDescription
score_idPKINTUnique score record identifier
current_scoreINTCurrent score value
score_changes
ColumnTypeDescription
change_idPKINTUnique score change identifier
score_idINTReferenced score record
operationVARCHAR(20)Requested operation
amountINTMagnitude of the requested change
appliesBOOLEANWhether the request is enabled
created_atTIMESTAMPCreation timestamp used for deterministic ordering
Tablesscoresscore_changes
Interviewer

Your question is Test Coverage and SQL Logic. 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.