CV Keywords for System Engineers and Sysadmins (2026)

"System engineer" and "system administrator" cover an unusually wide range of jobs. In a small company the title means one person who owns everything: the servers, the network, the backups, the printer nobody can fix. In a larger organization it can mean a specialist who touches one layer of a platform team's stack. Two postings with the same title routinely describe different jobs, and a CV written for one reads as underqualified for the other.

There is a second problem specific to this role, and it is the one that quietly costs interviews. The job has moved. Postings that still use the old title now ask for things the old title never implied, and a CV that describes only the traditional version of the work answers a job description from several years ago.

This guide lists the term families that recur in infrastructure postings, in the order they actually appear, and shows where each belongs in the document. Everything below applies to a CV and a resume alike, since the screening works the same way.

The job moved and the postings show it

Read enough listings under these titles and one thing stands out immediately: cloud terms appear in more of them than any other family, including the ones you would expect to define the role. Azure shows up ahead of AWS, which reflects how many of these employers are Microsoft shops that grew into the cloud rather than starting there.

This does not mean on-premise skills stopped mattering. Virtualization, Active Directory and backup remain everywhere, and most of these roles are genuinely hybrid. It means the CV that reads as pure on-premise maintenance is now answering half the question. If you have touched cloud work at all, even migrations you supported rather than led, that experience belongs on page one and not buried in a skills list at the end.

The honest caveat: do not manufacture cloud experience you do not have. A CV that claims Azure architecture and cannot survive a technical conversation about it fails later and more expensively than one that never claimed it.

Name the product, not the practice

Recruiters search the applicant tracking system literally, and "virtualization" does not match a search for "VMware". This is the single most common way a strong infrastructure CV becomes invisible, and it is covered in more depth in our guide on how ATS systems read your CV.

So write the product name and let the category follow it, not the other way around:

• "VMware vSphere" rather than "virtualization platforms"
• "Veeam Backup & Replication" rather than "backup solutions"
• "FortiGate" or "Cisco" rather than "firewall management"
• "Windows Server 2022 and Active Directory" rather than "Microsoft environments"

The category words are still worth having, because some postings use them, but they should sit alongside the product names rather than replacing them.

The families that recur

Ordered roughly by how often they turn up in postings for these titles.

Cloud. Azure first, then AWS, with Google Cloud a distant third. Name the services you actually worked with, not just the platform.

Windows and Active Directory. Active Directory is close to universal. Microsoft 365 administration appears nearly as often, and many CVs leave it out because it feels too routine to mention. Windows Server, Group Policy and Exchange complete the family.

Virtualization. VMware dominates this space in a way few other categories are dominated by one vendor. vSphere and ESXi are worth naming explicitly. Hyper-V and Proxmox appear, but far less often.

Backup and continuity. Three distinct things that postings ask for together: backup itself, business continuity, and disaster recovery. If you have ever run a restore test, say so, because a candidate who has actually restored something is different from one who has only configured backups.

Networking. Firewalls, DNS, DHCP, VPN, VLANs and routing. Vendor names matter here too, Cisco and Fortinet especially.

Linux. Present in roughly a third of these postings, and importantly it appears alongside Windows rather than instead of it. If you work in both, say both in the same line, because a recruiter filtering for either will find you.

Automation. Scripting, PowerShell, Python, Ansible, Terraform, and containers. This family used to belong to a different job title. It does not anymore, and it is the clearest dividing line between postings that pay well and postings that do not. If this is the direction you want the next role to take, our DevOps and SRE keyword guide covers what those postings ask for.

Monitoring. Frequently requested, frequently missing from CVs. See below.

Storage. SAN and NAS, capacity planning, the array vendors you have administered.

Process. Documentation, ticketing, SLAs and ITIL. Also frequently under-sold. See below.

The two families sysadmin CVs under-sell

Monitoring and documentation are asked for far more often than they are written about, and both suffer from the same problem: they feel like housekeeping rather than achievement, so people leave them out.

They are not housekeeping to the person hiring. Monitoring is how an infrastructure team finds out about a problem before the business does, and a candidate who has built or tuned monitoring is describing a capability, not a chore. Name the tool. Zabbix, Nagios, Grafana, PRTG and Centreon all appear in postings, and none of them will match a CV that says "system monitoring" and stops there.

Documentation is the same story from the other direction. Employers ask for it because they have been burned by infrastructure only one departed person understood. A line about runbooks you wrote, or a migration you documented well enough that someone else could repeat it, answers a fear the posting is expressing indirectly.

Certifications are named less often than you would expect

Very few of these postings name a specific certification. CCNA, the Microsoft AZ track, VMware's VCP and the Red Hat certifications all appear, but rarely, and almost never as a hard requirement.

Keep the ones you hold, in their own short section near the end. Do not build the CV around them, and do not put them in your headline in place of what you can actually do. This mirrors what we found writing the architect keyword guide: certifications are a tiebreaker in this field, not an entry ticket.

Where the terms go

A skills section alone will not do it. Terms carry more weight when a recruiter sees them attached to something you did.

1. Title line, under your name: the role you are targeting, alongside your real job title.
2. Summary, two or three lines: the environment you run, in product names. "Hybrid Windows and Azure environment, roughly 200 servers, VMware and Veeam on-premise."
3. Experience bullets: this is where the terms should live, attached to an outcome. "Migrated 40 on-premise VMs to Azure" beats "Azure" in a list.
4. Skills section: the remainder, grouped by family rather than listed as one long line.

What a rewrite looks like

Before:

Responsible for the maintenance of company servers and network. Managed backups and user accounts. Provided support to internal users.

After:

Ran a hybrid infrastructure of about 200 servers across VMware vSphere on-premise and Microsoft Azure. Administered Active Directory and Microsoft 365 for 400 users. Owned Veeam backup and quarterly restore testing, including two disaster recovery drills. Automated Windows patching with PowerShell, cutting the monthly maintenance window from six hours to two.

Same job, same person. The second version contains the product names a recruiter searches for, and each one is attached to a scale or a result.

Mistakes specific to infrastructure CVs

Listing every technology you have ever touched. A wall of 60 acronyms reads as a keyword dump to a human and dilutes the terms that matter. Cover the families in the posting properly and let the rest go.

Hiding the scale. Number of servers, number of users, number of sites. Infrastructure work is judged by scale as much as by tooling, and "managed servers" tells a reader nothing.

Describing tickets instead of outcomes. Volume of tickets closed says how busy you were. Reduced ticket volume, or the automation that reduced it, says what you changed.

Leaving cloud out because your role was on-premise. If your company ran anything in Azure or AWS and you touched it, that counts, and the posting is probably asking for it.

Once your terms are in place, the next step is adjusting them per posting rather than sending the same document everywhere. Our 10-minute tailoring routine is the short version of how to do that without rewriting your CV each time.

FAQ

Should I write "System Engineer" or "System Administrator" in my headline?

Use the title from the posting you are applying to, alongside your official one if they differ. The two titles are often used interchangeably by employers, and a recruiter searching for one will not find a CV that only contains the other. Where the posting is Italian and uses "Sistemista", the English terms still belong in the document, because the technology names are identical in both languages.

How much cloud experience do I need for these roles?

Less than you might fear. Many of these postings describe hybrid environments where the cloud portion is a migration in progress rather than a finished platform. Supporting a migration, administering Microsoft 365, or managing a handful of cloud VMs is worth stating clearly. What does not work is claiming architectural ownership of something you have only used.

Is Linux or Windows more valuable on a sysadmin CV?

Neither, and framing it as a choice costs you. Windows and Active Directory appear in more of these postings, Linux in a substantial minority, and a good number ask for both. If you have real experience in both, put them in the same line so that either filter finds you.

Do I need Ansible or Terraform to be competitive?

Not for every role, but automation now appears in a large share of postings under these titles, and it separates the better-paid ones from the rest. If you have written even modest PowerShell or bash automation, that belongs on the CV. If you have not, it is the highest-return thing to learn next for this career path.