Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Why Join + Same-Location Filter:** Business rule: employee must be in dept AND colocated. The join condition e.city = d.city enforces referential locality—critical for org hierarchy and location-based access control. **Query Design:** JOIN on dept_id plus e.city = d.city....
This medium-level Python/Coding question appears frequently in data engineering interviews at companies like Freight Tiger. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join) 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.
Why Join + Same-Location Filter: Business rule: employee must be in dept AND colocated. The join condition e.city = d.city enforces referential locality—critical for org hierarchy and location-based access control.
Query Design: JOIN on dept_id plus e.city = d.city. Alternative: JOIN on (dept_id, city) as composite key if indexed—can be faster. Use INNER JOIN when you want only matching pairs; LEFT JOIN if you need depts with no local employees (would show NULL).
Scalability: Index (dept_id, city) on both tables. For large orgs (100K+ employees): consider materialized view for 'employees by location' refreshed nightly.
SELECT d.dept_name, e.employee_name, e.city
FROM employees e
JOIN departments d ON e.dept_id = d.dept_id AND e.city = d.city;
Red Flag: Joining only on dept_id and forgetting city match. Pro-Move: 'We denormalize (dept_id, dept_city) into employee dimension for fast point lookups—join is now a simple filter.'
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 Python/Coding interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.