Count Direct Reports per Manager
Return each manager id with the number of employees reporting to them, largest team first.
The challenge runs on the SQLabHub practice database (SQLite) and uses the employees table. You can solve it in the browser, with nothing to install.
The task
Find managers with highest number of direct reports.
A correct answer returns 10 rows with 2 columns: manager_id, subordinates.
Tables used in this challenge
employees 120 rows
id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · department TEXT · department_id INTEGER · title TEXT · salary REAL · hire_date TEXT · manager_id INTEGER · city TEXT · status TEXT
| id | first_name | last_name | department | department_id | title | salary | hire_date | manager_id | city | status | |
|---|---|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| manager_id | subordinates |
|---|---|
The complete result: 10 rows. This is the output of the model solution on the practice database.
What you practise
- Filtering rows with a WHERE condition
- Testing for missing values with IS NULL and IS NOT NULL
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Grouping rows with GROUP BY to get one result row per group
- Sorting the result with ORDER BY
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Self join GROUP BY manager_id
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
employeestable. - Filter in
WHERE: keep the rows wheremanager_idhas a value (it is not NULL). - Group the rows by
manager_id, so the result has one row for each value. - For each group, compute
COUNT(*). - Sort the result by
subordinatesdescending.
Model solution
Checking your session…
What to watch for
No join is needed: grouping on manager_id counts the reports. A self join is only required to show the manager's name. The WHERE clause removes the people at the top, whose manager_id is NULL.
- GROUP BY. Every selected column must either be in GROUP BY or sit inside an aggregate. SQLite accepts other columns and returns an arbitrary value for them; most databases raise an error.
- IS NULL. Comparing with = NULL or <> NULL never matches any row. NULL has to be tested with IS NULL or IS NOT NULL.
- ORDER BY. Without ORDER BY the row order is not guaranteed, even if it looks stable. Rows that tie on the sort columns can come back in any order.
Related SQL challenges
- Rank Products by Their Average Review RatingSimilar levelHard
- Count Orders in Each Customer's First 7 DaysSimilar levelHard
- Salary Statistics per Department: Count, Avg, Min and MaxEasierMedium
- Find Shipped Orders with IS NOT NULLEasierEasy
- Find Unshipped Orders with IS NULLEasierEasy
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: GROUP BY
- Lesson: IS NULL
- Lesson: ORDER BY
- Lesson: Aggregate Functions
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database