A new joiner cannot log in, a file server is nearly full, a domain controller has stopped replicating and the monthly patch cycle starts tonight. All of that lands with the systems administrator, the person who keeps Windows and Linux servers, directory services and day-to-day access running for everyone else. When this work is done properly, staff simply get on with their jobs, and the backups work the one time someone needs them.
This page has a systems administrator job description you can paste into your applicant tracking system, then explains how it changes with experience, what to check before you make an offer, the ad errors that recur for this title and how contract and permanent hiring compare. It also sets the role apart from DevOps, service desk and specialist Linux or Microsoft 365 administrators.
Systems administrator job description template
Update the brackets to match your estate. State the split between Windows and Linux honestly, since few administrators are equally strong on both.
About the role
[Company] is hiring a Systems Administrator to run our server estate of [number] Windows and Linux servers across [on-premises / cloud] environments. You will look after Active Directory, patching, monitoring, backups and access, and act as the escalation point for our service desk. You will report to [manager title] and work from [location].
Responsibilities
- Administer Windows Server and [RHEL / Ubuntu] systems, from build through to decommissioning.
- Manage Active Directory, DNS, DHCP and Group Policy, including domain controller health and replication.
- Run a monthly patch cycle with test groups, approved change windows and rollback plans.
- Monitor servers and services through [monitoring tool], then investigate capacity, performance and availability alerts.
- Manage user access, privileged accounts and joiner, mover and leaver processes with [HR or IT lead].
- Administer file services, shared storage and permissions.
- Run backups in [Veeam / Commvault] and carry out scheduled restore tests.
- Take service desk escalations and write up fixes so that repeat issues get resolved at first contact.
- Automate routine tasks with PowerShell and Bash.
Requirements
- [X] years of systems administration in a business environment.
- Strong Windows Server and Active Directory experience, including Group Policy and troubleshooting authentication.
- Working Linux administration: users, services, storage, logs and permissions.
- Good grasp of DNS, DHCP and basic TCP/IP.
- Patch management experience across a real server estate.
- PowerShell scripting, with Bash for Linux hosts.
- A habit of clear documentation and calm communication during outages.
Nice to have
- Experience with VMware vSphere or Hyper-V.
- Microsoft 365 and Entra ID administration.
- Configuration management with Ansible.
- A Red Hat Certified System Administrator credential or equivalent Microsoft training.
What we offer
- [Salary and benefits].
- [Fixed hours / rotational shifts] with [weekend change window arrangements].
- [Training allowance or lab access].
How the systems administrator role changes by level
Junior systems administrator
Often promoted from service desk, a junior handles account requests, routine patching, disk space alerts and escalated tickets, using runbooks written by others. Ask for a solid understanding of Windows and basic networking, and for evidence of a home lab or structured learning.
Systems administrator
The mid-level post owns services outright: Active Directory health, patch cycles, backup success and server builds. Requirements should call for root cause thinking, scripting that saves real time and experience of at least one significant outage or restore.
Senior systems administrator or infrastructure lead
Seniors plan upgrades, server migrations and capacity, set hardening baselines and represent infrastructure in audits and vendor conversations. They also mentor juniors and decide what gets automated next. Expect wider ownership such as virtualisation, identity integration and disaster recovery runbooks.
Systems administrator skills that matter most, and how to check them
- Active Directory troubleshooting. Ask why some users cannot log in at one site while others are fine. Good candidates check DNS first, then domain controller replication, time sync and Group Policy, and can name the tools they would use.
- Restore experience. Ask about the last time they restored something for real. Anyone can say backups run nightly, whereas someone who has done a restore describes what was slower or harder than expected.
- Patching discipline. Ask them to describe how a monthly cycle runs, from release to reboot. Look for test rings, change approval, handling of a failed update and how they treat servers that nobody wants to reboot.
- Linux basics under pressure. Ask what they would do when a Linux host reports a full disk while the visible files seem small. Deleted files still held open by a process, or inode exhaustion, are the kinds of answers you want.
- Scripting. Set a small PowerShell task, such as reporting stale accounts from Active Directory and exporting the result. It shows whether the candidate writes scripts or only pastes them.
Ask every candidate to explain one outage they caused themselves. The honesty of that story, and what they changed afterwards, is usually a stronger predictor than any certification on the CV.
Common systems administrator job description mistakes
- Combining sysadmin, service desk and network work. An ad that wants laptop rollouts, firewall design and server patching from one person reads as a sign of an understaffed team. Fix: state what is truly core, and name who else covers the rest.
- Asking for DevOps skills that the job never uses. Listing Kubernetes when the estate is Windows file servers pulls in the wrong applicants, and they soon leave. Fix: describe the actual estate, then mention automation only where it will really happen.
- Leaving out out-of-hours expectations. Patch nights and weekend changes shape daily life in this role. Fix: state the frequency and how that time is compensated.
- Not saying which platform dominates. A mostly Linux shop and a Microsoft-heavy one need different people. Fix: give a rough description of the split and list the Linux distributions in use.
- Vague access responsibilities. Administrators can reach sensitive data, yet many ads never mention it. Fix: note the privileged access involved and how it is controlled, which tells serious candidates that you run things properly.
Contract, contract-to-hire or permanent: which suits a systems administrator
Contract administrators are a good fit for project peaks: upgrading ageing Windows Server versions, moving file shares, migrating to new virtualisation, cleaning up Active Directory after an acquisition or covering leave. Decide in advance how privileged access will be issued and removed, because a contractor may hold domain-level rights for the duration.
Contract-to-hire lets you observe how someone behaves when a patch fails at midnight, and how well they document their fixes. For a small IT team of two or three, personal reliability matters as much as technical range.
Permanent hiring suits most ongoing administration. Understanding why an old application needs a particular server, or which business team depends on an odd share, only comes with time. Zilo AI can work with any of these: we hire systems administrators in India on contract, contract-to-hire or permanent terms. Those who need database or identity specialists as well can see more roles on our IT recruitment page.
Frequently asked questions
What should a systems administrator job description include?
Give the size of the estate, the Windows and Linux split, the on-premises and cloud mix, the tools for backup and monitoring, and the hours expected for changes. Name the services the person will own outright and what they only support.
What is the difference between a systems administrator and a DevOps engineer?
A systems administrator keeps servers and shared IT services running for the business, while a DevOps engineer automates how application code gets built and deployed. Administrators increasingly script their work, but their main customers are staff and systems, and developers are a smaller part of it.
Is a systems administrator the same as a service desk engineer?
No. Service desk staff handle user requests and first-line faults, then escalate. The administrator owns the servers and directory behind those requests and takes on the problems that the desk cannot resolve.
Do we need a general systems administrator or a specialist?
A general administrator suits small and mid-sized estates. Once one area demands constant attention, such as a large Linux fleet, Microsoft 365 and Entra ID, or VMware clusters, a dedicated Linux, identity or virtualisation administrator usually pays off.
Are systems administrators still needed when you move to the cloud?
Yes, although the work shifts. Identity, access, patching of virtual machines, backups and cost hygiene remain. Many administrators move towards cloud operations, so check for cloud exposure if a migration is planned.
Looking for a shortlist instead of a job ad? Zilo AI can take on the search and first screening. Reach out with the details of your server estate and the gap you need filled.