How would you index a filter-and-sort API: category, price range, and created_at desc?
PICTURE THIS: DATABASE INDEX
Simple meaning
A composite index that matches equality then range then order, such as (category_id, price, created_at), can serve the query without a sort if the planner agrees.
WHY — SQL instead of guessing?
Why interviewers care about SQL:
question about SQL.
trade-offs, and what you would actually do on a Backend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1A composite index that
matches equality then range then order, such as (category_id, price, created_at), can serve the query without a sort if the planner agrees.
- 2If users sort by
many columns, you cannot cover every permutation
- 3pick the hottest and
consider a search engine.
- 4Measure with EXPLAIN on
production-like data, not ten demo rows.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
A composite index that matches equality then range then order, such as (category_id, price, created_at), can serve the query without a sort if the planner agrees. If users sort by many columns, you cannot cover every permutation