The request

From Laura Bennett, Head of Finance
Your goal
Step 1 of 3. Check the table. Join employees (alias e) to itself (alias m) with a LEFT JOIN on m.employee_id = e.manager_id and return one row: employees (rows), distinct_ids, distinct_names (distinct first_name || ' ' || last_name), no_manager (e.manager_id is NULL), unknown_manager (e.manager_id is not NULL but no manager row was found), min_salary and max_salary.
- Read from the
employeestablenot done yet - Show exactly
employeesdistinct_idsdistinct_namesno_managerunknown_managermin_salarymax_salarynot done yet - 1 row, sorted as askednot done yet
Step 2 of 3. Summarise by department. Return department, headcount, payroll (total salary), mean_salary (rounded to 0), median_salary and hired_since_2024 (hire_date on or after 2024-01-01). Sort by payroll descending, then department.
- Read from the
employeestablenot done yet - Show exactly
departmentheadcountpayrollmean_salarymedian_salaryhired_since_2024not done yet - 9 rows, sorted as askednot done yet
Step 3 of 3. Count direct reports. Join employees (e) to itself (m) on m.employee_id = e.manager_id with an inner join, and return manager (m.first_name || ' ' || m.last_name), title (the manager's title) and direct_reports (how many employees report to them). Sort by direct_reports descending, then manager.
- Read from the
employeestablenot done yet - Show exactly
managertitledirect_reportsnot done yet - 12 rows, sorted as askednot done yet
This case unlocks when you finish any one of:
The ticket and lesson are open to read now. Solve every level in one of those chapters, in whichever track you prefer, and this case opens.
Step 1 · your query
Loading the editor…
Reference solution
| employee_id | first_name | last_name | department | title |
|---|---|---|---|---|
| 1 | Catherine | Hale | Executive | Chief Executive Officer |
| 2 | Robert | Kim | Executive | Chief Operating Officer |
| 3 | Megan | Collins | Sales | Head of Sales |
| 4 | Chloe | Gutierrez | Sales | Account Executive |
Mote checks your result
Press Run. Each row that matches the goal becomes a firefly in your lantern.
Step 2 · your query
Loading the editor…
Reference solution
| employee_id | first_name | last_name | department | title |
|---|---|---|---|---|
| 1 | Catherine | Hale | Executive | Chief Executive Officer |
| 2 | Robert | Kim | Executive | Chief Operating Officer |
| 3 | Megan | Collins | Sales | Head of Sales |
| 4 | Chloe | Gutierrez | Sales | Account Executive |
Mote checks your result
Press Run. Each row that matches the goal becomes a firefly in your lantern.
Step 3 · your query
Loading the editor…
Reference solution
| employee_id | first_name | last_name | department | title |
|---|---|---|---|---|
| 1 | Catherine | Hale | Executive | Chief Executive Officer |
| 2 | Robert | Kim | Executive | Chief Operating Officer |
| 3 | Megan | Collins | Sales | Head of Sales |
| 4 | Chloe | Gutierrez | Sales | Account Executive |
Mote checks your result
Press Run. Each row that matches the goal becomes a firefly in your lantern.
What Laura gets, and why
Tables
Harbor & Pine store data, ready to query.
employees60 rows · 8 columns
employee_idintegerfirst_namevarcharlast_namevarchardepartmentvarchartitlevarcharmanager_idintegerhire_datedatesalaryinteger
| employee_id | first_name | last_name | department | title | manager_id | hire_date | salary |
|---|---|---|---|---|---|---|---|
| 1 | Catherine | Hale | Executive | Chief Executive Officer | NULL | 2016-03-01 | 285000 |
| 2 | Robert | Kim | Executive | Chief Operating Officer | 1 | 2017-01-09 | 235000 |
| 3 | Megan | Collins | Sales | Head of Sales | 1 | 2018-04-16 | 172000 |
| 4 | Chloe | Gutierrez | Sales | Account Executive | 3 | 2020-01-21 | 72000 |
| 5 | Frank | Bell | Sales | Account Executive | 3 | 2023-05-21 | 73000 |
customers2,018 rows · 9 columns
customer_idintegerfirst_namevarcharlast_namevarcharemailvarcharcityvarcharstatevarcharsignup_datedatesegmentvarcharreferral_sourcevarchar
| customer_id | first_name | last_name | city | state | signup_date | segment | referral_source | |
|---|---|---|---|---|---|---|---|---|
| 1 | Owen | Hudson | owen.hudson@icloud.com | San Francisco | CA | 2022-06-02 | consumer | search |
| 2 | Douglas | Mendoza | dmendoza69@gmail.com | Atlanta | GA | 2022-06-02 | consumer | NULL |
| 3 | Henry | Brooks | hbrooks@lakesidecafe.com | Los Angeles | CA | 2022-06-04 | business | NULL |
| 4 | Brian | Graham | bgraham@bluecedarhomes.com | Seattle | WA | 2022-06-06 | business | |
| 5 | Kyle | Jimenez | kjimenez27@yahoo.com | Indianapolis | IN | 2022-06-07 | consumer | NULL |
products120 rows · 8 columns
product_idintegernamevarcharcategoryvarcharsubcategoryvarcharunit_pricedecimalunit_costdecimallaunched_ondateis_activeboolean
| product_id | name | category | subcategory | unit_price | unit_cost | launched_on | is_active |
|---|---|---|---|---|---|---|---|
| 101 | Vale Velvet Loveseat | Furniture | Sofas | 1659.00 | NULL | 2023-09-11 | true |
| 102 | Alder Oak Coffee Table | Furniture | Tables | 919.00 | 503.50 | 2024-05-16 | true |
| 103 | Orchard Rattan Dining Chair | Furniture | Chairs | 789.00 | 429.87 | 2023-05-27 | true |
| 104 | Upland Oak Bookcase | Furniture | Storage | 429.00 | 214.70 | 2022-12-20 | true |
| 105 | Avery Leather Bed Frame | Furniture | Beds | 449.00 | 232.70 | 2021-08-31 | true |
orders12,000 rows · 7 columns
order_idintegercustomer_idintegerorder_datetimestampstatusvarcharchannelvarcharshipping_feedecimalcoupon_codevarchar
| order_id | customer_id | order_date | status | channel | shipping_fee | coupon_code |
|---|---|---|---|---|---|---|
| 1001 | 125 | 2023-01-01 20:51:19 | completed | web | 0.00 | NULL |
| 1002 | 156 | 2023-01-02 07:58:46 | completed | web | 0.00 | NULL |
| 1003 | 22 | 2023-01-02 10:25:27 | completed | marketplace | 4.99 | WELCOME10 |
| 1004 | 48 | 2023-01-02 11:21:51 | completed | marketplace | 4.99 | WELCOME10 |
| 1005 | 82 | 2023-01-02 11:43:36 | completed | web | 0.00 | WELCOME10 |
order_items30,338 rows · 6 columns
order_item_idintegerorder_idintegerproduct_idintegerquantityintegerunit_pricedecimaldiscount_pctdecimal
| order_item_id | order_id | product_id | quantity | unit_price | discount_pct |
|---|---|---|---|---|---|
| 1 | 1001 | 121 | 9 | 31.99 | 0.00 |
| 2 | 1001 | 154 | 3 | 11.99 | 0.00 |
| 3 | 1002 | 154 | 4 | 11.99 | 0.00 |
| 4 | 1002 | 194 | 1 | 149.00 | 0.00 |
| 5 | 1002 | 193 | 2 | 19.99 | 0.00 |
returns1,673 rows · 5 columns
return_idintegerorder_item_idintegerreturned_ondatereasonvarcharrefund_amountdecimal
| return_id | order_item_id | returned_on | reason | refund_amount |
|---|---|---|---|---|
| 1 | 14 | 2023-01-10 | damaged | 83.69 |
| 2 | 42 | 2023-01-10 | wrong_item | 19.99 |
| 3 | 105 | 2023-01-14 | wrong_item | 10.99 |
| 4 | 24 | 2023-01-16 | changed_mind | 26.99 |
| 5 | 126 | 2023-01-16 | late | 20.99 |
web_sessions40,000 rows · 7 columns
session_idintegercustomer_idintegerstarted_attimestampdevicevarcharsourcevarcharpages_viewedintegerconvertedboolean
| session_id | customer_id | started_at | device | source | pages_viewed | converted |
|---|---|---|---|---|---|---|
| 1 | NULL | 2023-01-01 23:02:24 | mobile | paid | 1 | false |
| 2 | 18 | 2023-01-01 15:07:49 | desktop | paid | 1 | false |
| 3 | NULL | 2023-01-01 16:55:46 | desktop | direct | 7 | false |
| 4 | NULL | 2023-01-01 12:43:28 | mobile | organic | 3 | false |
| 5 | NULL | 2023-01-01 13:06:21 | mobile | social | 2 | false |
marketing_spend3,276 rows · 3 columns
spend_datedatechannelvarcharamountdecimal
| spend_date | channel | amount |
|---|---|---|
| 2023-01-01 | paid | 492.99 |
| 2023-01-01 | 37.38 | |
| 2023-01-01 | social | 200.53 |
| 2023-01-02 | paid | 709.13 |
| 2023-01-02 | 64.13 |
The lesson
What you are checking, and why
An HR export looks tidy, but it is often edited by hand: people are re-entered after a role change, managers leave and their reports keep pointing at them. Before you total anything, check three things.
- Is anyone listed twice? Ids are unique by design, so compare the row count with the count of distinct names as well.
- Does every reporting line lead somewhere? A
manager_idthat matches noemployee_idis an orphan. Only the CEO should have no manager at all. - Are the salaries plausible?
MINandMAXcatch a monthly figure typed as yearly, or a missing zero.
The reporting check needs a self-join: the table joined to itself under two aliases, one for
the employee and one for the manager. A LEFT JOIN keeps every employee even when no manager row
is found, and then that manager’s columns are NULL:
FROM employees AS e
LEFT JOIN employees AS m ON m.employee_id = e.manager_id
An employee with a manager_id but a NULL in m.employee_id is an orphan. Here there are none.
Headcount, payroll, mean and median
Step 2 is a plain GROUP BY department with several aggregates side by side. The interesting
pair is mean and median. The mean adds every salary and divides; the median is the middle salary
when they are sorted. In a department of seven where one person is the head, the head’s salary
moves the mean a lot and the median hardly at all:
| department | headcount | mean_salary | median_salary |
|---|---|---|---|
| Engineering | 8 | 149,750 | 139,500 |
| Data & Analytics | 7 | 108,000 | 92,000 |
| Sales | 9 | 84,000 | 73,000 |
| Customer Support | 9 | 59,333 | 50,000 |
For “what does a typical person here earn”, report the median. Payroll is still the sum: that is what the budget pays.
Span of control
Span of control is the number of people who report directly to a manager. It is a common
input to org design: too narrow and the company is top-heavy, too wide and managers cannot keep
up. With the inner self-join, every row is one reporting line, so counting rows per manager gives
the span. Group by the manager’s columns, from m.
The spans here run from 2 (Anna Chen, Sales Manager) to 7. Support’s two managers have 5 and 3.
Pitfalls
- An inner join in the check hides the very rows you are looking for; use
LEFT JOIN. GROUP BY m.first_name || ' ' || m.last_namewould merge two managers who share a name; grouping by id is safer in a big company.- Department means of 2 or 5 people can reveal individual salaries. Keep them out of reports that go beyond Finance and HR.
Lantern lit!
Practised: data validationself joinleft joingroup bymedianspan of control
- Solved
- No hints
- First run
