Job titles vs. real scope: what actually builds market value

Job titles are local currency. They inflate and deflate by company — a "vice president" at one bank is a mid-level manager, a "head of" at a startup may lead a team of two. Scope is the hard currency: what you owned, how big it was, what happened because of you. The market prices scope. Understanding that changes how you evaluate offers, how you write your resume, and which opportunities you chase.
What the market actually prices
- Owned outcomes. "Ran the launch that added a new revenue line" is worth more than "Senior Manager" on its own. Ownership means the result was yours to deliver and yours to explain.
- Scale. The size of the budget, team, customer base or system you were responsible for. Scale is comparable across companies in a way titles are not.
- Complexity. Cross-functional work, ambiguous problems, multiple stakeholders, regulated environments. Harder scope commands a premium.
- Trajectory. Evidence that your scope has grown over time — each role bigger than the last. Reviewers look for the slope, not the current point.
- Portable skills. Capabilities that transfer between employers, demonstrated through outcomes.
When title and scope diverge
Big title, small scope. An inflated title can feel good and hurt later. If your business card says "Director" and your scope is one small project, you will interview for director roles you cannot do and be screened out of roles you could. Recruiters have seen enough inflated titles to discount them; what they cannot discount is a clear description of scope.
Small title, big scope. This is the common and fixable problem. Many people do far more than their title suggests — an "analyst" running a whole reporting function, a "coordinator" who is in fact the project manager. The fix is to make the scope visible on the resume and in conversation, without lying about the title.
Writing scope onto your resume
Under each title, the first bullet states the scope in plain terms: "Owned the onboarding function for all mid-market accounts — a team of four, roughly 300 new customers a quarter." Then the outcomes. If your title badly understates the role, add a clarifier in parentheses that is honest and recognizable: "Operations Coordinator (de facto project manager for the regional rollout)." Do not change the title itself; that is checkable and being caught costs the offer.
Choosing roles by scope
When comparing opportunities, ask what you will own, at what scale, with what complexity — and where that scope typically leads. A slightly lower title with clearly larger scope is often the better move: the scope becomes the story, and the title catches up at the next transition. Conversely, a title bump attached to a narrower job is a trade you should make knowingly, if at all.
Negotiating title when it matters
Titles do matter in some contexts — client-facing roles where seniority signals matter, industries with rigid hierarchies, and international moves where a title is read literally. If a title is genuinely out of line with the scope you are being offered, negotiate it; employers often have more flexibility on titles than on pay. But negotiate it as a description of the work, not as a trophy: "Given that the role owns the region, would 'Regional Manager' be a more accurate title?"
Growing scope where you are
Scope can be built without a promotion. Volunteer for the cross-team project. Take over the thing nobody owns. Ask to run the next iteration of something you contributed to. Document each expansion as it happens. Eighteen months of deliberately widening scope produces a resume that reads two levels above the title on it — and that is exactly the gap a job change or a promotion case closes.
The habit
Once a quarter, write one sentence describing your current scope in market terms — what you own, how big, how complex. If the sentence is the same as last quarter, you are not growing, whatever your title says. If it is bigger, you are building the currency the market actually pays for, and the title will follow.