Engineering Manager Salary in Washington DC — 2026 BLS Data
Salary distribution
Percentile breakdown of Engineering Manager base salaries in Washington DC.
The $185,000 median base for an Engineering Manager in Washington DC is a real number with a misleading simplicity to it. It comes from BLS OEWS May 2024 data for SOC code 11-9041 (Architectural and Engineering Managers), applied to the Washington-Arlington-Alexandria, DC-VA-MD-WV metropolitan statistical area — a market where the national median of $167,740 gets pushed up by a dense cluster of federal contractors, defense primes, and a growing commercial tech sector. But “Engineering Manager” in DC can mean the person running a 4-person software team at a Series B fintech in Georgetown, or the manager of a $200M systems integration program at a Beltway contractor with a secret clearance. Those two people share a job title and almost nothing else in their compensation structure.
The P25-to-P90 spread — $148,000 to $262,000 — tells you how wide the real market is. This page breaks down what sits at each end and how to figure out which range you belong in.
What the median hides in DC
The national BLS OEWS May 2024 data puts p10 below $111,450 and p90 above $239,200 for this occupation. The DC metro premium for management occupations runs roughly 10-15% above national, based on BLS regional wage data showing the Washington-Arlington-Alexandria area consistently above the national management occupation average. That produces a realistic DC p50 of $185,000 — but the distribution is not symmetric.
The bottom quartile (below $148,000) is populated almost entirely by:
- Government and quasi-government roles. Federal civilian GS-14/GS-15 Engineering Manager equivalents top out at $148,084–$191,900 under the 2024 General Schedule for the DC locality pay area. Many public-sector and nonprofit roles anchor near GS-14 step 1 ($148,084), which is essentially the DC p25 for this occupation.
- Early-stage startups with a first-time EM title and no product-market fit, paying cash-constrained but heavy on unvested equity.
- Small civil/environmental/architecture firms where the “engineering manager” is a licensed PE running a 3-person team on municipal infrastructure contracts.
The top quartile (above $221,000) pulls in:
- Defense prime and intelligence community contractors (Booz Allen, SAIC, Leidos, General Dynamics IT, CACI) running large program teams with clearance premiums on top of base.
- Commercial tech and fintech (Capital One, Appian, AWS GovCloud divisions, Palantir’s DC office) that pay closer to Seattle-scale comp for senior EMs.
- Consulting firm principals (McKinsey Digital, Deloitte, Accenture Federal Services) whose engineering leadership titles often exceed what the government clients pay their own people.
The median of $185,000 is real, but it flattens two genuinely different labor markets into one number.
How DC compares to other engineering management hubs
Washington DC is the fifth-largest metro market for engineering managers by employment, behind San Francisco Bay Area, New York, Seattle, and Boston. The comp picture is distinctive enough to deserve its own map:
San Francisco Bay Area runs the highest median base — roughly $215,000-$230,000 for SOC 11-9041 — driven by FAANG and late-stage growth-stage tech. Total comp at public tech companies routinely reaches $350,000-$500,000 with RSUs. The catch: a COL index of 178.6 versus DC’s 143 means a $185,000 DC base has essentially the same purchasing power as $231,000 in the Bay Area. The gap is real but narrower than the headline numbers suggest.
Seattle runs $200,000-$215,000 median base. Amazon, Microsoft, and a handful of smaller tech companies (Zillow, Expedia, Convoy) dominate hiring. Seattle-based EMs skew toward tech more than DC does, so the clearance-depressed segment of the distribution is smaller.
New York City is the closest peer to DC structurally — a mixed market with finance-adjacent tech (Capital One, Bloomberg, Stripe’s NYC office, Wall Street firms) pulling the top end up and traditional enterprise and media companies anchoring the middle. Median base lands around $195,000-$205,000. COL in Manhattan runs higher than DC; the outer boroughs and Jersey City cut that gap.
Austin comes in around $160,000-$175,000 median. The DC-to-Austin difference looks like $25,000-$30,000 in cash, but COL-adjusted (Austin at ~121 versus DC’s 143) the gap almost disappears.
Boston is the closest comparable to DC in market structure: a government/academia/biotech base with commercial tech layered on top. Median base for EMs runs $185,000-$195,000.
DC’s sweet spot is that it combines solid base pay with lower effective COL than SF or NYC, and the government-contractor ecosystem creates a uniquely stable demand floor. Layoffs hit the DC market less severely than the Bay Area during the 2022-2024 tech correction because headcount at defense primes and fed-adjacent contractors doesn’t track Nasdaq.
What drives the spread: company tier, clearance, and specialty
Three variables explain the bulk of the $114,000 gap between p25 and p90:
Company tier and ownership structure. A GS-15 equivalent EM at a federal agency earns $148,084-$191,900 under the 2024 DC locality pay scale. A program manager/engineering lead at a mid-sized contractor (ICF, Engility, ManTech) earns $155,000-$185,000 base. A senior EM at a defense prime on a cost-plus contract earns $180,000-$215,000. A commercial tech company EM (Capital One’s tech division, AWS’s DC public sector team, Palantir) earns $200,000-$250,000 base plus meaningful equity.
Security clearance premium. A Secret clearance adds roughly $10,000-$20,000 to base for engineering leadership roles; a Top Secret/SCI clearance adds $20,000-$40,000. The Defense Intelligence Agency, NSA, DARPA contractors, and classified DoD program work all sit above the unlabeled market rate for the same level of engineering management responsibility. If you hold an active TS/SCI and can manage cleared teams, the DC market compensates that credential directly in base salary — a structural difference from SF or Seattle, where clearances are irrelevant to most tech roles.
Domain specialty. Software engineering managers (SOC 15-1252 would be more specific, but many are lumped into 11-9041) in commercial tech earn 15-20% more than civil/structural/mechanical engineering managers in DC. AI/ML-adjacent roles — managing teams building intelligence community data products, autonomous systems, or large-scale federal data infrastructure — are at the very top of the distribution, pulling $240,000-$280,000 base at senior levels. Biodefense and cybersecurity EMs sit in between.
Total compensation breakdown
The $185,000 median base is only part of the picture, and the full comp story in DC looks different from SF or Seattle because equity is a smaller component:
Base: $185,000. This is the BLS-tracked figure. At commercial tech companies it’s negotiable within a published band; at government contractors it’s often tied to SCA wage determinations or internal labor categories that reduce flexibility. Government direct employees (GS pay scale) have almost no base negotiation — step increases are automatic.
Bonus: ~$25,000. The DC market runs lower on cash bonus than SF or NYC tech. Government and contractor roles often have no discretionary bonus at all, or a fixed 5-10% annual bonus tied to contract performance. Commercial tech companies (Capital One’s tech division is the largest local example) pay 15-20% performance bonuses at EM level, which pushes total cash for the top quartile closer to $245,000-$270,000. Defense prime annual bonuses average 8-12% for program leadership.
Equity: ~$20,000 annualized. This is where DC diverges most sharply from the Bay Area. The majority of DC’s engineering management jobs sit at government agencies (zero equity), publicly-traded contractors (RSUs that exist but are modest by tech standards), or private-equity-owned contractor firms (equity programs that are opaque and illiquid). Capital One’s tech division and a handful of commercial tech companies in the corridor are the exceptions — their EM equity packages look more like Seattle than the Beltway norm, running $80,000-$150,000 annualized at senior EM levels.
The practical upshot: total comp (base + bonus + equity) at the DC p50 lands around $230,000. At p75 it’s closer to $275,000-$310,000, and almost all of that upside comes from switching from contractor/government to commercial tech or from a clearance premium stacking on top of a high-tier commercial base.
Cost-of-living adjusted comparison
DC’s COL index of 143 means living costs run 43% above the US national average. That’s driven largely by housing — median asking rent for a one-bedroom in DC proper runs $2,100-$2,400; a two-bedroom in Arlington or Bethesda runs $2,600-$3,200. The federal government’s heavy presence keeps high-quality public services and transit (Metro) competitive with comparable peer cities.
Adjusting the DC median of $185,000 for COL: it has the purchasing power of roughly $129,000 at the US national average. Compare that to Austin at $165,000 median (COL ~121), which equals $136,000 in purchasing power — actually slightly higher. Or Boston at $190,000 median (COL ~162), which equals $117,000 in purchasing power — lower than DC despite a higher headline number.
The COL-adjusted calculation matters most if you’re choosing between a DC role and a remote role with geographic pay adjustments. A company offering $155,000 “national rate” for a fully remote EM role has effectively given you a raise if you’re currently earning $185,000 in DC, once you move to a lower-COL city. Many DC-based EMs discovered this arbitrage during the 2020-2023 remote window.
Where COL-adjustment misleads: if you need to live in DC proper for a classified program or an in-person hybrid role with weekly on-site requirements at a government facility, the theoretical purchasing power comparison doesn’t help. The COL premium is a real cash cost, not a negotiating variable.
Three-lever negotiation playbook
DC has specific negotiation dynamics that differ from the standard SF-tech playbook:
Lever 1: Use market tier as your anchor, not just a salary band. The single most effective move in DC compensation negotiation is establishing which tier you’re pricing yourself against. If a Beltway contractor opens at $165,000 for a senior EM and you have comparable experience to what Capital One or AWS pays $215,000 for, that’s your counter — not “I need 10% more than your offer.” Presenting a concrete competing offer from a commercial tech company (even an exploratory one) is the strongest signal that a contractor can’t low-ball with impunity. The DC market segments enough that many contractors genuinely don’t track commercial tech comp until a candidate forces the comparison.
Lever 2: Negotiate the clearance premium separately. If you hold an active TS/SCI and the role requires cleared personnel, price that as a discrete asset. Cleared EM talent in the National Capital Region carries a 15-25% premium over uncleared equivalents performing identical management work. Contractors know this and will sometimes pre-load it into an offer to avoid the conversation — but if it’s not explicit, ask: “How does the compensation account for maintaining an active TS/SCI?” The question itself signals that you know the market and won’t accept uncleared-equivalent pricing for a cleared role.
Lever 3: Push compensation review timing for government-adjacent roles. Federal contractors and GS pay schedules don’t offer the “sign a competing offer counter” dynamic that commercial tech does. What they do offer is annual review cycles, step increases, and promotion-in-place mechanisms that are essentially guaranteed if you hit performance benchmarks. Negotiate the starting step (for GS roles) or the job grade (for contract labor categories) at offer time — not the specific dollar figure, which is often fixed, but the classification that determines the dollar figure. Moving from GS-14 step 1 ($148,084) to step 3 ($157,978) at the offer stage is a permanent $9,894/year difference that compounds across every future raise. Contractors: the equivalent is negotiating your labor category one tier higher at hire — often worth $15,000-$25,000/year in base and is far easier before you start than after.
Data caveats
BLS OEWS is the most rigorous public wage dataset — mandatory reporting covering employers across all industries — but three limitations apply here:
Equity is excluded. For commercial tech company EMs, BLS understates total comp by 15-30%. For the majority of the DC market (government, contractors), this matters less because equity is genuinely smaller or absent. Still: if you’re evaluating an offer with meaningful RSUs from a Capital One, AWS, or Palantir, supplement this data with Levels.fyi, which puts the Washington DC software engineering manager total comp median at roughly $246,000 across all levels.
The SOC code is broad. SOC 11-9041 covers software EMs, civil engineering managers, systems integration leads, and mechanical engineering directors at defense primes. These are meaningfully different jobs with meaningfully different pay. The $114,000 P25-to-P90 spread exists in part because the BLS bucket is doing a lot of work.
Data lag. May 2024 survey data covers wages paid in mid-2024. By mid-2026, the DC commercial tech segment has moved 5-10% higher on base; the contractor/government segment adjusts more slowly (GS locality pay increases, SCA wage determinations) but also moved modestly upward. Use these percentiles as calibration, not as the final word on a specific offer.
For a complete picture: triangulate BLS base data here, total comp from Levels.fyi or Glassdoor for the specific employer tier you’re targeting, and posted salary ranges on current DC job postings (required disclosure for some roles due to DC’s pay transparency requirements under the DC Wage Transparency Act).