Practise headcount and workforce planning vocabulary: FTE, open reqs, backfill vs. growth hires, attrition, and writing a headcount business case.
0 / 18 completed
1 / 18
What does "FTE" mean, and how does it differ from a contractor headcount?
FTE (Full-Time Equivalent) is the standard unit for counting permanent full-time headcount; two part-time employees at 0.5 FTE each count as 1 FTE combined.
Key distinction: FTE vs. contractor — contractors are typically budgeted separately (often from a different cost center, e.g. "contingent labor" or "opex" rather than "headcount"), don't count against FTE headcount caps, and are used for flexible or time-boxed work. During a headcount freeze (a hiring pause on new FTEs), some companies still allow contractor hiring since it doesn't touch the frozen FTE budget.
Vocabulary: "We have budget for 2 FTEs and 1 contractor this quarter."
2 / 18
What is the difference between a "backfill req" and a "growth req"?
Req (short for requisition) is the formal, approved authorization to hire for a specific role.
• Backfill req: opened because a previous employee left the role — the team size stays the same once filled • Growth req: a genuinely new headcount slot — the team size increases once filled
This distinction matters in budget conversations: backfill reqs are usually approved faster (replacing existing budget) while growth reqs require new budget approval, often needing a stronger business case.
Example: "We have 3 open reqs: 2 backfills for engineers who left in Q4 and 1 growth hire to support the new platform initiative."
3 / 18
Which pair correctly distinguishes "regrettable" from "non-regrettable" attrition?
Regrettable attrition — losing someone the company wanted to keep (a strong performer, hard-to-replace skill set). This is the metric leadership tracks most closely, since it signals retention problems.
Non-regrettable attrition — departure of an underperformer, or a departure that aligns with restructuring plans; generally not concerning from a retention standpoint.
Related terms: • voluntary attrition — employee chose to leave (resignation) • involuntary attrition — company ended the employment (layoff, termination)
Note: these two axes are independent — a voluntary resignation can be regrettable (losing a strong performer) or non-regrettable, and the same applies to involuntary departures.
4 / 18
Rewrite this headcount request to follow standard business-case structure (problem → impact → ask):
"I want more people on my team, we're busy."
Option B follows the standard headcount business-case structure: 1. The specific ask: "2 additional FTEs" 2. The concrete problem: quantified gaps (on-call rotation size, backlog growth %) 3. The consequence of inaction: burnout risk, roadmap slippage
Vague requests ("we're busy", "everyone is tired", comparisons to other teams' headcount) rarely succeed in budget conversations because they give approvers nothing concrete to evaluate. Strong headcount requests quantify the gap and tie it to business risk or roadmap commitments — this is what finance and leadership need to approve new budget.
5 / 18
What does "span of control" mean in workforce planning, and why does it matter?
Span of control — the number of people reporting directly to one manager. Also called manager-to-IC ratio.
Why it matters in workforce planning: • Too low a span (e.g. 2-3 reports) can mean too many management layers relative to the org's size — expensive and slows decision-making • Too high a span (e.g. 15+ reports) means managers can't give each person meaningful coaching, 1:1 time, or career development attention • A commonly cited healthy range for engineering managers is 6–8 direct reports, though this varies by team maturity and manager experience
Related term: team density — how concentrated headcount is within a specific function/product area, used when deciding whether to add a new team vs. grow an existing one.
6 / 18
Reviewer: 'The PR needs a headcount review before merging. We're seeing consistently high ticket resolution times for this module and it's impacting our sprint velocity. Let's get a senior engineer to assess the workload and determine if we need to bring in additional support.'
Which of the following best describes the reviewer's primary concern regarding this PR?
The reviewer's statement focuses on 'consistently high ticket resolution times and impacting sprint velocity,' directly pointing to a problem with insufficient headcount. While scaling or resource allocation could be contributing factors, the core issue is that the team doesn't have enough people to handle the workload. This highlights a critical bottleneck, not just an overall lack of resources; it's about the *balance* between demand and capacity. Choosing 'scaling' implies a general overgrowth which isn't necessarily reflected in the details provided.
7 / 18
Reviewer: 'The PR needs a headcount review before merging. We're seeing consistently high ticket resolution times for this module and it's impacting our sprint velocity. Let's get a senior engineer to assess the workload and determine if we need to bring in additional support.'
Which of the following best describes the reviewer's primary concern regarding this PR?
The reviewer's statement focuses on 'consistently high ticket resolution times and impacting sprint velocity,' directly pointing to a problem with insufficient headcount. While scaling or resource allocation could be contributing factors, the core issue is that the team doesn't have enough people to handle the workload. This highlights a critical bottleneck, not just an overall lack of resources; it's about the *balance* between demand and capacity. Choosing 'scaling' implies a general overgrowth which isn't necessarily reflected in the details provided.
8 / 18
Reviewer: 'The PR needs a headcount review before merging. We're seeing consistently high ticket resolution times for this module and it's impacting our sprint velocity. Let's get a senior engineer to assess the workload and determine if we need to bring in additional support.'
Which of the following best describes the reviewer's primary concern regarding this PR?
The reviewer's statement focuses on 'consistently high ticket resolution times and impacting sprint velocity,' directly pointing to a problem with insufficient headcount. While scaling or resource allocation could be contributing factors, the core issue is that the team doesn't have enough people to handle the workload. This highlights a critical bottleneck, not just an overall lack of resources; it's about the *balance* between demand and capacity. Choosing 'scaling' implies a general overgrowth which isn't necessarily reflected in the details provided.
9 / 18
Reviewer: 'The PR needs a headcount review before merging. We're seeing consistently high ticket resolution times for this module and it's impacting our sprint velocity. Let's get a senior engineer to assess the workload and determine if we need to bring in additional support.'
Which of the following best describes the reviewer's primary concern regarding this PR?
The reviewer's statement focuses on 'consistently high ticket resolution times and impacting sprint velocity,' directly pointing to a problem with insufficient headcount. While scaling or resource allocation could be contributing factors, the core issue is that the team doesn't have enough people to handle the workload. This highlights a critical bottleneck, not just an overall lack of resources; it's about the *balance* between demand and capacity. Choosing 'scaling' implies a general overgrowth which isn't necessarily reflected in the details provided.
10 / 18
Alex: "Hey team, I've noticed our Jira ticket backlog for the Phoenix module is consistently exceeding 50 open issues. This is directly impacting sprint velocity and we're starting to fall behind on our commitments. We need a headcount review to address this."
This scenario demonstrates a common situation in product development. Alex's message effectively frames the issue (high ticket backlog) and its impact (reduced velocity). While stating the need for headcount is implied, directly articulating it as 'we need more people' strengthens the argument. Options A and C are too weak; option D misses the core of his request.
The API response highlights a critical metric (ticket resolution time) for the Phoenix module. The 'warning' status and value exceeding the defined threshold (60 minutes) immediately indicate a potential bottleneck needing attention. Options A and B are incorrect as they misinterpret the data's meaning; option D is irrelevant given the context.
12 / 18
Slack Message: '@john.doe Can you run a headcount analysis for the Core Services team? We've been onboarding three new engineers this month and our current workload is significantly higher than anticipated.'
This Slack message effectively explains the reason for requesting a headcount analysis. The key factor is the recent onboarding of three new engineers – this directly contributes to an increased workload. Options A and C misinterpret the tone; option D highlights a potential weakness in planning but doesn't fully explain the justification for additional resources.
13 / 18
During a standup meeting, Sarah says: 'I'm currently juggling three high-priority bug fixes and working on the new feature for Project X. I'm feeling really stretched thin and could use some support.' What is Sarah primarily communicating?
Sarah's statement directly addresses her current workload (multiple bug fixes + feature work) and expresses feeling 'stretched thin.' This indicates a need for support or potentially additional resources to manage the demands. Options A and C are irrelevant; option D misinterprets her request – she's not asking for *another* project, but help with *existing* ones.
14 / 18
Mark: '@team-dev I need a headcount review for the Data Pipelines project. We've just launched the new reporting dashboard and support requests are up 30% this week. The current team is consistently working overtime to maintain stability. What does Mark likely want to discuss?
Mark's message directly points to an imbalance between demand (increased support requests) and supply (team capacity). The phrase 'consistently working overtime' signals a critical need for headcount review – specifically to determine if the team can sustainably manage the increased workload. Options A, C, and D are potential outcomes of such a review, not the initial driver of the request.
15 / 18
API Response: {
"metric": "developer_burnout",
"module": "Frontend",
"value": 85,
"unit": "%",
"threshold": 70,
"status": "critical"
} What does this API response indicate?
The 'critical' status and value of 85% clearly signal a problem. This API is monitoring developer burnout – a key factor in productivity and retention. A value above the threshold indicates that the team is at risk of becoming overloaded and potentially impacting quality or velocity.
16 / 18
PR Description: 'Merging this PR will significantly improve user onboarding flow. However, we need to ensure the team has sufficient capacity to handle the increased load from new users. Let's schedule a headcount review to confirm our resource allocation.' What is the primary purpose of this PR description?
The description explicitly mentions 'sufficient capacity' and 'resource allocation,' directly indicating a need to evaluate headcount. This is a preventative measure – recognizing potential strain *before* it impacts delivery. Options A, C, and D are tangential to the core concern raised in the PR.
17 / 18
During a standup meeting, David says: 'I'm currently working on refactoring the legacy payment system and debugging intermittent errors. I'm feeling pretty overloaded with this work and haven't had time to address the new UI requests. I need help prioritizing.' What does David primarily express?
David's statement clearly highlights an imbalance between his assigned work (legacy system refactoring and debugging) and newly added requests (UI). The phrase 'feeling pretty overloaded' directly indicates a need for help prioritizing – suggesting he's unable to meet deadlines or deliver effectively due to excessive workload. Options A, C, and D are less central to the immediate issue.
18 / 18
Reviewer: 'The team's headcount for the 'Project Chimera' initiative is currently at 3. We've been assigned a critical bug fix with a high severity impact on user experience and are also supporting the rollout of the new mobile app. Based on this, what key metric should be immediately investigated to inform a headcount decision?"
This scenario highlights a situation where multiple high-priority tasks are simultaneously impacting the team. The key here isn't just about meeting sprint goals (option A), but whether the current workload is *sustainable*. Option C directly addresses this overload, while option D misinterprets the rollout's impact—it's a critical feature launch.
What does the "Headcount Planning Language" exercise cover?
Learn headcount and workforce planning vocabulary in English: FTE, requisitions, backfill vs. growth reqs, attrition types, and span of control.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Headcount Planning Language"?
This exercise has 18 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Developer Hiring exercises?
Browse the full Developer Hiring hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.