AVP vs VP vs SVP vs EVP: The Complete Comparison
Date Published
AVP, VP, SVP, EVP — four titles, four supposedly distinct levels, and in practice a huge amount of overlap. A VP at a 200-person SaaS company can own more scope than an SVP at a regional bank, and an AVP in corporate banking can outrank a "VP" almost everywhere else. The letters alone don't tell you what someone actually owns. What does, reliably, is scope: headcount, budget, decision rights, and how far up the reporting line runs. This guide lays out where each title typically sits, where the real boundaries fall, and how to check whether your own title ladder matches the scope behind it.
TL;DR
- AVP < VP < SVP < EVP is the typical order, but the gap between each level varies enormously by industry.
- AVP is often an entry point to the executive tier — a working title in banking and financial services more than a scope signal elsewhere.
- VP usually means ownership of a function or a meaningful piece of one, with real budget and headcount authority.
- SVP typically runs a major business unit, region, or enterprise initiative, often with P&L ownership.
- EVP sits at the top of the VP ladder, usually overseeing multiple divisions and reporting straight into the C-suite.
- Title alone is a weak signal — scoring each role against consistent, weighted compensable factors is the only reliable way to know what a title is actually worth.
Where Each Title Sits in the Hierarchy
Most VP-ladder organizations follow roughly this order, though the labels — and how liberally they're handed out — shift by industry and company size.
Level | Typical scope | Usual reporting line | P&L ownership |
|---|---|---|---|
AVP (Assistant/Associate VP) | A defined team, product area, or function within a department | Reports to a VP or Director | Rare |
VP | A full function, or a substantial piece of a larger one; owns budget and headcount decisions | Reports to an SVP, EVP, or a C-suite leader | Sometimes, at the function level |
SVP | A major business unit, region, or company-wide initiative | Reports to an EVP, President, or directly into the C-suite | Common |
EVP | Multiple divisions or a full line of business | Reports to the CEO or President | Almost always |
For the full walk from AVP through the C-suite, including where "Chief" titles fit, see our executive title classification framework. If you only need the SVP layer explained on its own, we cover that separately in what SVP means.
AVP vs VP: Where the Line Actually Falls
Outside banking and insurance, AVP is uncommon — most companies go straight from Director or Senior Manager to VP. Where it does exist, AVP is best read as "not quite a VP yet": someone running a defined slice of a function, often with a small team, but without the budget authority or cross-functional reach a full VP has. A VP, by contrast, typically owns a function outright (or a large, clearly bounded piece of one), sets its budget, and makes the hiring and structure calls for the team under them.
The gap matters most in financial services, where AVP is frequently a working-title rung on a much longer ladder than other industries use — see the next section for why.
VP vs SVP: What Changes at the Senior Level
The jump from VP to SVP is usually the biggest scope change in the ladder, not the smallest. A VP owns a function; an SVP owns a business. That might be a $300M business unit, a full geographic region, or an initiative that cuts across several functions and reports directly to the COO or CEO. SVPs typically manage a layer of VPs and directors beneath them rather than individual contributors, and P&L ownership — real accountability for revenue and cost, not just a functional budget — becomes the norm rather than the exception.
If a "VP" role in your org already looks like this description, the title hasn't kept pace with the job. That's a leveling problem worth fixing before it becomes a pay-equity problem.
SVP vs EVP: The Top of the Ladder
EVP sits above SVP and typically oversees multiple SVPs, multiple business units, or an entire division — think "runs North America" rather than "runs the Northeast region." EVPs report straight to the CEO or President and are usually one step from a C-suite title, if they don't carry one already (Chief titles and EVP titles increasingly overlap at large companies). Below President and the C-suite, EVP is generally the ceiling of the VP ladder itself.
Why the Same Title Means Different Things by Industry
Client-facing industries — banking, insurance, wealth management — have long used VP-level titles, AVP included, for external signaling and, in some cases, as formal "officer" designations tied to signing authority rather than pure internal leveling. That's a legitimate business reason, but it means a bank's AVP and SVP headcount can run far higher, relative to company size, than a software company's. Compare a 5,000-person regional bank to a 5,000-person SaaS company and you'll often find ten times as many VPs and SVPs at the bank — not because the bank has ten times the scope to divide up, but because the titling convention is different. Neither approach is wrong; the mistake is comparing titles across industries as if the words meant the same amount of scope everywhere.
How Much Each Level Typically Pays
Pay ranges for these titles vary too widely by industry, region, and company size to quote a single number that means much — a $150M business unit SVP and a $2B business unit SVP are not comparable jobs even though they share a title. As a general anchor, the U.S. Bureau of Labor Statistics puts the median annual wage for general and operations managers — a broad proxy for functional leadership roles below the C-suite — at roughly $105,800 as of May 2025, with the mean pulled up to about $134,900 by senior and large-scope roles (BLS Occupational Employment and Wage Statistics, May 2025). VP, SVP, and EVP roles with real P&L or multi-function scope typically sit well above that mean, and the spread between the lowest- and highest-paid people carrying the same title can be enormous once you control for actual scope rather than label.
Curious what your own VP and SVP roles are actually worth relative to their scope? See how point-factor job evaluation scores executive roles.
How to Know Which Level a Role Actually Is
Title alone won't tell you. What does is scoring the role against the same compensable factors you'd use for any other job in your architecture: scope of responsibility, budget and P&L authority, span of control, decision-making latitude, and the complexity of what the role is accountable for. That's the same logic behind point-factor job evaluation generally — instead of trusting a title (or a market survey title-match), you score what the job actually requires and let the points, not the label, tell you where it lands. Our guide to span of control is a useful starting factor if you're trying to sanity-check whether a "VP" role really has SVP-level scope.
Avoiding Title Inflation as You Scale
Title inflation compounds quietly. A department head gets an SVP title to make an offer competitive, a peer department matches it to avoid feeling shortchanged, and within a few review cycles the SVP layer is twice as large as the scope underneath it justifies — which then distorts pay bands, promotion expectations, and how the next external hire gets leveled. SHRM has flagged the underlying governance problem: research it cites found that roughly 80% of companies use job titles specifically to reflect the corporate hierarchy, not just to describe the work, which means an inflated title actively misleads the org chart it's supposed to clarify (SHRM, "Job Titles Should Reflect Changing Roles"). WorldatWork makes the structural case for fixing this at the source: a documented job architecture — job families, levels, and profiles defined once and applied consistently — gives leaders "a map of the workforce" and keeps promotion and pay decisions objective rather than negotiated case by case (WorldatWork, "The Business Case for Job Architecture"). Our guides to job title levels and management job titles walk through how to set that structure and where each layer should sit.
FAQ
Is AVP higher or lower than VP? Lower. AVP (Assistant or Associate Vice President) typically sits just below VP, often as an entry point to the executive tier. It's most common in banking and financial services, where it's frequently used as a working title rather than a strict scope signal.
Is SVP higher than VP? Yes, and usually by a wide margin. A VP typically owns a function; an SVP typically owns a business unit, region, or enterprise initiative, often with P&L accountability the VP role doesn't carry.
What comes after EVP? President, then the C-suite (CEO, COO, CFO, and other Chief titles). At smaller companies, EVP sometimes reports straight to the CEO with no President layer in between. See what comes after senior for the fuller progression from individual contributor up.
Do all companies use AVP, VP, SVP, and EVP the same way? No. The order holds directionally almost everywhere, but the scope behind each title — and how many people carry it — varies enormously by industry. Banking and insurance use these titles more liberally than tech, manufacturing, or professional services.
Can a VP outrank an SVP? Not by title, but by actual scope, yes — a VP at one company can have more budget, headcount, and P&L responsibility than an SVP at another. This is exactly why comparing titles across companies without comparing scope is unreliable.
How do I know if my VP and SVP titles are leveled correctly? Score each role against the same weighted compensable factors — scope, budget authority, span of control, decision rights, complexity — rather than relying on the title or a market benchmark's title-match. If two "VP" roles score at meaningfully different point totals, one of them is mislabeled.
Is EVP a C-suite title? Not technically. EVP sits just below the C-suite in most organizations, though at some companies EVP and Chief titles increasingly overlap or get combined (e.g., "EVP and Chief Marketing Officer").
PointFactors scores your executive roles against the same weighted compensable factors as every other job in your architecture, so the title on the door and the scope behind it finally match. Book a demo or see pricing.
Justin Hampton, founder and CEO of PointFactors