A recruiter reading a manager's CV wants one answer before anything else: how big was the job? "Managed a team" tells them almost nothing. Six people or sixty? Did you hire them, set their pay, own the budget, or simply run the stand-up? The good news is that scope fits into a few honest lines, and those lines carry more weight than most of the bullets underneath them.
Put scope in the first line under each role
The most common mistake is not inflation. It is burial. Managers write four bullets about delivery and then, somewhere near the bottom, mention that they "also led a team of 9". By then the reader has already decided what level you are.
Give every management role a scope line directly under the job title and dates, before any achievement bullets. Something like:
- Engineering Manager, Payments (2021 to 2024): led 6 engineers and 2 team leads, 14 people in total; owned hiring for the group and a tooling budget of around 120k a year.
That single line answers what a screener wants to know: span, depth, hiring authority, money. A bullet about cutting release time means something different once the reader knows it came from a group of fourteen.
Keep the scope line factual. If you want to show the arc of a promotion inside the same employer, a separate article on promotions at the same company covers that layout; here the point is simply that each role gets its own scope line.
Direct reports versus the wider organisation
"Team of 14" can mean two very different jobs. In one, fourteen people report to you and you write all fourteen reviews. In the other, you manage two leads who each manage six, and you are one level removed from most of the work. Both are real management. They are not the same management, and a hiring manager filling a senior role cares a lot about the difference.
The cleanest way to write it is to separate the two numbers:
- Direct reports: the people whose line manager you were. You approved their leave, ran their one-to-ones, wrote their reviews.
- Total organisation: everyone in the reporting tree under you, including the reports of your reports.
So "led 6 engineers; 2 team leads reporting in, 14 people in total" is precise and easy to verify. "Led a 14-person team" is vaguer and, if most of them report to your leads, slightly misleading.
If your team changed during the role, give the range or the end state with a word of context: "grew the team from 3 to 8" is stronger than either number alone, because it tells the reader you hired.
Dotted lines and matrix leadership, stated honestly
A lot of modern leadership happens without line authority. You may run a cross-functional squad where the designer reports to design, the data analyst reports to analytics, and you still set the priorities every week. That is valuable work, and it belongs on the CV. It just needs the right verbs.
Words that tell the truth about matrix work:
- Coordinated a squad of 7 across product, design and data
- Led, without line authority, a migration involving 4 teams
- Set priorities for 5 contractors through a vendor agreement
- Acted as dotted-line manager for 2 analysts embedded in the team
The phrase "without line authority" feels like a confession the first time you write it. It is not. Influencing people who do not report to you is a recognised skill. What damages a candidate is the opposite: listing matrix colleagues as reports, then struggling in the interview when asked about the last salary review you ran for them.
A practical test: if you could not have given this person a performance rating, they were not your direct report. Describe the relationship as it was.
Hiring and developing people as evidence
Headcount on its own is a weak claim. Anyone can inherit a team. Hiring and development show what you did with it, and they are the two areas most CVs treat in half a line.
Hiring
Write hiring as outcomes, not as a duty. "Responsible for recruitment" is a job description. These are evidence (figures illustrative):
- Hired 5 engineers in 9 months, including the first two data roles in the team
- Rebuilt the interview loop around a paired exercise; offer acceptance improved and the loop dropped from 6 stages to 4
- 4 of the 5 people I hired were still in the team two years later
Retention of your own hires is an underused line. It says your judgement held up after the offer, which is the part of hiring that matters most to the person reading.
Developing people
Promotions of your reports are the clearest evidence that you grow people. "Two of my reports promoted to senior during my time as manager" is specific and checkable. Coaching counts too, but name the result: a junior who took over on-call ownership, a struggling performer you supported back to a solid rating.
If you are writing for a specific role family, two related guides go further: one on the engineering manager or tech lead CV, and one on the player-coach CV for people who still carry hands-on work. And for putting numbers on achievements in general, the guide on quantifying achievements covers metrics well beyond team size.
Budget and headcount: ownership or influence
Money is the area in which managers are most tempted to round up. There is a real gap between owning a budget and influencing one, and senior hiring managers know where it sits.
You owned a budget if you set it or proposed it, were accountable for the variance, and could move money between lines without asking. You influenced a budget if you made the case for spending and someone else approved it. Both are worth writing down. They read differently:
- Owned an annual operating budget of around 400k, including contractors and tooling
- Built the business case for 3 additional hires, approved in the next planning cycle
- Managed a 60k training allowance for a team of 12
Headcount works the same way. "Approved headcount of 10" means you had the seats. "Secured 2 new roles" means you fought for them. Do not merge them into one vague "managed resources" line.
If you are unsure whether you owned something, ask what happened when it went over. If the explanation landed on your desk, you owned it.
Do not turn informal leadership into management
This is the line that gets people caught. Mentoring a new joiner, running a guild, leading a project with other people's work in it: all of these are leadership, and all belong on a CV. None of them are people management, and a CV that calls them "managed" invites an interview question you cannot answer well.
Write informal leadership as what it was:
- Mentored 3 new joiners through their first six months
- Led the accessibility working group across 4 product teams
- Stood in for my manager for 6 weeks, covering one-to-ones and sprint planning
That last example is strong precisely because it is precise. If you are applying for your first formal management role, the cover letter is where you make that case in story form, and a separate article in this series covers exactly that. And when you meet the team you would lead, they will test the same claims from the other side of the table; the article on meeting your future direct reports covers that conversation.
Before you send the CV, go through each management role and confirm the first line under the title answers four questions: how many direct reports, how many people in total, whether you hired, and what money you controlled or influenced. If any answer is missing, add it. If any answer would surprise your former manager, soften the verb until it would not.
If your LinkedIn profile already lists these roles, tools like Postulit can pull them into a CV draft so you are editing scope lines rather than retyping job history. Ten minutes on the scope line changes how every other bullet on the page is read.
State the span, separate direct reports from the wider tree, and use "coordinated" or "without line authority" wherever it applies. Honest scope reads as senior. Inflated scope reads as a risk.