You’re now the solo sysadmin for 300 users after your coworker quit, but your paycheck hasn’t changed. Here’s a senior engineer’s guide on how to document your new workload, build a case for a raise, and know when it’s time to walk away.

My Co-Worker Quit. Now I’m a Solo Admin for 300 Users With No Raise. What Do I Do?

I remember this happening to me back in 2014. My counterpart on the infrastructure team, a guy named Kevin who knew our ancient AS/400 system better than he knew his own kids, put in his two weeks. Management smiled, wished him well, and told me, “You’ve got this, Darian!” Two weeks later, on a Friday at 4:55 PM, the primary batch job on that AS/400 failed. The job that processed all our daily orders. No one had a clue how to fix it except Kevin, who was already on a flight to his new gig. That weekend, fueled by cold pizza and pure panic, I learned a lesson that’s stuck with me: when a team of two becomes one, the company doesn’t just lose a person, it inherits a massive, ticking time bomb of risk. And I was sitting right on top of it.

First, Let’s Talk About Why This Happens

Look, it’s rarely because your boss is a mustache-twirling villain. It’s usually something far more common: inertia and the invisibility of competence. When your two-person team was running smoothly, management saw a green status light. When your co-worker left and things *didn’t* immediately explode (because you’re good at your job and picked up the slack), they still see a green light. They don’t see the 12-hour days, the skipped lunches, or the fact that your “bus factor” is now one. In their view, the problem solved itself. Our job is to make the new reality—and the new risks—visible.

So, you have a few paths forward. Let’s break them down from the immediate triage to the long-term career move.

Solution 1: The Quick Fix – The “Document and Automate” Gambit

Your first move isn’t to polish your resume or storm into your boss’s office. It’s to protect yourself and the company, while simultaneously building the evidence you’ll need later. Your goal is to make your workload tangible.

Step 1: Create a “Bus Factor” Document. Create a shared document (Confluence, SharePoint, whatever you use) called “Critical Infrastructure Knowledge Transfer” or something similar. Start listing every single system and process you are now solely responsible for. Be specific.

• System: Active Directory (AD-DC-01, AD-DC-02)
• Knowledge Holder: Darian Vance (formerly Darian Vance & Kevin Smith)
• Risk: No other employee has admin credentials or knowledge of GPO structure. An outage while I am unavailable would halt all user logins.
• System: VMware vSphere Cluster (vcenter.corp.local)
• Knowledge Holder: Darian Vance
• Risk: I am the only person with credentials to the vCenter server and knowledge of the datastore layout on the SAN.

Step 2: Automate the Annoying Stuff. You need to claw back some time. Pick one repetitive, low-risk task that eats up your day and script it. A classic is new user creation. It shows initiative and frees you up for more critical work.

# Super simple PowerShell example for a new user
# This isn't production-ready, but it's a START.

$FirstName = "Jane"
$LastName = "Doe"
$Password = "P@ssword123!" | ConvertTo-SecureString -AsPlainText -Force
$Username = "jdoe"

New-ADUser -Name "$FirstName $LastName" `
    -GivenName $FirstName `
    -Surname $LastName `
    -SamAccountName $Username `
    -UserPrincipalName "$Username@corp.local" `
    -Path "OU=NewUsers,DC=corp,DC=local" `
    -AccountPassword $Password `
    -Enabled $true -ChangePasswordAtLogon $true

Pro Tip: Don’t just do this in secret. Send a brief email: “Hey Boss, to handle the increased ticket volume, I’ve automated the new user creation process. This should save us about 3 hours a week and let me focus on the firewall upgrade project.” You’re showing value, not just complaining.

Solution 2: The Permanent Fix – The “Data-Driven Ask”

After a few weeks of documenting and automating, you have leverage. Now you can stop talking about how you *feel* overwhelmed and start showing them the data. It’s time to build a business case for a raise, a title change, and/or hiring a replacement.

Your case should have three parts: Workload, Risk, and Market Rate.

1. The Workload: Present a simple before-and-after. Use your ticketing system data if you have it. If not, your own logs will do.

2. The Risk: Bring up your “Bus Factor” document. Frame it professionally. “I’m committed to the company’s success, which is why I’ve documented the current knowledge gaps. If I were to get sick or win the lottery, we would be in a very vulnerable position with systems like our production database `prod-db-01`.”

3. The Market Rate: Do your research on Glassdoor, LinkedIn, and Levels.fyi. Find the average salary for a “Solo System Administrator” or “IT Manager” for a company of your size in your region. Say something like, “Based on my research, the market rate for an engineer with this level of responsibility is between $X and $Y. I’m confident in my ability to handle this role, and I’d like to discuss bringing my compensation and title in line with these new responsibilities.”

Solution 3: The ‘Nuclear’ Option – The “GTFO” Plan

Let’s be real. Sometimes, management won’t listen. If you present a solid, data-backed case and get a vague “we’ll see what we can do in the next budget cycle,” or worse, a simple “no,” then you have your answer. They are accepting the risk and have shown they don’t value you.

This is not defeat. This is a gift. It’s the clarity you need to leave.

1. Update Your Resume Immediately: You have a fantastic new narrative. “Solely responsible for all IT operations for a 300-user environment, including server administration, network management, and user support.” That’s a huge upgrade from “Member of a two-person IT team.”
2. Activate Your Network: Discreetly let former colleagues and recruiters know you’re open to opportunities.
3. Interview & Secure an Offer: Don’t even think about quitting until you have a signed offer letter in hand. Continue to do your job professionally in the meantime. You need the reference, and you’re not the kind of person who leaves a company in a lurch (even if they deserve it).

Warning: The Counter-Offer Trap. They will likely panic when you resign and suddenly “find the budget” for a raise. Do not accept it. The fundamental culture of undervaluing you hasn’t changed. They only acted when they were forced to. The trust is broken. Take your new job, thank them for the opportunity, and don’t look back.

Being the last one standing is a stressful, thankless job, but it’s also a fork in the road. You can use it as leverage to redefine your role and compensation where you are, or you can use it as a springboard to a much better opportunity elsewhere. The choice is yours. Just don’t choose to do nothing.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions