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
Troubleshoot Slow Query Plans
00:00
5 left

Troubleshoot Slow Query Plans

HardSQL · PostgreSQL

Problem

How would you troubleshoot a slow query using execution plans?

Explain a repeatable PostgreSQL workflow for identifying the bottleneck, validating whether indexes are useful, and separating planner estimates from actual execution behavior. Address join strategies, row estimates, sorting, aggregation, buffer activity, and statistics.

Output

  1. A concise diagnosis workflow and the plan evidence to inspect
  2. Recommended validation steps and possible corrective actions
  3. A PostgreSQL query that can be analyzed with EXPLAIN (ANALYZE, BUFFERS)

Schema

customers
ColumnTypeDescription
customer_idPKINTCustomer identifier
customer_nameVARCHAR(100)Customer display name
orders
ColumnTypeDescription
order_idPKINTOrder identifier
customer_idINTCustomer who placed the order
created_atDATEOrder creation date
order_items
ColumnTypeDescription
order_item_idPKINTOrder item identifier
order_idINTOrder containing the item
quantityINTNumber of units
unit_priceNUMERIC(10,2)Price per unit
Tablescustomersordersorder_items
Interviewer

Your question is Troubleshoot Slow Query Plans. 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.