The Engineering Roster

The VP of Engineering at Kestrel Labs is running a compensation review with her own team and wants the working list in front of her: her people and what each of them is paid, best paid at the top so the conversation starts at the expensive end.

The employee export will not tell you which of these people are hers, at least not directly. Each row carries a plain number in department_id, and the number-to-team lookup lives in a second table. Settle which number Engineering is first; the employee table is not useful until you have.

departments — one row per team. budget is that team's annual budget in dollars.

employees — one row per person. department_id is the team they sit on, given as the matching id in departments; salary is annual pay in dollars; hire_date is the day they started, written year-month-day; manager_id is the id of the person they report to, and is NULL for anyone who reports to nobody.

Both tables already exist in the database — there is nothing to create or load.

Task: Write a query returning two columns, name and salary, one row per employee on the Engineering team, highest salary first. No two Engineering salaries are equal, so that single instruction fixes the order completely.

Example output — shape only, on invented people and pay: