Reviewed by Aditya Kumar · Last reviewed 2026-03-24
2nd highest without MAX: SELECT salary FROM employees e1 WHERE 1 = (SELECT COUNT(DISTINCT salary) FROM employees e2 WHERE e2.salary > e1.salary). Or: SELECT MIN(salary) FROM (SELECT salary FROM employees ORDER BY salary DESC LIMIT 2) t. Or DENSE_RANK: WITH r AS (SELECT salary,...
2nd highest without MAX: SELECT salary FROM employees e1 WHERE 1 = (SELECT COUNT(DISTINCT salary) FROM employees e2 WHERE e2.salary > e1.salary). Or: SELECT MIN(salary) FROM (SELECT salary FROM employees ORDER BY salary DESC LIMIT 2) t. Or DENSE_RANK: WITH r AS (SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) rn FROM employees) SELECT salary FROM r WHERE rn=2. Why it matters: Design choices compound at scale—wrong approach can cause 100× overhead. Scalability trade-offs: Profile before optimizing; validate on sample then full. Cost implications: Suboptimal choices multiply at billion-row scale.
Red Flag: Generic textbook answers. Pro-Move: 'At scale we measured X, implemented Y, achieved Z%—validated and iterated.'
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.