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
Optimize Slow Database Query
00:00
5 left

Optimize Slow Database Query

MediumSQL · PostgreSQL

Problem

Explain how you would optimize a slow-running database query that handles millions of customer records at PayJoy.

For the practical portion, provide a PostgreSQL query that returns active customers with active loans, a positive outstanding balance, and no successful latest payment. Assume the query must remain correct at large scale.

Output

  1. One row per qualifying loan, with customer_id, full_name, loan_id, outstanding_balance, latest_payment_date, and latest_payment_status
  2. Include only active customers and loans with a positive balance whose latest payment is missing or not successful
  3. Order by outstanding_balance descending, then customer_id ascending

Schema

customers
ColumnTypeDescription
customer_idPKINTUnique PayJoy customer identifier
full_nameVARCHAR(120)Customer's full name
statusVARCHAR(20)Customer account status
loans
ColumnTypeDescription
loan_idPKINTUnique loan identifier
customer_idINTCustomer who owns the loan
principal_amountNUMERIC(12,2)Original loan principal
statusVARCHAR(20)Current loan status
payments
ColumnTypeDescription
payment_idPKINTUnique payment identifier
loan_idINTLoan associated with the payment
payment_dateDATEDate the payment was recorded
amountNUMERIC(12,2)Payment amount
statusVARCHAR(20)Payment processing status
Tablescustomersloanspayments
Interviewer

Your question is Optimize Slow Database Query. 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.