Reviewed by Aditya Kumar · Last reviewed 2026-08-08
Aggregate to the grain you are ranking on, rank within each region, then filter. Aggregating and ranking in one pass Notice that the window function orders by SUM(sales) directly. Window functions are…
This medium-level SQL question appears frequently in data engineering interviews at companies like Fragma Data Systems. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (partition, sql) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones. The expert answer includes a code example that demonstrates the implementation pattern.
Aggregate to the grain you are ranking on, rank within each region, then filter.
SELECT region, product_id, total_sales
FROM (
SELECT region,
product_id,
SUM(sales) AS total_sales,
ROW_NUMBER() OVER (PARTITION BY region
ORDER BY SUM(sales) DESC) AS rn
FROM sales
GROUP BY region, product_id
) ranked
WHERE rn <= 5
ORDER BY region, total_sales DESC;
Notice that the window function orders by SUM(sales) directly. Window functions are evaluated after GROUP BY, so the aggregate is already available and no extra subquery is needed. This surprises people who expect to have to nest twice.
ROW_NUMBER returns exactly five rows per region, breaking ties arbitrarily. That is usually what "top 5" means for a dashboard with fixed layout, but it means two products with identical sales can swap places between runs. Add a deterministic tiebreaker — ORDER BY SUM(sales) DESC, product_id — so results are reproducible.
If a tie at fifth place should include both products, use RANK instead and accept a variable row count. DENSE_RANK returns the top five distinct sales values, which can be many more than five rows. Pick deliberately and state the choice.
Snowflake, BigQuery and DuckDB support QUALIFY, which filters on a window function without the subquery:
SELECT region, product_id, SUM(sales) AS total_sales
FROM sales
GROUP BY region, product_id
QUALIFY ROW_NUMBER() OVER (PARTITION BY region ORDER BY SUM(sales) DESC) <= 5;
PostgreSQL and MySQL have no QUALIFY, so the subquery form is the portable answer.
The window sorts within each partition, so cost scales with the number of distinct region-product pairs rather than raw row count — the GROUP BY has already collapsed the data. Partitioning or clustering the source table by region lets the engine process regions in parallel.
In the interview, also mention that this exact pattern generalises to any "top N per group" problem by changing the partition key.
Red Flag: RANK when ties could yield >5 rows. Pro-Move: 'ROW_NUMBER for exactly 5; RANK if ties must share rank.'
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.