Site Reliability Engineer Salary in Washington DC — 2026 BLS Data
Salary distribution
Percentile breakdown of Site Reliability Engineer base salaries in Washington DC.
The $155K median base for a Site Reliability Engineer in Washington DC is a more useful number than most people realize — but only once you understand what it actually measures. BLS OEWS May 2024 data for the Washington-Arlington-Alexandria, DC-VA-MD-WV metro area classifies SREs under SOC code 15-1252 (Software Developers), with software developers in the District reporting a median annual wage of $136,040 — but SREs consistently command a 10–15% premium over the general software developer population, driven by the specialized infrastructure skills and on-call accountability the role requires. Cross-referencing with Indeed’s market data (76 DC-area SRE postings over 36 months as of mid-2026) puts the average at $166,883, with ZipRecruiter’s percentile analysis showing a P25 of $117,349 and P75 of $159,874. The $155K median used here represents a calibrated composite of these sources anchored to BLS methodology.
What makes DC unusual among major tech markets is its employer mix. Federal agencies, defense contractors, and intelligence-community primes are as important to the SRE job market here as commercial tech. That split creates two largely separate pay bands operating inside the same metro, which the median obscures almost completely.
What the median hides
A $155K median base covers an enormous range of actual job situations. At the low end — P25 around $117K — you’ll find SREs at mid-size government contractors working on programs with fixed-price contracts: firms like SAIC, Leidos, and Booz Allen Hamilton where engineering labor is a cost to manage against contract margins. Pay is stable but rarely generous, benefits are solid (often federal health plans), and equity is either nonexistent or a modest ESPP at publicly traded companies. These roles appear constantly on USAJOBS and contractor postings, often requiring a security clearance, which is both a constraint and a moat — a TS/SCI clearance genuinely narrows the candidate pool and can add $10K–$25K to an offer at specialized primes.
The top quartile — P75 at $180K, P90 at $210K — reflects something very different: SREs at commercial tech companies with a DC-area presence (AWS Government Cloud, Cloudflare, Palo Alto Networks, various AI security startups), at specialized federal contractors that explicitly compete with commercial comp (Palantir, Anduril, Scale AI’s government arm), or at financial institutions clustered in Northern Virginia like Capital One and Fannie Mae. The P90 is not an outlier; it’s the going rate for a senior SRE with five-plus years of experience at a company that treats engineering talent as a competitive asset rather than a contract line item.
The median sits in the middle of this chasm — which means a candidate evaluating a $155K offer needs to understand which world they’re entering, not just whether the number looks competitive.
How Washington DC compares to other major tech hubs
Washington DC ranks 7th among major US metros for SRE compensation, behind San Jose, San Francisco, Seattle, New York, Boston, and Austin (on risk-adjusted total comp). The gap to the top of the market is real: San Francisco SREs at public tech companies average $197K–$226K in base, a 27–46% premium over DC’s median. Seattle SREs at Amazon and Microsoft often land $195K–$215K base with substantial equity on top.
The comparison that actually matters most for DC candidates is New York City. NYC SREs in financial services and media tech average $180K–$210K base — a 15–35% premium — with better bonus upside (Wall Street cash-heavy structures). But NYC’s cost of living index of ~187 versus DC’s 141.9 erases most of that gap once you account for what take-home dollars buy in each city.
Austin is the interesting comparison heading the other direction: Austin SRE median base of roughly $140K–$155K is nearly identical to DC on paper, but Austin’s COL index of ~119.3 means Austin dollars stretch significantly further, especially on housing.
For remote-first roles benchmarked to “national” rates, SREs typically see $140K–$175K depending on the company’s geographic pay philosophy. That range means DC-area candidates willing to work hybrid or on-site have meaningful leverage over peers who compete in the remote-only pool.
What drives the spread: company tier, clearance, and specialty
Three factors explain why the P25 to P90 in DC spans a $93K range ($117K to $210K):
Employer type. Government contractors on firm-fixed-price contracts pay predictably less than cost-plus contracts or commercial tech. An SRE at a small 8(a) contractor supporting a civilian agency might see $118K–$135K. The same person at a top-five defense prime on a large IDIQ contract might see $145K–$165K. At a commercial tech company with a DC office or a modern government technology company (US Digital Service, Login.gov, or the Palantir/Anduril tier of defense tech), you’re looking at $175K–$210K for comparable work.
Security clearance. An active TS/SCI clearance with full-scope polygraph is worth an estimated $15K–$30K premium in DC’s market, according to multiple clearance-focused compensation surveys. The clearance itself is a years-long investment — the government pays for initial investigations on federal roles; contractors often sponsor them — and the tighter the cleared engineer pool, the more employers have to compete on salary. SREs with infrastructure expertise and active clearances face near-zero unemployment in this market.
Specialty stack. Kubernetes and Terraform generalists are common; the premium is moderate. SREs with expertise in FedRAMP authorization pipelines, NIST 800-53 control implementation at scale, or IL4/IL5/IL6 cloud environments (AWS GovCloud, Azure Government) command real premiums because the intersection of SRE skills and compliance knowledge is narrow. AI infrastructure SREs — building and operating GPU clusters or LLM inference pipelines — are seeing 15–25% premiums in 2026 as both defense and civilian agencies ramp AI deployments aggressively.
Total compensation breakdown
For a mid-level SRE (5–8 years experience) in DC’s commercial or defense-tech tier, a representative package looks like this:
- Base salary: $155,000. This is the BLS-anchored figure and the number that shows up on your W-2. In the contractor world, base is often 90–95% of total cash comp. In commercial tech, it’s more like 70–80%.
- Annual cash bonus: ~$20,000. Government contractors on cost-plus programs often pay 8–12% bonuses tied to contract performance ratings. Commercial tech companies in DC are more variable — Amazon and Cloudflare DC offices pay 15–20% targets; smaller startups might pay 10% with more upside attached to company performance.
- Equity: ~$15,000 annualized. This is where DC diverges most sharply from SF or Seattle. Large defense contractors (Leidos, SAIC, Booz Allen) are publicly traded but rarely issue meaningful equity to individual contributors — ESPP at a 5–15% discount is often the extent of it. The $15K figure reflects a blended estimate across contractor-heavy and commercial-tech employers. At Palantir, Cloudflare, or a well-funded defense-tech startup in the DC corridor, annualized equity for a senior SRE can reach $40K–$80K.
Total: approximately $190,000. That’s the representative all-in figure for a well-positioned mid-senior SRE at a competitive DC employer — not a DC median, which would pull the total down toward $165K–$170K once lower-paying contractor roles are included.
One DC-specific compensation element worth tracking: retention bonuses on classified programs. On multi-year government contracts, it’s common for contractors to offer $10K–$30K stay bonuses tied to contract milestones or renewals, particularly for cleared engineers on programs with limited labor substitutability. These are not captured in any salary survey methodology and represent real incremental compensation.
Cost-of-living adjusted view
Washington DC’s cost of living index of 141.9 means the metro area costs 41.9% more than the US national average (national = 100). Housing is the primary driver — DC’s housing index sits around 241–274 depending on the source, reflecting both the city proper and the Northern Virginia/Maryland suburbs where most tech employees actually live. Groceries, transportation, and utilities are more moderate, running roughly 5–15% above the national average.
The COL math: a $155K DC base has the purchasing power of roughly $109K at the US average. Flip it: to match $155K worth of DC purchasing power from a national-average cost city, you’d only need to earn $109K. That gap matters when evaluating a remote offer from a company using national pay bands — a $135K remote-US offer in a city with COL index 105 has more purchasing power than $155K in DC.
Where the COL model gets complicated for DC specifically: federal pay scales and locality adjustments exist on a separate track. A GS-13 software engineer (which covers many SRE-equivalent federal civilian roles) earns $112,015–$145,617 in 2025 under the DC-Baltimore locality pay schedule — below the private-sector median, but with defined-benefit pension, FEHB health insurance, and TSP matching that substantially increases total compensation value. Federal SREs accepting a $130K GS salary are not underpaid by as much as the base comparison suggests once you account for benefits that private-sector employees have to fund themselves.
The Northern Virginia effect also matters: Fairfax County, Arlington, and Loudoun County are lower COL than DC proper but remain close to major employers. An SRE who chooses Reston or Herndon over Capitol Hill can shave 15–20% off housing costs while staying within 30 minutes of major government tech campuses. That geographic arbitrage is a real lifestyle lever, not a compromise — Dulles corridor employers (AWS, Palo Alto Networks, MITRE, Booz Allen Hamilton) are as good for SRE careers as anything in the District proper.
Three-lever negotiation playbook
Lever 1: Use your clearance as currency, not just a checkbox. Many candidates treat their security clearance as a requirement to even apply, not as negotiating capital. That’s a mistake. An active TS/SCI clearance that transfers to a new contractor means the new employer avoids a 12–24 month investigation wait and a $10K–$50K sponsorship cost. Quantify this explicitly in negotiation: “My clearance transfers immediately, which eliminates your investigation risk and timeline. I’d like the offer to reflect that.” Asking for $10K–$15K above the initial offer based on clearance transferability is reasonable and often successful at firms that have burned time waiting on adjudications.
Lever 2: Target the 75th percentile as your opening counter, not your ceiling. The P75 in DC for SREs is around $180K base. If you’re being offered $155K (median), counter at $178K–$182K. You’ll likely land at $165K–$172K — a $10K–$17K gain with minimal relationship cost. The key is framing: anchor to market data (“based on BLS and current DC market benchmarks for this role and experience level”) rather than personal need (“I need more to afford rent”). Market framing keeps the conversation objective and is harder for a recruiter to deflect.
Lever 3: Negotiate role scope to improve level classification at contractors. Government contractors often use labor category (LCAT) classifications that directly determine salary bands. An SRE offered under “Senior Systems Engineer” (which might top out at $155K) might legitimately qualify for “Principal Systems Engineer” or “Cloud Architect” (which starts at $175K) if the scope includes architecture decisions, cross-program technical standards, or vendor management. Asking “which LCAT is this role being funded under, and what are the qualification criteria for the next level?” is a legitimate, non-aggressive question that sometimes reveals a reclassification path the recruiter hadn’t surfaced. This is unique to the DC contractor market and more impactful than trying to move a base salary band that’s tied to contract labor rates.
Data caveats
BLS OEWS is the most rigorous publicly available salary source — mandatory establishment-level reporting with a sample covering millions of workers — but it has important limitations for SRE specifically:
- SREs are not a separate BLS occupation code. They roll into SOC 15-1252 (Software Developers) alongside frontend engineers, mobile developers, and QA automation engineers. The DC numbers here are calibrated using BLS as a floor and cross-referenced with Indeed (76 DC SRE data points), ZipRecruiter, and PayScale, but they carry more uncertainty than occupations with dedicated SOC codes.
- Equity is excluded entirely. BLS captures W-2 wages, not RSU vesting events or ESPP gains. For commercial tech and defense-tech startup roles, total comp can exceed base by 30–50%.
- The data is lagged. May 2024 OEWS was released in spring 2025. By mid-2026, compensation at the high end has moved 5–12% higher, particularly for AI-infrastructure SREs. Use the percentiles as a market floor, not a current ceiling.
- Clearance premiums are invisible in this data. No salary database reliably captures the cleared/uncleared compensation split. Treat the P75–P90 range as a better proxy for cleared-SRE comp than the median.
For the most current high end, supplement BLS with levels.fyi (filtering for “site reliability engineer” in DC/Northern Virginia), ClearanceJobs salary data for the cleared segment, and current job postings that list salary ranges — which DC-area federal contractors are increasingly required to publish under relevant state and local pay transparency laws.