N031-E2 Tier 3 · Intermediate · easy hr · Helix Systems

Return the department ID and headcount for every large department

Part of Chained CTEs in SQL

The problem

Helix Systems' HR team wants to find large departments — those with 5 or more staff on record.

Write a query to return the department ID and headcount for every large department.

Assumptions:

  • The employees table has one row per employee with a department_id.
  • A department's headcount is the number of employees records linked to that department_id.
  • Only departments with 5 or more employees should appear.

Output:

  • One row per qualifying department, with columns department_id and headcount.
Schema · hr 4 tables
departments
id integer
name text
location text
budget numeric
salaries
id integer
employee_id integer
amount numeric
effective_date date
end_date? date
employees
id integer
name text
email text
department_id integer
manager_id? integer
hire_date date
title text
is_active boolean
job_history
id integer
employee_id integer
title text
department_id integer
start_date date
end_date? date

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
WITH
  dept_counts AS (
    SELECT
      department_id,
      COUNT(*) AS headcount
    FROM
      employees
    GROUP BY
      department_id
  ),
  large_depts AS (
    SELECT
      department_id,
      headcount
    FROM
      dept_counts
    WHERE
      headcount >= 5
  )
SELECT
  department_id,
  headcount
FROM
  large_depts

The shape

Two named layers in one WITH clause. The first counts employees per department, and the second reads that result and keeps only departments with 5 or more on the headcount. The threshold check runs against the already-counted rows, not against the raw employees table.

Clause by clause

The first CTE reduces the employee roster to one row per department with its headcount:

WITH dept_counts AS (
  SELECT department_id, COUNT(*) AS headcount
  FROM employees
  GROUP BY department_id
)

GROUP BY department_id produces one row per department, and COUNT(*) counts the rows inside each group. AS headcount names the aggregate so the next layer can refer to it.

The second CTE reads those counts and keeps the large ones:

large_depts AS (
  SELECT department_id, headcount
  FROM dept_counts
  WHERE headcount >= 5
)

FROM dept_counts reads the counted result as if it were a table. WHERE headcount >= 5 drops the smaller departments. The six survivors are departments 1, 2, 3, 4, 7, and 8, with headcounts ranging from 5 to 17.

  • SELECT department_id, headcount FROM large_depts returns the final layer unchanged. The work happens in the two CTEs; the main query just reads the last one.

You practiced layering two WITH stages — compute the per-department count in one named layer, then read from that layer in a second named layer that applies the threshold check.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.