Dataford
Interview QuestionsInterview GuidesExperiencesCoachingPricing
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 Large Query Performance
00:00
5 left

Optimize Large Query Performance

HardSQL · PostgreSQL

Problem

Describe how you would optimize a slow-running query that joins multiple large event tables containing billions of communication logs at Twilio.

Provide an optimized PostgreSQL query and explain the main performance decisions. Use the supplied tables and restrict processing to communication events from 2025-01-01 through 2025-01-03.

Output

  1. One row per account and communication day.
  2. Columns: account_id, account_name, event_day, messages_sent, delivered_events, failed_events, and total_cost.
  3. Include only accounts with messages in the date range. Sort by account_id, then event_day.

Schema

accounts
ColumnTypeDescription
account_idPKBIGINTTwilio customer account identifier
account_nameVARCHAR(120)Customer account name
communication_messages
ColumnTypeDescription
message_idPKBIGINTUnique communication message identifier
account_idBIGINTOwning customer account
event_tsTIMESTAMPMessage creation timestamp
message_delivery_events
ColumnTypeDescription
delivery_event_idPKBIGINTUnique delivery event identifier
message_idBIGINTRelated communication message
event_tsTIMESTAMPDelivery event timestamp
delivery_statusVARCHAR(30)Delivery outcome such as delivered or failed
message_cost_events
ColumnTypeDescription
cost_event_idPKBIGINTUnique cost event identifier
message_idBIGINTRelated communication message
event_tsTIMESTAMPCost event timestamp
cost_amountNUMERIC(12,4)Cost associated with the event
Tablesaccountscommunication_messagesmessage_delivery_eventsmessage_cost_events
Interviewer

Your question is Optimize Large Query Performance. Start with the requirements and the four 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.