Systems administrators keep an organisation's servers, accounts and core services running. They install and update software, manage backups and access, and fix problems before most people notice them.
Where you start matters less than what you can show you have done. This is what the work is built from.
Core skills
Tools and settings
What the work tends to feel like from one day to the next.
Mornings start with checking that the overnight jobs, backups and updates worked. During the day you handle account requests, apply patches, solve problems that others cannot, and work on improvements such as automating a repetitive task. Planned maintenance happens outside working hours, and every change is written down so someone else could understand it.
The day-to-day tasks behind the job title, in plain terms.
There is rarely one route to becoming a systems administrator. These are the two most common.
The most common route: a few years of support gives a feel for users, systems and what breaks.
Running your own services and automating them is practical evidence of the skills.
How people usually show they can do the work, and how employers tend to weigh each route.
Common and helpful, but many engineers are self-taught or retrained. Employers care most about what you can build and explain.
Short, practical certifications for a cloud provider, a security standard or a tool show current skills, and can open doors for career changers.
Public repositories, a deployed project, or write-ups of problems you solved often count for more than any certificate.
As you gain experience the work tends to fork. These are two directions it commonly takes.
Applying the same discipline to cloud-hosted systems.
Making systems resistant to attack and easy to audit.
A typical shape, not a rule: people move at different speeds, and some skip stages.
The most common route: a few years of support gives a feel for users, systems and what breaks.
Get dependable at linux or Windows server administration, user and access management and backup and recovery, and learn how your employer's tools and habits work. This is where trust is earned.
Applying the same discipline to cloud-hosted systems. Security hardening is the other common direction.
Short design notes and post-incident write-ups show how you think, and they are what senior people are asked to produce.
What usually separates people who progress from people who stay level.
Take a feature, a service or an incident from first idea to production, and be the person who can explain every step of it.
Short design notes and post-incident write-ups show how you think, and they are what senior people are asked to produce.
Learn the layer just below and just above the one you work in; most promotions go to people who can see the whole path of a request.
Every role has them. Knowing what they are is part of choosing it well.
Test on a copy, patch in stages, watch closely, and keep a way back.
Write it down as you go, share tasks, and automate steps so they do not depend on memory.
Offer a safe alternative, explain the risk, and involve the owner when you cannot agree.
No role suits everyone. These are the traits that help and the things people say they wish they had weighed first.
Local meetups, online forums and open-source project chats are where hiring managers and peers actually talk shop.
Answering questions and reviewing others' code builds a record people can check before they ever meet you.
A repository or two with a clear readme beats a long list of technologies on a resume.
Lead with the problems you have solved and the systems you have run, not only the languages you know.
The two most common routes are moving up from IT support and certification and a home server lab. The most common route: a few years of support gives a feel for users, systems and what breaks. Running your own services and automating them is practical evidence of the skills.
The essentials are linux or Windows server administration, user and access management and backup and recovery. Employers also value reliability and ownership, clear documentation and communicating planned downtime.
Typical tools and settings include a directory service, backup software, a configuration management tool and a monitoring system. The names change with employer and fashion, so understanding what each kind of tool is for matters more than any one product.
Cloud administration: applying the same discipline to cloud-hosted systems. Security hardening: making systems resistant to attack and easy to audit. To move up in this kind of work, own something end to end: take a feature, a service or an incident from first idea to production, and be the person who can explain every step of it.
Core systems still need care, and administrators who add automation and cloud skills tend to find the widest set of opportunities. It is worth weighing the pace of change, screens and sitting and on-call and deadlines before you decide.
Read the interview questions for the role, then practise answering out loud. HireMonkey lets you upload your resume and a job description and answer an AI interviewer that follows up, then scores each answer and tells you what to fix.
Upload your resume and the job description, and the AI interviewer builds its questions from both. Every answer is scored against the bar for the role, with notes on what to fix.