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
Optimizing Slow SQL Queries
00:00
5 left

Optimizing Slow SQL Queries

MediumSQL · PostgreSQL

Problem

How do you approach optimizing slow-running SQL queries and stored procedures in large-scale relational databases?

Using the provided PostgreSQL tables, write an optimized query that identifies active accounts with at least 100 billable usage units during 2025. The query should avoid unnecessary row multiplication and preserve accounts even when plan details are missing.

Output

  1. One row per qualifying active account with account_id, account_name, plan_name, and total_billable_units
  2. Include only accounts with at least 100 billable units during 2025
  3. Sort by total_billable_units descending, then account_id ascending

Schema

accounts
ColumnTypeDescription
account_idPKINTUnique account identifier
account_nameVARCHAR(100)Account display name
statusVARCHAR(20)Current account status
plan_idINTReferenced subscription plan
created_atDATEAccount creation date
plans
ColumnTypeDescription
plan_idPKINTUnique plan identifier
plan_nameVARCHAR(80)Subscription plan name
monthly_feeDECIMAL(10,2)Monthly plan fee
is_activeBOOLEANWhether the plan is currently offered
usage_events
ColumnTypeDescription
event_idPKINTUnique usage event identifier
account_idINTAccount associated with the event
occurred_atDATEDate when usage occurred
event_typeVARCHAR(20)Usage classification
unitsINTNumber of usage units
Tablesaccountsplansusage_events
Interviewer

Your question is Optimizing Slow SQL Queries. 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.