Optimize a slow query on events
Last updated: April 16, 2026
Quick Overview
A query on events is running slowly. Identify the bottleneck and optimize it.
Expedia
April 16, 202626
5
1,977 solved
A query on events is running slowly. Identify the bottleneck and optimize it.
This question from Expedia's Take-home Project tests practical data skills. The interviewer wants to see clean, efficient queries that handle edge cases like NULLs, duplicates, and large datasets.
What the Interviewer Expects
- Write syntactically correct SQL with proper JOIN and WHERE clauses
- Use GROUP BY and aggregate functions appropriately
- Handle NULL values correctly in your queries
- Explain the query execution plan at a high level
Key Topics to Cover
How to Approach This
- Clarify the schema and expected output format before writing queries.
- Use CTEs (WITH clauses) to break complex queries into readable steps.
- Consider window functions (ROW_NUMBER, RANK, LAG, LEAD) for ranking and sequential analysis.
- Watch for NULLs, duplicates, and edge cases in JOINs and GROUP BY.
- For pandas, prefer vectorized operations over row-by-row iteration.
Possible Follow-up Questions
- How would you validate the correctness of your query results?
- Can you rewrite this without using subqueries?
- How would you handle slowly changing dimensions in this scenario?
- How would you handle this if the data was spread across multiple databases?
Sharpen Your Skills on Codemia
Practice similar problems with our interactive workspace, get AI feedback, and track your progress.
Practice SQL ProblemsSample Answer
Approach
Break the problem into logical steps before writing SQL. Think about: 1. What tables do I need to join and on which keys? 2. What filtering (WHERE) d...
Solution Pattern
```sql WITH filtered_data AS ( SELECT * FROM main_table WHERE condition = 'value' AND date_col >= '2024-01-01' ), aggregated AS ( SELECT ...
Submit Your Answer
