Skip to main content
A systems administrator inspects a removable drive at a server rack

Sysadmin

Keeps the servers, accounts and backups working, and is usually the person who finds out first when they don't.

Role at a glance

The shape of the job

Typical UK pay£30–36k entry · £45–55k senior
ExperienceEarly to mid career
Work patternHybrid, some on-site work
Technical depthBroad, with deep pockets
People contactModerate, mostly IT colleagues
HoursOut-of-hours changes and on-call rotas

Pay bands are TechWaymark practitioner estimates for UK roles, reviewed 2026-09, not survey data. They vary by region, sector and employer.

What the Sysadmin role involves

  • You look after Windows or Linux servers: updates, disk space, services that stop, certificates that expire.
  • You manage accounts and permissions, usually in Active Directory or Entra ID, and you clean up after joiners and leavers.
  • You check backups actually restore, because a backup nobody has tested is a hope, not a backup.
  • You script the jobs you're tired of doing by hand, then document them so someone else can run them.
Read TechWaymark's full role verdict and reasoning
TechWaymark verdict

A systems role built around dependable operation, recovery and controlled change.

Domain
Foundations
Entry
£30–36k
Senior
£45–55k
Pick this if
  • You like owning a problem end-to-end, from the kernel up
  • You're patient with systems that don't fail cleanly
  • You're moving up from helpdesk and want a wider remit, not a deeper queue
  • The advertised on-call arrangement fits your circumstances
Skip this if
  • You want to write software for a living, this isn't that
  • You can't bear documentation, half the job is leaving the next person something to read
  • You see cloud as a clean break from servers, it isn't, you'll meet them all again
  • Your runbooks are the ones people copy
  • You've automated something that used to take a colleague an afternoon
  • You can rebuild a server you've never seen before from its docs and a backup
  • Junior engineers come to you before they raise the ticket
The bit you're probably underestimating

Responsibility can exceed documentation and staffing. Check the recovery evidence, change authority and support available before assuming the estate is manageable.

An administrator works on a laptop beside an open server rack
Some weeks it's all remote. Then a disk fails and you're in the comms room.

Illustrative

A day in the role

  1. Overnight alerts: a file server at 94% disk. Find what grew and whether it's safe to clear
  2. Service desk escalation. A shared drive permission broke after a team restructure
  3. Plan tonight's patching window and warn the finance team their app will drop for twenty minutes
  4. Test-restore last week's backup of the HR database to a spare server
  5. Write a PowerShell script to report accounts that haven't signed in for 90 days
  6. Patch, reboot, check each service came back. Note the one that didn't and why

An example day. Roles and organisations vary, and no two days match.

Day to day

What you'll work with

Systems

Windows ServerLinux (RHEL, Ubuntu)Active Directory and Entra IDVMware or Hyper-V

Tools

PowerShell and BashBackup software (e.g. Veeam)Monitoring (e.g. PRTG, Zabbix)Ticketing and change records

Concepts

Least privilegeChange controlRestore testingDNS and DHCP

Hiring reality

What employers actually expect

Must understand

  • Fix things without making them worse
  • Follow change control, even when it's slow
  • Write down what you did
  • Know Windows or Linux properly, not just the GUI

Commonly expected

  • Service desk or IT support background
  • Basic scripting
  • Virtualisation experience
  • A cert such as RHCSA, LFCS or a Microsoft associate

Sets you apart

  • A tested restore you can describe step by step
  • Automation that removed a recurring job
  • Cloud exposure alongside on-prem
  • Calm on a bad night

What this role isn't

It isn't a helpdesk job with a better title, and it isn't DevOps. You're less likely to fix users' laptops and more likely to own the server their app runs on. You also carry the pager.

How the role changes with seniority

1Junior

Works through server tickets, patches to a plan, escalates anything unfamiliar.

2Experienced

Owns a group of systems, plans changes, automates routine work, joins on-call.

3Senior

Designs how the estate is run, argues for replacements, mentors, and gets called when it's really bad.

An administrator checks a printed patching plan late in the evening
Patching happens when users have gone home, which is why the plan matters.

Nobody puts this in the advert

The hard parts

Invisible when it works

Nobody thanks you for the outage that didn't happen. People notice the one that did.

Out-of-hours work

Patching, maintenance and on-call mean evenings and the odd weekend.

The shrinking title

Many firms now call this Infrastructure or Cloud Engineer. The work overlaps, the adverts don't always say so.

Legacy systems

Someone has to look after the 2012 server nobody dares switch off. It's often you.

More than one way in

How people actually get into it

From IT support

The normal route. Take on server tasks in support until you're doing more of them than tickets.

Apprenticeship

Infrastructure technician apprenticeships lead straight into this work.

Small business generalist

In a small firm the support person is often the admin too. That counts.

Home lab

A couple of virtual servers, a domain, a backup and a written-up restore. It shows you've done it.

Evidence employers value

"Experience with Windows Server"

Moved file shares to a new server over a weekend with a rollback plan, and nobody lost access on Monday

"Good at PowerShell"

A script that reports stale accounts every Monday, and what the first report found

"Responsible for backups"

Restored a database to a test server monthly and cut the restore time from four hours to one

Projects that prove it

Small pieces of work you can do on your own, and what each one shows an employer.

Build a small domain at home

2 weekends

Two virtual servers, a domain controller, a file share with group-based permissions and a test user who joins, moves team and leaves.

What it demonstrates

Active DirectoryPermissionsJoiner and leaver process

Prove a restore

2-3 evenings

Back up a server, break it on purpose, then restore it. Time each step and write the runbook you'd want at 2am.

What it demonstrates

Backup and restoreRunbook writingWorking under pressure

Automate one boring job

1-2 evenings

Pick a task you'd do weekly, such as a disk space report or stale account list, and script it with a clear output.

What it demonstrates

PowerShell or BashSchedulingReadable output

Your next hops

Where Sysadmin can take you

Systems AdministratorSenior Systems AdministratorInfrastructure Engineer

Other common branches

There is no single ladder. See the routes on the Atlas.

Worth the effort?

Certifications that complement it

Interview reality

Questions you may be asked

Loading questions…

Practise with model answers in My Waymark

For educators

Used in TechWaymark Education

These modules use this page as investigation material in the classroom.

  • 1
    Technology is not one career

    An example of work that mainly operates systems, keeping services running day to day

Where this fits

Roles connect to pathways, certs and other roles. Use one to test the next.

Could you realistically get here from where you are?

The Guided Route compares your background with this role and shows the honest route, hop by hop.

Last reviewed 2026-09. Photographs are illustrative.