Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
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 feedbackSuccess 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 Poorly Performing SQL
00:00
5 left

Optimizing Poorly Performing SQL

HardSQL · PostgreSQL

Problem

How do you optimize a query that is performing poorly on a large dataset?

Using the supplied schema and data, write an efficient PostgreSQL query for the report and explain how you would validate and improve its execution plan. Preserve active engagements even when they have no qualifying events.

Output

  1. One row per active engagement with engagement_id, client_name, billable_hours, latest_event_at, and latest_review_status
  2. Include billable events from 2025-01-01 through 2025-03-31
  3. Order by engagement_id ascending

Schema

engagements
ColumnTypeDescription
engagement_idPKINTUnique engagement identifier
client_nameVARCHAR(100)Client associated with the engagement
statusVARCHAR(20)Current engagement status
engagement_events
ColumnTypeDescription
event_idPKINTUnique event identifier
engagement_idINTRelated engagement
event_atTIMESTAMPTimestamp when the event occurred
event_typeVARCHAR(30)Event classification
hoursDECIMAL(8,2)Hours attributed to the event
engagement_reviews
ColumnTypeDescription
review_idPKINTUnique review identifier
engagement_idINTReviewed engagement
reviewed_atTIMESTAMPTimestamp when the review was completed
review_statusVARCHAR(30)Review outcome
Tablesengagementsengagement_eventsengagement_reviews
Interviewer

Your question is Optimizing Poorly Performing SQL. 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.