ronutz

The Roles · Who runs it

Systems administrator

Written from published sources

The person who keeps the systems running. The framework lists the work plainly: installing, configuring and updating hardware and software, managing accounts, overseeing backup and recovery, and implementing the controls that policy requires. It is the most widely held technical role in any organisation of size, and the one whose output is measured almost entirely by the absence of events.

What the day looks like

  • Patching, updating and renewing the things that expire: certificates, licences, agents, firmware.
  • Managing accounts and access, which is a security control performed as an administrative task.
  • Backup and, far more rarely and far more importantly, restore.
  • Responding to whatever the monitoring or the service desk sends, in among the planned work.
  • Automating the parts that repeat, in whatever time the unplanned work leaves.

What it answers for

  • The systems being available, current and recoverable.
  • Access being what the policy says it is.
  • Restores actually working, which is knowable only by testing them.

What it is measured on

  • Availability and incident count.
  • Patch currency and audit findings.
  • Tickets closed, which measures the interruptions rather than the engineering.

Who it receives from

The service desk
What users are experiencing, filtered through first-line triage.
Vendors
Patches, advisories and end-of-support dates.
Security and audit
Controls to implement and findings to close.

Who it serves

Everyone in the organisation
Systems that work, which is noticed mainly in its absence.
The security function
The controls, actually applied to actual machines.
The business
The ability to recover, which is worth precisely what the last restore test proved.

Who else has a stake

  • Auditors and insurers, whose questions are about this role's routine.
  • Every team whose application sits on these systems.
  • Whoever inherits the estate, and whatever documentation exists by then.

What it takes

  • Breadth, because the estate contains whatever the organisation bought over fifteen years.
  • Discipline with routine work whose value shows up only when it was skipped.
  • Automation as a habit, since the alternative is a career of the same afternoon.
  • Writing things down, which is the difference between expertise and a dependency.

What the job turns on

The role accumulates knowledge that lives nowhere else. Fifteen years of small decisions — why that service runs on that host, which job has to finish before that one starts — become the reason the estate works and the reason it cannot be handed over. Administrators who write it down convert personal indispensability into organisational capability, and the trade is real: the documented administrator is easier to replace and far easier to promote.

The published sources

Where it leads

Roles that lead here

The work itself

The Practice covers how this work is done — triage, escalation, evidence, handover — across the whole corpus.

Read The Practice