1. Lighthouse

Level 9 · Who is paid closest to their manager?

The request

From Priya Shah, Head of Data

“HR is reviewing pay bands. They want the ten people whose salary is closest to their own manager's, with both names, so they can check those bands first.”

Your goal

Merge employees with itself so each employee who has a manager sits next to that manager. Set result to a DataFrame with columns employee_id, employee (first_name + ' ' + last_name), title, manager (the manager's first_name + ' ' + last_name) and salary_gap (manager's salary minus the employee's salary) for the 10 smallest gaps, sorted by salary_gap ascending then employee_id ascending, index reset.

  • Use the employees DataFramenot done yet
  • Show exactly employee_id employee title manager salary_gapnot done yet
  • 10 rows, sorted as askednot done yet

Your code

Python

Loading the editor…

    ResultPreview of employees · press Run to see yours
    Preview of employees
    employee_idfirst_namelast_namedepartmenttitle
    1CatherineHaleExecutiveChief Executive Officer
    2RobertKimExecutiveChief Operating Officer
    3MeganCollinsSalesHead of Sales
    4ChloeGutierrezSalesAccount Executive

    Mote checks your result

    Press Run. Each row that matches the goal becomes a firefly in your lantern.

    DataFrames

    Loaded for you as pandas DataFrames, plus pd and np.

    employees60 rows · 8 columns
    • employee_idinteger
    • first_namevarchar
    • last_namevarchar
    • departmentvarchar
    • titlevarchar
    • manager_idinteger
    • hire_datedate
    • salaryinteger
    First 5 rows of employees
    employee_idfirst_namelast_namedepartmenttitlemanager_idhire_datesalary
    1CatherineHaleExecutiveChief Executive OfficerNaN2016-03-01285000
    2RobertKimExecutiveChief Operating Officer12017-01-09235000
    3MeganCollinsSalesHead of Sales12018-04-16172000
    4ChloeGutierrezSalesAccount Executive32020-01-2172000
    5FrankBellSalesAccount Executive32023-05-2173000
    customers2,018 rows · 9 columns
    • customer_idinteger
    • first_namevarchar
    • last_namevarchar
    • emailvarchar
    • cityvarchar
    • statevarchar
    • signup_datedate
    • segmentvarchar
    • referral_sourcevarchar
    First 5 rows of customers
    customer_idfirst_namelast_nameemailcitystatesignup_datesegmentreferral_source
    1OwenHudsonowen.hudson@icloud.comSan FranciscoCA2022-06-02consumersearch
    2DouglasMendozadmendoza69@gmail.comAtlantaGA2022-06-02consumerNaN
    3HenryBrookshbrooks@lakesidecafe.comLos AngelesCA2022-06-04businessNaN
    4BrianGrahambgraham@bluecedarhomes.comSeattleWA2022-06-06businesspinterest
    5KyleJimenezkjimenez27@yahoo.comIndianapolisIN2022-06-07consumerNaN
    products120 rows · 8 columns
    • product_idinteger
    • namevarchar
    • categoryvarchar
    • subcategoryvarchar
    • unit_pricedecimal
    • unit_costdecimal
    • launched_ondate
    • is_activeboolean
    First 5 rows of products
    product_idnamecategorysubcategoryunit_priceunit_costlaunched_onis_active
    101Vale Velvet LoveseatFurnitureSofas1659.00NaN2023-09-11true
    102Alder Oak Coffee TableFurnitureTables919.00503.502024-05-16true
    103Orchard Rattan Dining ChairFurnitureChairs789.00429.872023-05-27true
    104Upland Oak BookcaseFurnitureStorage429.00214.702022-12-20true
    105Avery Leather Bed FrameFurnitureBeds449.00232.702021-08-31true
    orders12,000 rows · 7 columns
    • order_idinteger
    • customer_idinteger
    • order_datetimestamp
    • statusvarchar
    • channelvarchar
    • shipping_feedecimal
    • coupon_codevarchar
    First 5 rows of orders
    order_idcustomer_idorder_datestatuschannelshipping_feecoupon_code
    10011252023-01-01 20:51:19completedweb0.00NaN
    10021562023-01-02 07:58:46completedweb0.00NaN
    1003222023-01-02 10:25:27completedmarketplace4.99WELCOME10
    1004482023-01-02 11:21:51completedmarketplace4.99WELCOME10
    1005822023-01-02 11:43:36completedweb0.00WELCOME10
    order_items30,338 rows · 6 columns
    • order_item_idinteger
    • order_idinteger
    • product_idinteger
    • quantityinteger
    • unit_pricedecimal
    • discount_pctdecimal
    First 5 rows of order_items
    order_item_idorder_idproduct_idquantityunit_pricediscount_pct
    11001121931.990.00
    21001154311.990.00
    31002154411.990.00
    410021941149.000.00
    51002193219.990.00
    returns1,673 rows · 5 columns
    • return_idinteger
    • order_item_idinteger
    • returned_ondate
    • reasonvarchar
    • refund_amountdecimal
    First 5 rows of returns
    return_idorder_item_idreturned_onreasonrefund_amount
    1142023-01-10damaged83.69
    2422023-01-10wrong_item19.99
    31052023-01-14wrong_item10.99
    4242023-01-16changed_mind26.99
    51262023-01-16late20.99
    web_sessions40,000 rows · 7 columns
    • session_idinteger
    • customer_idinteger
    • started_attimestamp
    • devicevarchar
    • sourcevarchar
    • pages_viewedinteger
    • convertedboolean
    First 5 rows of web_sessions
    session_idcustomer_idstarted_atdevicesourcepages_viewedconverted
    1NaN2023-01-01 23:02:24mobilepaid1false
    2182023-01-01 15:07:49desktoppaid1false
    3NaN2023-01-01 16:55:46desktopdirect7false
    4NaN2023-01-01 12:43:28mobileorganic3false
    5NaN2023-01-01 13:06:21mobilesocial2false
    marketing_spend3,276 rows · 3 columns
    • spend_datedate
    • channelvarchar
    • amountdecimal
    First 5 rows of marketing_spend
    spend_datechannelamount
    2023-01-01paid492.99
    2023-01-01email37.38
    2023-01-01social200.53
    2023-01-02paid709.13
    2023-01-02email64.13

    The lesson

    One table, two roles

    employees stores the reporting line inside itself: manager_id holds the employee_id of the person’s manager. To see both people on one row, merge the table with itself. The left side plays the employee, the right side plays the manager:

    bosses = employees[["employee_id", "first_name", "last_name", "salary"]]
    pairs = employees.merge(bosses, left_on="manager_id", right_on="employee_id", suffixes=("", "_mgr"))

    left_on and right_on are for keys with different names on each side. Because both sides have first_name, last_name, salary and employee_id, pandas needs suffixes to tell them apart. ("", "_mgr") leaves the employee’s columns unchanged and adds _mgr to the manager’s, which reads far better than the default _x and _y. Selecting only four manager columns first keeps the merged table narrow.

    A float key meets an int key

    manager_id is a float column (1.0, 3.0, …) while employee_id is an int. That’s because the CEO has no manager, and plain pandas can’t store a missing value in an int column, so the whole column became float with NaN for her. The merge still works: 3.0 matches 3. The CEO’s NaN matches nothing, so the inner merge drops her and 59 pairs remain. Use how="left" instead if you need everyone, managers or not, with NaN in the manager columns.

    Building the answer

    Text columns join with +, and numbers subtract column by column:

    pairs["employee"] = pairs["first_name"] + " " + pairs["last_name"]
    pairs["salary_gap"] = pairs["salary_mgr"] - pairs["salary"]
    pairs.sort_values(["salary_gap", "employee_id"]).head(3)[["employee", "salary_gap"]]

    The three closest are support specialists Helen Parker ($22,000 below her lead) and Eric Jimenez ($23,000), then Donna Vasquez, a Senior Software Engineer $25,000 below the Head of Engineering. Nobody earns more than their manager, which is a useful check in itself: a negative gap would be the first thing HR asks about.

    Common mistakes

    • Merging on="employee_id", which pairs each person with themselves.
    • Keeping the default suffixes and then subtracting salary_x from salary_y the wrong way round.
    • Expecting the CEO in the result: an inner merge drops rows whose key is NaN.
    • Converting manager_id with astype(int) first, which fails on the NaN.

    Pick what may run on this site. You can change this any time from "Cookie settings" at the bottom of every page.