Systems Administrator Salary Guide for 2026

A systems administrator in the United States earns a median salary of $96,800 per year, according to the Bureau of Labor Statistics. The full range stretches from around $60,000 at the entry level to north of $150,000 for senior sysadmins in high-cost metros or specialized industries. If you’re hiring one or trying to figure out what you should be earning, those numbers are only useful once you understand what moves them.

I’ve spent most of my recruiting career in the IT staffing space, and systems administrators are one of those roles that every company needs but nobody thinks about until the Exchange server crashes on a Tuesday morning and nobody can send email. The salary conversation for sysadmins is different than it is for developers or cloud engineers. There’s less hype. Less venture capital inflating comp packages. But the actual supply-demand picture is tighter than most people realize, especially in Southern California where we do most of our placements.

What the Salary Data Actually Shows

Pull up five different salary databases and you’ll get five different numbers. That’s normal for any role, but it’s especially noticeable with sysadmins because the title covers a huge range of responsibilities. Someone managing a three-server closet at a 200-person company and someone running a hybrid VMware/Azure environment across four data centers are both called “systems administrator.” They’re not doing the same job.

The PayScale and Salary.com numbers look low compared to the rest. They are. PayScale’s dataset skews toward earlier-career respondents, and Salary.com’s $73,667 figure specifically measures their “Systems Administrator I” classification, which is basically year-one-to-two territory. The BLS median of $96,800 is the most methodologically sound anchor point. When I’m advising a client on what to budget for a mid-level sysadmin in 2026, I start there and adjust for location, certs, and how complex their environment is.

Glassdoor’s $112,674 is the outlier on the high end, but that’s total compensation including bonuses and on-call stipends. Not base salary. Important distinction when you’re building an offer.

Salary by Experience Level

Experience moves the needle more than almost anything else in this role. A sysadmin with five years of experience managing Active Directory and a couple of VMware clusters is not interchangeable with someone fresh out of a CompTIA A+ bootcamp, and the pay gap reflects that.

The jump from entry to mid-level is where the biggest percentage increase happens. That 0-2 year sysadmin making $62,000 can be pulling $95,000 within four years if they pick up cloud certs and land in a slightly larger environment. We placed a sysadmin last year who’d been stuck at $68,000 for three years at a small manufacturing company, managing maybe 40 endpoints and a single server rack. Moved them to a healthcare company with a 500-seat hybrid Azure/on-prem environment. Starting salary was $97,000. Same person. Different context.

Where You Work Changes the Number

Geography still matters for sysadmins more than it does for developers. Developers can realistically work fully remote for a Bay Area company while living in Austin. Sysadmins? Many of these roles still require someone physically present. Servers need racking. Hardware fails. The UPS battery in the closet doesn’t replace itself.

Southern California runs 23-32% above the national median depending on which part of the metro you’re in. Orange County is the highest in SoCal, partly because of the defense and aerospace concentration in the Irvine corridor and partly because there’s just less sysadmin talent available relative to demand compared to LA proper. We see this in our own placement data at KORE1. A mid-level sysadmin search in OC takes us on average about 10 days longer to fill than the same search in downtown LA. Smaller talent pool, pickier employers, higher floor on comp expectations.

The DC area number looks surprisingly low. That’s because PayScale’s Arlington data at $89,088 doesn’t fully capture the cleared sysadmin market. Federal contractors with active TS/SCI clearances working on classified networks are pulling $115,000-$140,000 easily, but those salaries don’t always show up in public databases because the positions themselves are classified or ambiguously titled.

Industry Moves the Floor and the Ceiling

Not all sysadmin jobs are created equal, and the industry you’re in determines both the baseline pay and how high the ceiling goes.

The BLS Occupational Employment Statistics break it down by sector. Information services pays the most at $107,310 median, followed by finance and insurance at $98,970. Government sits at $91,250, which is below the national median but comes with pension benefits, union protections, and the kind of work-life balance that the private sector does not offer.

Glassdoor’s industry data paints a slightly different picture when you include total compensation. Energy, mining, and utilities top their list at $104,868, which makes sense. Those companies run SCADA systems, process control networks, and industrial infrastructure where a misconfigured firewall rule doesn’t just cause downtime. It causes physical safety incidents. The premium reflects the stakes.

Aerospace and defense comes in at $102,690, and financial services at $102,204. One pattern I’ve noticed in our placement work is that finance companies tend to offer lower base salaries than tech companies but make up for it with bonuses that can add $15,000-$25,000 on top. A $92,000 base in fintech with a 15% annual bonus ends up outpacing a $105,000 base at a startup with no bonus structure. Ask about total comp, not just base. Always.

Certifications That Actually Move Pay

Not every cert is worth the study time. Some are table stakes. Some open doors. Some are resume decoration that nobody checking references has ever asked about.

Based on what we see in actual job requirements and offer letters, here’s what moves money in 2026:

AWS Certified SysOps Administrator is the single most valuable cert a sysadmin can hold right now if the goal is maximizing salary. Dice reports that AWS-certified sysadmins average 15-25% higher than their uncertified peers. We’ve seen it firsthand. A candidate with five years of on-prem Windows experience and an AWS SysOps cert is getting callbacks from companies that wouldn’t have looked at them otherwise. The cert signals that they can work in hybrid environments, which is where the vast majority of midmarket IT shops are right now. Not fully cloud. Not fully on-prem. Stuck in the middle and desperate for someone who can manage both.

The Microsoft Azure Administrator (AZ-104) does similar things. It replaced the old MCSA, and if anything the demand is stronger because Microsoft has pushed Azure aggressively into enterprise environments. Our 2026 SoCal salary report flagged Azure skills as one of the top three pay differentiators for infrastructure roles in the region.

Red Hat RHCSA and RHCE. These matter in specific environments but matter a lot. If a company runs RHEL in production, they won’t consider a sysadmin without at least the RHCSA. The RHCE is a performance-based exam, not multiple choice, and hiring managers in Linux shops treat it as proof that someone can actually do the work rather than just talk about it. We placed a sysadmin into a biotech company in San Diego last fall. They had three other candidates with more years of experience but hired the person with the RHCE because the CTO specifically said “I need someone who can fix a broken GRUB config at 11 PM without asking me what to do.”

CompTIA Security+ is table stakes for any government-adjacent or compliance-heavy environment. It won’t get you a raise on its own, but not having it will get you screened out of a significant chunk of sysadmin roles, especially in defense, healthcare, and finance. Think of it as the ante, not the winning hand.

CISSP is worth mentioning because it’s the cert that moves sysadmins into a completely different salary band, but it’s also a different career path. A sysadmin with a CISSP is usually pivoting toward security engineering or security architecture, and those roles pay $130,000-$170,000. It’s less of a sysadmin cert and more of an exit ramp into a higher-paying discipline. If you’re a sysadmin wondering how to break through the $120,000 ceiling, security is probably the fastest route.

The Job Outlook Question

The BLS projects a -4% decline in systems administrator jobs through 2034. That number gets quoted a lot, usually by people arguing the role is dying. It’s not dying. It’s changing.

14,300 openings per year. That’s the other BLS number, and it gets conveniently ignored in the “sysadmin is dead” discourse. Those openings come from retirements, promotions, and people leaving the field. Even in a declining-headcount occupation, 14,300 annual openings across 363,100 total positions means roughly 4% of the workforce turns over every year. That’s a lot of hiring.

What’s actually happening is that the pure on-premises sysadmin role, the person who only manages physical servers and never touches a cloud console, is shrinking. It should be shrinking. Running your own Exchange server in 2026 when Microsoft 365 exists is a choice that most companies have already moved past or are actively moving past. But the hybrid sysadmin, the person who manages Active Directory, maintains the on-prem network infrastructure, handles the VPN, AND manages the Azure or AWS resources? That role is growing. The title is the same but the job description has expanded.

We’ve seen this in our network engineer salary data too. The roles aren’t disappearing. They’re absorbing cloud responsibilities and getting relabeled. A sysadmin from 2018 who picked up Terraform and Azure is now a “Cloud Infrastructure Engineer” making $135,000. Same person. Different title. 40% raise.

Remote vs. On-Site Pay

Mixed picture here. Glassdoor data from late 2025 showed remote sysadmins averaging around $105,574, which is actually above the national median. ZipRecruiter pegged it lower, at roughly $89,000.

The real answer is that it depends entirely on whether the role is truly remote or just “remote until something breaks.” A lot of sysadmin roles are advertised as remote but have an asterisk. You’re remote until the SAN throws an error that can’t be diagnosed from a VPN. You’re remote until someone needs physical access to the server room for a firmware update. You’re remote except for the two weeks per quarter you need to be on-site for infrastructure audits. Those aren’t really remote jobs. They’re on-site jobs with generous work-from-home policies.

Fully remote sysadmin positions, the ones where there is genuinely no physical infrastructure to manage, tend to be cloud-heavy roles that are really cloud administrator jobs wearing a sysadmin title. And those pay well. But they’re also a different skillset, and the competition for them is national rather than local.

For candidates in Southern California specifically, the math often works out better taking the on-site role. A $122,000 on-site sysadmin position in Orange County beats a $105,000 remote position if you’re already living here and not planning to relocate. The cost-of-living arbitrage that makes remote work attractive for developers in cheap metros doesn’t apply the same way when you’re already in an expensive metro.

What Hiring Managers Get Wrong About Sysadmin Comp

The most common mistake I see is budgeting for an entry-level salary and writing a mid-level job description. You want someone who can manage your Active Directory, your VMware cluster, your backup infrastructure, your Azure tenant, your VPN, AND be on-call 24/7. That’s not a $68,000 hire. That’s $95,000 minimum, more in California, and if you post it at $68,000 you’ll get the applicants that $68,000 buys. Which is a recent grad who will need six months of hand-holding before they’re useful. There’s nothing wrong with hiring entry-level and growing them. Just don’t pretend you’re doing that when you actually need someone productive on day one.

Second mistake is not accounting for on-call comp. Sysadmin is one of the few IT roles where on-call is genuinely common and genuinely disruptive. Not like a developer who might get paged once a quarter. Sysadmins get woken up when the backup job fails, when the domain controller loses replication, when the VPN concentrator crashes and the CEO can’t access email from his hotel. If your sysadmin is on-call and you’re not compensating for it, either through an explicit stipend ($500-$1,500/month is typical) or through a higher base salary, you’re going to lose them to a company that does.

Third. Stop asking for 10 certifications in the job posting. I reviewed a sysadmin req from a client last month that required CompTIA A+, Network+, Security+, Server+, MCSA (which has been retired since 2021), CCNA, AWS Solutions Architect, and “preferred” CISSP. That person does not exist at the salary they were offering. Pick the two or three certs that actually matter for your environment and drop the rest.

Negotiation Leverage Points for Candidates

If you’re a sysadmin trying to figure out what to ask for, the data above gives you the framework. But numbers alone don’t win negotiations. Here’s where I’ve seen candidates actually move the offer upward.

Quantify your uptime. “I maintained 99.97% uptime across a 200-server environment for 18 months” is worth more in a negotiation than any certification. Hiring managers understand downtime costs. If you can tie your work to avoided losses, that’s real money.

Know the replacement cost. If you’re already employed and considering a move, understand that your current employer would spend $15,000-$25,000 in recruiting fees, plus 3-6 months of reduced productivity, to replace you. That context matters when you’re asking for a raise. You’re not threatening to leave. You’re helping them understand the economics of keeping you.

Cloud skills are the multiplier. The difference between a sysadmin who only knows on-prem and one who can also manage Azure AD, Entra ID, and Intune is $15,000-$25,000 in the current market. If you’ve been meaning to get the AZ-104, do it. The ROI per study hour is better than almost any other professional development investment in IT right now. KORE1’s salary benchmark tool can help you see where you fall relative to the market for your specific skill combination.

Things People Ask Us About Sysadmin Pay

$96,800 keeps showing up. Is that really what sysadmins make?

It’s the BLS median, which means half earn more and half earn less. As a central tendency measure it’s solid. But “median” hides a lot. A junior sysadmin in a low-cost market might make $58,000. A senior sysadmin with AWS certs in Orange County might make $140,000. Both are “systems administrators.” The title is almost uselessly broad, which is why salary ranges for this role are wider than most people expect.

Should I take the government sysadmin job even though it pays less?

Maybe. Depends on what you value. Government sysadmin salaries average around $91,250 according to BLS, which is below the private sector median. But factor in the pension, the health insurance that doesn’t cost $600/month for a family, the actual 40-hour weeks, and the fact that nobody is calling you at midnight because a marketing deploy broke the staging server. I’ve had candidates take $15,000 pay cuts to move into county or federal IT jobs and tell me a year later it was the best decision they ever made. I’ve also had candidates who went nuts from the bureaucracy inside six months. Know yourself.

Is systems administration actually dying?

No, but the version of it where you spend all day in a server closet swapping RAID drives is shrinking. The BLS projects -4% through 2034, which gets a lot of attention. The 14,300 annual openings that exist despite that decline get less attention. What’s really happening is the role is expanding into cloud operations, and sysadmins who refuse to touch cloud platforms are pricing themselves into a narrower and narrower market. The ones who add Azure or AWS to their toolkit end up with titles like “Cloud Infrastructure Engineer” and salaries 30-40% higher. Same foundation of knowledge. Different ceiling.

Realistically, what certs should I get first?

If you’re early career, Security+ and then AZ-104. Security+ because it’s required for too many jobs to skip, AZ-104 because Azure is the dominant enterprise cloud platform and the cert proves you can operate in it. If you’re mid-career and already have a few years of Windows server experience, go straight for the AWS SysOps Administrator or AZ-104 depending on which cloud your current employer uses. If you’re in a Linux shop, RHCSA first, RHCE when you’re ready. Skip anything that’s been retired. Do not study for the MCSA in 2026.

How big is the pay gap between sysadmins and software developers?

Real. The BLS median for software developers is roughly $130,000, compared to $96,800 for sysadmins. That’s about a $33,000 gap, or 34%. Dice puts the gap at about $18,700 when comparing to the average tech professional salary of $112,521. The structural reason is that developers are generally seen as revenue generators (they build the product) while sysadmins are classified as overhead (they keep the lights on). Whether that’s fair is a different conversation. The compensation data is what it is.

Do remote sysadmin jobs actually exist?

They exist, but read the fine print. About 60-70% of the “remote sysadmin” postings we see have on-site requirements buried in the description or discussed during the first screen. Truly remote sysadmin work almost always means cloud-only infrastructure. If there’s physical hardware involved, expect to be within driving distance. The salaries for genuine remote sysadmin roles cluster around $89,000-$105,000 nationally, which is competitive with on-site roles outside of coastal metros but below what you’d earn on-site in places like LA or Orange County.

Where to Go From Here

If you’re a hiring manager trying to fill a sysadmin role and the salary numbers above are higher than you expected, you’re not alone. The market has moved. The $70,000 sysadmin of 2020 is the $95,000 sysadmin of 2026, partly because of inflation and partly because the role now requires cloud skills that didn’t used to be table stakes.

If you’re a sysadmin trying to figure out your next move, look at the certification section above and figure out which of those gaps you can close fastest. The quickest path to a meaningful raise in this role is adding cloud administration to your skillset and then either negotiating internally or looking externally. Both work. External moves tend to produce larger jumps but require you to rebuild institutional knowledge at the new company. Internal moves are smaller but compound faster if the company promotes from within.

We staff systems administrator roles through our IT staffing practice at KORE1, across Southern California and for remote positions nationally. If you’re hiring and need help benchmarking comp for your specific requirements, or if you’re a sysadmin looking for your next role, talk to our team. We’ll give you a straight answer on what the market looks like for your situation, whether or not we end up working together.