The Scope Signal Reference, One Row per Resume Number That Sets Your Band

This reference is for anyone writing or rewriting a resume, profile, or portfolio where the level is in play: senior manager and up, staff and up, or any move between a small employer and a large one. It has one row for each scope number a recruiter or leveling committee reads as a level: direct reports, roll-up org, budget, quota, P&L, users, geography, reporting line, hiring volume, decision rights, and employer size. Each row gives the criterion the number maps to, how it misleads in both directions, and wording that survives a calibration call. Jump to the row you need and leave.

How do recruiters and leveling committees read scope numbers?

They read each scope number as evidence for one leveling criterion, then discount it for context: how big the employer was, how far you sat from the CEO, and whether you owned the thing or only influenced it. A number with no context tends to be read at the lowest level it plausibly supports.

A leveling committee is the group that decides which level an offer goes out at. A calibration call is the meeting where that group checks your evidence against the written definition of each level. Those definitions use a small, stable vocabulary. Most frameworks combine four factors, and Carta adds a fifth:

• Scope - breadth of responsibility. One framework calls it "the most defensible leveling criterion because it's observable."
• Complexity - the kind of problem you solve. It moves from defined, to framed, to ambiguous as level rises.
• Autonomy - how much you direct yourself. It grows from check-ins, to outcome review, to self-direction.
• Impact - the size of the business outcomes.
• Leadership - Carta's added factor. Carta folds autonomy and scope together as "level of independence, decision-making authority, and breadth of impact on individuals, teams, departments, or the entire organization."

The step between levels widens these axes. It does not just add headcount. One framework puts it plainly: pay follows "the scope, complexity, and impact of the work, not the number of direct reports." That sentence is why the usual advice to "add team size and budget" falls short.

Two readers, measuring different things

Your resume is read twice, by two different logics. Textkernel's documented matching engine has a Management Level category that runs from supervisory roles up to C-level. Its parser assigns a job level "based on the length of experience and job titles." The engine scores 8 categories and combines them with weights that each employer's integrator sets. The vendor does not publish fixed weights, and its own documentation names leaving the default weights in place as the most common integration mistake. So you cannot know how much weight a given employer puts on management level.

A third-party analysis gives an illustration, not a vendor figure. A managerial role might weight management level at 25% and skills at 35%. A technical individual-contributor role might put management level near zero.

The people who read it next look for scope, complexity, autonomy, and impact. That gap causes most of the misreads in this reference: a title can clear the machine and still fail the committee.

Which leveling criterion does each scope signal map to?

People signals map to leadership and scope. Money and reach signals map to scope, impact, and complexity. Context signals (employer size, reporting line, decision rights, level code) map to autonomy or change how much every other number counts. Use the three tables below as the index. The sections after them give the wording for each row.

People signals

Money and reach signals

Context signals

Each row gets exactly one criterion on purpose. If a figure seems to prove two things, choose the one the target level definition stresses most, and let a second figure carry the other.

People signals: direct reports, roll-up org, hiring volume, reporting line

On a senior resume, direct reports are the weakest level signal. What separates a director from a strong line manager is whether you managed managers and how large the org under you was.

Pave's benchmark covers 257,000+ managers and shows why:

Directors average about 6% fewer direct reports than managers. Pave also finds that "spans narrow at the Director level, then widen again at SVP." Refolk's index shows the same thing from the supply side.

Directors are 34.5% of the combined US pool. Together with Pave's spans, this means the move to director is about managing managers and answering for a bigger org. It is not about adding direct reports.

Direct reports

• Criterion: leadership.
• Proves: you are formally responsible for developing, evaluating, and supporting these people.
• Inflates when: cross-functional partners, contractors, or dotted lines are counted. A count of 12 individual contributors can also read as senior to a parser and junior to a committee.
• Deflates when: a director lists "4 reports" without saying all four were managers. That reads like a line manager.
• Wording: "Managed [n] engineering managers; org of [N] engineers." Put it in the scope line, not a bullet.

Roll-up org

• Criterion: scope.
• Proves: the total breadth you answer for, through your managers.
• Reference point: one worked example puts roughly 200 managers, 40 senior managers, 8 directors, and 2 VPs in a 1,000-person organization at an average span of 5. A director in that shape answers for well over a hundred people. This is an illustration, not a norm.
• Inflates when: peers' teams or matrixed partners are added in.
• Deflates when: it is left off and only the direct-report count remains.
• Wording: "Org of [N] across [teams], through [m] managers."

Hiring volume

• Criterion: leadership.
• Proves: you built or scaled the team rather than inheriting it.
• Limit: no published norm ties a hiring count to a level. Check locally: if the target posting says "build" or "scale the team," this row belongs high on the page.
• Inflates when: hires closed by other managers or by recruiting are claimed as yours.
• Wording: "Hired [n] of the [N]-person org, including [m] managers."

Reporting line

• Criterion: autonomy.
• Proves: how close you sat to final decisions.
• The practitioner test: "If a 'Director' reports to the CEO, it's probably a real Director. If a 'Director' reports to a VP who reports to a Senior VP who reports to the CEO, it's probably a mid-level manager with an inflated title."
• Wording: "Reported to the CEO" or "Reported to the VP Engineering," on the line under the title.

Money and reach signals: budget, quota, P&L, users, geography

Money and reach figures place you only when the verb matches who held the authority. "Owned" and "influenced" are separate rows, and an interview or reference call can tell them apart.

Budget owned

• Criterion: scope.
• Proves: the breadth of resources you could commit without escalating.
• Inflates when: the department's total budget is listed under your name.
• Wording: "Owned $[X] annual [opex/capex] budget; approved [vendor/headcount] spend."

Budget influenced

• Criterion: impact.
• Proves: your judgment moved resources, even without signature authority.
• Deflates when: it is hidden because it was "not really yours." Influence over a large spend is real senior evidence.
• Wording: "Shaped $[X] [program] spend; recommendation adopted, cutting [cost] by [Y]."

Quota

• Criterion: impact.
• Proves: the revenue you carried personally, or through a team you led.
• Inflates when: a team or regional quota is written as a personal one.
• Wording: "Carried $[X] quota; [Y]% attainment" for individual quota. "Led [n] reps carrying $[X] combined quota" for team quota.

P&L

• Criterion: scope.
• Proves: you answered for both revenue and cost, which is the clearest executive-scope figure.
• Inflates when: a cost center is called a P&L.
• Wording: "Full P&L for [unit], $[X] revenue." Advice for executive roles is to put P&L size, team size, and geography in a one-line scope statement above the bullets.

Users or transactions

• Criterion: impact.
• Proves: the scale your work ran at.
• Inflates when: company-wide user counts are claimed for one feature or service.
• Wording: "Platform serving [N] monthly users; my team owned [component]."

Geographic reach

• Criterion: complexity.
• Proves: you handled breadth across markets, regulators, or time zones.
• Inflates when: countries the product sold into are listed as countries you ran.
• Wording: "Ran teams in [n] countries" is a different claim from "launched in [n] markets." Use the one that is true.

On order, sources disagree. StoryCV says to lead with team size for manager roles and with budget for finance roles. Another source says to add scope only where it is true and useful for the target role. I side with the second as the filter and the first as the tiebreaker.

The limit to state plainly: no published norm ties a specific budget, quota, or user figure to a level. What counts as big depends on the employer. Check locally: read the target posting and any public level definition, and lead with the money figure they name.

Context signals: employer size, reporting depth, decision rights, level code

Context figures do not earn a level by themselves. They decide how much every other number on the page counts. The same title and team size mean different things at a 25-person company and a 10,000-person one.

Pave reports that "a manager's average span of control at a company with 1,000 or more employees" runs "nearly double that of a manager at a company with 1 to 25 employees." It also notes that "as companies get larger, the proportional share of directors-and-above decreases." Put together, a startup director with 4 reports reads like a large-company line manager unless headcount sits next to the number.

Employer size

• Criterion: context. It changes how every other row reads.
• How it misleads upward: a startup title read at face value. One anecdotal report: "if you're a VP at a 100 person company you might only come in as a junior director at FAANG or even just an EM at first." Treat it as one person's report, not a rule.
• How it misleads downward: a large-company title read without the org behind it.
• Wording: "[Company], [headcount] employees, [stage]" on the role header.

Titles also inflate in the other direction at hiring time. A recruiter quoted by Ravio says: "You might have someone levelled as a senior manager based on experience but offered a Director role by a new employer just to secure the hire." So a Director title on your last role is not proof of director scope to the next committee.

Refolk's index shows how wide the range is behind one title. The US Director of Engineering sample of 25 profiles runs from Palo Alto Networks, Workday, and Figma to small firms such as Splice, Fluency, and Confirm.

Why the UK pool clusters this way is unverified. It is consistent with a smaller director pool concentrated in fintech, which would mean UK committees calibrate against a narrower set of reference employers. Check locally: look at where directors at your target employer worked before, and match your context line to that market.

Decision rights

• Criterion: autonomy.
• Proves: what you could approve alone, without escalating.
• Inflates when: "led" stands in for "recommended."
• Wording: "Final approval on [hiring/vendor/roadmap] decisions up to $[X]."

Internal level code

• Criterion: context.
• Proves: where a large employer itself placed you.
• Deflates when: it is missing and the title under-reads. A "Senior PM" title can read below Director even when the scope matches.
• Wording: "Senior PM ([level code]), org of [N]," on the title line.

What does being read one level low cost?

At the midpoint, it costs roughly one midpoint step, which band benchmarks most commonly put at 10 to 14%. In practice it is often less, because adjacent bands overlap and you can land high in the lower one. A midpoint step is the gap between the middle of one level's pay band and the middle of the next.

Published overlap figures disagree, and one source runs as high as 30 to 50%. Overlap above 50% "means your grade boundaries have collapsed," so a band structure that loose tells you less about level than about negotiation. At senior grades the step is larger. A dated source puts executive midpoint progression at 20 to 35%, so check the employer's own structure rather than relying on it.

Two consequences follow for the resume:

1. A down-level is bounded. A one-level drop is roughly one midpoint step, and where you land inside the band can win much of it back. That supports qualifying an inflated title over defending it.
2. A down-level is not automatically a pay cut. Because bands overlap, a strong lower-level offer can beat a weak higher-level one. Compare each offer against the midpoint of its own band.

How to put scope numbers on the page

Inventory every figure, map each to one criterion, put employer context next to the title, and write a one-line scope statement above the bullets. Then pair every number with an outcome and cut any precision you cannot defend. Plan on about four hours for a full history.

The inventory is the slow part, because the figures are scattered across old reviews, planning docs, and memory. Refolk writes the resume from your own history, so the owned-or-influenced inventory starts from records instead of a blank page. You still make the judgment calls in steps 2 and 4.

The finished role entry has four layers, read from the outside in:

[Title] ([level code, if it under-reads]) | [Company], [headcount] employees, [stage]
Reported to [CEO / VP title]; [n] layers below the CEO.
Scope: [n] direct reports ([m] managers); org of [N] across [teams]. Owned $[X] budget; influenced $[Y] [program] spend. [Geography]. Final approval on [decision type].
- [Action] across [scale figure], which [outcome with number].
- Hired [n] of the [N]-person org, including [m] managers; [retention or delivery outcome].

Which scope figure leads should change with the posting: org size for a "scale the team" role, budget owned for a cost-control role. Refolk tailors the resume to each posting you apply to, so you do not hand-edit the order of the scope line for every application.

How scope signals misread you

Most misreads come from a number shown without the context that tells a reader which level it supports. Each one below shows how it happens, what the false read looks like, and how to check for it.

1. Direct reports read as level. Directors average fewer reports than managers (4.6 against 4.9), so a large count does not prove seniority. False positive: 12 individual contributors read as director scope by a parser. Check: say whether you managed managers.
2. Title read without the reporting line. A "Director" three layers below the CEO reads as a mid-level manager. False positive: a startup VP with a team of 3 read as an executive. Check: put headcount and reporting line next to the title.
3. Budget influenced written as owned. A reference call or interview probing your decision rights exposes it, and then the committee discounts every other figure. Check: use "owned" or "influenced" to match who approved the spend.
4. Parser mismatch. The parser infers level from titles and years. Textkernel's parser, for example, has a Senior Manager level defined as "more than 5 years management experience." An inflated title ranks you high by machine, then people down-level you. Check: make the title and the scope line say the same level.
5. Partners counted as team size. Span counts only people you are formally responsible for developing, evaluating, and supporting. Check: list direct reports and cross-functional partners separately.
6. Under-titling at a big employer. A "Senior PM" title reads below Director even when the scope matches. Check: add the internal level code and the size of the org.
7. Treating a down-level as a pay cut. Overlapping bands can mean higher pay at a lower level. Check: compare the offer against the midpoint of the band it sits in.

The evidence on testing is thin, and I will not overstate it. No public case shows a team-size or budget figure being checked on its own. Employment checks do cover "job titles, employment dates, responsibilities, and accomplishments," and dates and degrees are described as the easiest to verify. In Monster's survey of 1,002 US job seekers, 13% admitted lying recently, and 56% believed employers only "sometimes" verify resume details. "Sometimes" is the wrong bet when the figure is what places you in your band. The real test is the interview: every number on the page invites a follow-up question.

Keeping the scope line current

Rebuild the scope line whenever your role changes, your target level changes, or a posting asks for a different kind of scope. The figures stay the same. What changes is which one leads and which ones need a qualifier.

The benchmarks behind this reference move too. Pave's manager span went from 4.4 to 4.9 between readings. Before you use a span norm in a negotiation or a cover letter, re-read the current benchmark rather than quoting a remembered figure. The same goes for band overlap and midpoint progression: ask the recruiter for the band of the level you are offered, then compare your offer against that band's midpoint.

When a target employer is under consideration, check how people with your background landed there. If directors from small companies routinely arrive one level lower, plan for it in the scope line instead of finding out in the offer. Refolk scores how well you fit each posting, which shows early when a scope line reads a level below the role.