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

Fixing Slow SQL Queries

MediumSQL · PostgreSQL

Problem

How do you optimize a slow-running SQL query at Citi?

Using the accounts and transactions tables, write an optimized PostgreSQL query that returns active accounts whose completed transactions during Q1 2025 total at least 1,000. The query should avoid unnecessary rows before aggregation and produce a deterministic result.

Output

  1. One row per qualifying active account
  2. Columns: account_id, account_name, q1_completed_amount, completed_transaction_count
  3. Include only completed transactions from 2025-01-01 through 2025-03-31 and accounts meeting the amount threshold
  4. Order by q1_completed_amount descending, then account_id ascending

Schema

accounts
ColumnTypeDescription
account_idPKINTUnique account identifier
account_nameVARCHAR(100)Account holder name
account_statusVARCHAR(20)Current account status
account_typeVARCHAR(30)Account product type
transactions
ColumnTypeDescription
transaction_idPKINTUnique transaction identifier
account_idINTRelated account identifier
transaction_dateDATETransaction posting date
statusVARCHAR(20)Transaction processing status
amountDECIMAL(12,2)Transaction amount
Tablesaccountstransactions
Interviewer

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