The national median cash compensation for a VP of Engineering in 2026 is $231,000. The 10th percentile sits at $152,000, the 90th at $342,000. That is a 2.25x spread between the bottom and top of one title, and if you have spent any time in this job market you already know why: "VP of Engineering" describes at least three different jobs, priced in at least three different labor markets, before you even open a map.
For calibration, the federal anchor: BLS OEWS May 2025 data puts Architectural and Engineering Managers (SOC 11-9041) at a national median of $171,270, with a 10th percentile of $120,810 and a 90th of $262,760, across roughly 220,260 people employed. That SOC blends every flavor of engineering management — civil, mechanical, plant — with software. Software VPs at venture-scale companies price meaningfully above that blended anchor, which is why Boss Playbook applies a documented title premium to get from the government number to what offers actually look like. If a recruiter quotes you the raw BLS median for a VP Eng seat at a funded software company, they are either lowballing you or reading the wrong row.
This guide breaks the number down the two ways that actually matter: geography and company stage. Then it covers the third variable most candidates underweight — team size — and finishes with what to do about all of it when the offer lands.
VP of Engineering Pay by City, 2026
Per-metro figures below are the national numbers localized by each metro's cost multiplier, rounded to the nearest $1,000. Median is the headline; the 25th–75th range is where most credible offers actually land.
| Metro | 25th Percentile | Median | 75th Percentile | vs. National |
|---|---|---|---|---|
| San Francisco, CA | $287,000 | $358,000 | $437,000 | +55% |
| Boston, MA | $259,000 | $323,000 | $395,000 | +40% |
| Washington, DC | $255,000 | $319,000 | $389,000 | +38% |
| New York, NY | $250,000 | $312,000 | $381,000 | +35% |
| Seattle, WA | $241,000 | $300,000 | $367,000 | +30% |
| Los Angeles, CA | $237,000 | $296,000 | $361,000 | +28% |
| Denver, CO | $207,000 | $259,000 | $316,000 | +12% |
| Miami, FL | $207,000 | $259,000 | $316,000 | +12% |
| Chicago, IL | $204,000 | $254,000 | $310,000 | +10% |
| Austin, TX | $200,000 | $249,000 | $305,000 | +8% |
| Salt Lake City, UT | $194,000 | $243,000 | $296,000 | +5% |
| Atlanta, GA | $191,000 | $238,000 | $290,000 | +3% |
| Raleigh, NC | $185,000 | $231,000 | $282,000 | national par |
| Pittsburgh, PA | $170,000 | $213,000 | $259,000 | −8% |
| Columbus, OH | $168,000 | $210,000 | $257,000 | −9% |
How to read the tiers
Tier one — SF, Boston, DC, New York, Seattle. These markets run 30 to 55 percent above national, but the cash premium is only half the story. San Francisco is the most equity-saturated executive market in the country; a $358,000 median there routinely comes attached to an equity grant that dwarfs it. Seattle's $300,000 lands in a state with no income tax, which quietly adds 8 to 10 percent to take-home versus a nominally identical California offer. Nobody prints those two facts on the offer letter side by side. You should.
Tier two — Denver, Miami, Chicago, Austin. The 8 to 12 percent premium markets. Austin is the interesting one: a decade of corporate relocations pushed the top of its band up sharply as Bay Area leadership moved in, so the 75th percentile there ($305,000) behaves more like a coastal number than the median suggests. Texas taxes sweeten it further.
Tier three — Salt Lake City, Atlanta, Raleigh, and the value metros. Raleigh sits at exactly national par with a Research-Triangle talent pool that keeps technical credibility table stakes. Salt Lake City's Silicon Slopes built a real software executive market with equity culture intact at two-thirds coastal cost. Pittsburgh at $213,000 is the arbitrage play: CMU's robotics and AI pipeline means the engineering leadership there is world-class and underpriced relative to the coasts. If you can run a remote-friendly org from a −8% metro on a +30% company's pay philosophy, that spread is yours to keep.
Company Stage: Where the 2x Spread Actually Comes From
Geography explains maybe half the variance in this title. Stage explains most of the rest. The same person, same skills, same year can sign three very different packages.
Seed and Series A
You are the first real engineering executive, often managing fewer than 30 people, and the company cannot pay you like a VP — so it doesn't. Expect cash 20 to 40 percent below the local median and an equity grant that is supposed to make up the difference. At Series B, VP Eng grants typically run 0.5 to 1.5 percent of the company on a four-year vest; earlier than that, push toward the top of the range or above it, because you are taking genuine venture risk with a four-year lockup. Two things matter more than the percentage: the preference stack (a 1% grant behind two participating preferred rounds can be worth less than a 0.4% clean grant) and the strike price relative to the last 409A. A VP who won't ask for the cap table math is telling the company something about how they'll negotiate vendor contracts, too.
Growth stage — Series C through pre-IPO
This is where cash normalizes toward the medians in the table above and equity shifts from lottery ticket to portfolio position. Grants shrink to basis points but attach to a real valuation. The item that matters most here — and the one candidates skip — is the refresh policy. An initial grant, however generous, decays: by year three your unvested value is thinning out, and whether the company issues refresh grants annually, on promotion only, or effectively never determines whether your total comp grows or quietly collapses. The refresh policy matters more than the initial grant by year three. Get it in writing before you sign, not at your first comp review.
Public companies
Late-stage and public VPs flip the startup ratio: top-of-band cash, RSUs instead of options, and predictable annual refreshes that behave like a second salary. The trade is real but honest — you're buying liquidity and a beta-weighted equity position instead of a binary one. The failure mode at public companies isn't the package, it's the scope: a "VP of Engineering" who is one of nine VPs under an SVP is holding a director's job with a better business card. Price the level by the org chart, not the title.
Team Size: The Stair-Step Nobody Puts in the Job Post
VP Eng comp does not scale smoothly with headcount. It scales in steps, and the thresholds are roughly 30 engineers, 80 engineers, and 150-plus. Each threshold is a different job and a different pay band.
- ~30 engineers. You still know every name and probably still read the important diffs. This band overlaps heavily with senior software engineering manager comp — SEM medians run $196,000 nationally — and plenty of companies title it VP anyway. Fine. Take the title, but price the job, not the letterhead.
- ~80 engineers. Managers of managers, real org design, real hiring-machine responsibility. This is the band where the national median ($231,000) actually lives, and where org-design failures — the most expensive mistakes in tech — become your personal P&L.
- 150+ engineers. You are running a company-within-a-company: directors reporting to you, platform and product splits, budget lines a CFO scrutinizes. This is 75th-to-90th percentile territory — $282,000 to $342,000 nationally, well past $400,000 at the 75th percentile in San Francisco.
The negotiation implication is blunt: ask how many engineers the plan assumes in 18 months. If the answer is double the current headcount, you are being hired to build a bigger org than you are being paid for. Reprice the offer against the org you'll be running at month 18, or get a written comp checkpoint when the team crosses the next threshold.
Negotiating the Offer
Four rules, learned the expensive way.
Never negotiate on base alone. Base is the least negotiable and least consequential line in a VP package. The refresh policy, the equity type, and the acceleration terms move more money over a three-year window than any $20,000 base bump.
Trade cash for equity only with information. Current preferred price, option strike, last 409A, and the preference stack — all four, before you sign. Companies that hesitate to share them with an incoming VP of Engineering are telling you how they'll treat you as an insider.
Define the CTO relationship before you sign. Who owns architecture, who owns headcount, who is in the room for the board's technology discussion. Ambiguity there is how VPs get layered a year in. If the company has a CTO, read the CTO compensation picture too — the gap between the two seats tells you how the company actually values each one.
Use geography deliberately. A VP Eng offer in Columbus at Denver numbers is a better deal than a Seattle offer at Seattle numbers, once housing and taxes are in the model. The table above is your anchor — walk in knowing the local median and the national one, and make them explain any offer that sits below both.
Adjacent Seats Worth Pricing
Before you accept, benchmark the seats next door. The Chief Technology Officer band runs a national median of $247,000 in cash — closer to VP Eng than most people assume, because CTO packages carry the value in equity. Down a level, software engineering managers median $196,000 nationally, which is why the ~30-engineer VP band feels crowded from below. Knowing all three numbers is how you spot a mis-leveled offer in the first phone screen — and how you price the promotion you'll be negotiating two years from now.
The 2026 market pays VPs of Engineering for exactly two things: orgs that scale without breaking, and delivery a board can set its watch to. Everything in this guide is downstream of proving you can do both. The number is negotiable. The evidence isn't.