5 exercises — people management scope, headcount/budget language, technical vs managerial requirements, cross-functional language, and success metrics in EM job descriptions.
0 / 5 completed
1 / 5
An EM JD states: 'You will manage a team of 6–8 engineers, conduct performance reviews, run 1:1s, and support career development.' What is the PRIMARY scope of this people management role?
People management scope: EM roles focus on the performance and growth of direct reports. '1:1s' are regular one-on-one meetings with each engineer. 'Performance reviews' are formal evaluations. This is distinct from technical IC (individual contributor) work or VP-level strategy.
2 / 5
An EM JD reads: 'You will manage a $1.2M annual engineering headcount budget and collaborate with Finance on quarterly forecasts.' What does 'headcount budget' mean?
Headcount budget = the total cost of the people on the team (salaries, benefits, contractors). This is separate from infrastructure or tooling budgets. Managing headcount means making decisions about team size, hiring timing, and contractor vs full-time trade-offs within the allocated cost.
3 / 5
An EM JD lists under Requirements: Required: 3+ years of engineering management experience, ability to read and review code, understanding of distributed systems. Preferred: Prior hands-on experience as a software engineer for 5+ years. A candidate has managed teams for 4 years but started as a project manager, not an engineer. Do they meet the requirements?
Technical vs managerial requirements: The 5+ years as an engineer is listed as 'preferred', not required. The candidate's 4 years of management exceeds the 3-year requirement. 'Ability to read and review code' and 'understanding of distributed systems' are requirements they may meet through their management background, which would need to be demonstrated in interview.
4 / 5
An EM JD states: 'You will work cross-functionally with Product, Design, Data Science, and Security to deliver quarterly roadmap objectives.' What does 'cross-functional' mean in this context?
'Cross-functional' language means working across different specialisms — not just within engineering. An EM in a cross-functional model is a stakeholder alongside PMs and designers, not their manager. This signals the company uses empowered product teams (like the Spotify model) rather than a pure engineering-silo structure.
5 / 5
An EM JD lists success metrics: 'Within 6 months: team velocity is stable, no critical production incidents due to process gaps. Within 12 months: team NPS > 8, two engineers promoted to senior level.' What type of success metric is 'team NPS > 8'?
Team NPS (Net Promoter Score) applied internally measures how likely team members are to recommend working in the team. It is an engagement and satisfaction signal, not a technical or financial metric. Seeing it as a 12-month EM goal signals the company values psychological safety and team health as measurable outcomes.