Why is it so hard to fill this senior sysadmin role?

November 17, 2026 5 answers
Asked by _y86~canvasfunnel.4

We've been trying to fill a fully remote senior sysadmin role for almost a year and have already gone through three hires. The job pays $135,000 plus a 10% bonus, requires US citizenship and at least six years of experience, and covers Azure, Windows, Linux and Docker. Government experience is a plus.

We're getting a lot of applications, but few seem to meet the requirements. We've also tried a recruiting agency. What should we look at changing?

Answers

n.582~copperwinder

I'd start by breaking down how much of each technology the person will actually own. Senior-level Azure administration plus deep Linux and Docker experience is a different ask from Azure and Windows with basic Linux maintenance and occasional container troubleshooting.

Put the day-one requirements up front, then separate out the skills someone could learn on the job. A strong infrastructure admin who's used another virtualization stack might be able to pick up Docker. Government experience can stay a bonus rather than becoming an unwritten requirement.

_r91+fablemixer.6:

Concrete examples would help too. Patching Linux servers and designing a container platform suggest very different levels of experience.

Reply to this answer
_n74!bracketmaraca.2

The pay could be part of it. $135,000 plus bonus may appeal to some candidates, but people with senior experience across several of those areas may be looking for more, especially in expensive markets.

Check compensation against the actual scope, not just the sysadmin title. If the budget can't move, narrowing the role or hiring someone with room to grow may get you a better pool.

Reply to this answer
v.284~clampthistle

Look at the funnel as well as the applicants. If a remote posting gets hundreds of responses within hours, good candidates can disappear in the pile, particularly when the person reviewing them has another job to do.

Make the citizenship requirement prominent and use a clear eligibility question early. Then review how candidates are being screened for the technical requirements. Someone without Docker on a work history isn't necessarily unable to learn it, and an overly literal screen could miss them. It's also worth checking whether the agency understands which skills are genuinely nonnegotiable.

_y86~canvasfunnel.4:

I'm reviewing applications myself, and the volume gets overwhelming quickly. A clearer eligibility screen would help.

Reply to this answer
6p!mangoferule_382

The onboarding problem is worth examining separately from the skills gap. Missing required meetings and basic training in the first week is concerning, but it doesn't by itself explain why the broader search is struggling.

During interviews, use a practical discussion or a short paid task tied to the real work. Ask candidates to explain how they'd troubleshoot a relevant problem and communicate progress. Also make the first week's meetings and deadlines explicit before they start.

6e!quartzladle_738:

Keep the task focused and short. A long unpaid exercise can turn away the same experienced candidates you're trying to attract.

Reply to this answer
_c36~bracketpocket.7

Don't assume the posting tells candidates enough about the job. Spell out what they'll be responsible for, how much on-call work there is, and whether the citizenship requirement comes with any clearance requirement.

A vague senior title paired with a long technology list can make a role look broader than it is, or leave people wondering what support they'll have.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions