Sysadmin (systems administrator)

A sysadmin, or systems administrator, administers, maintains and secures the systems and servers that support an organisation’s IT services. They keep them running, handle incidents and prepare changes. Their work enables teams to use applications, storage and equipment in line with the company’s requirements.

Their remit may cover servers, virtualised systems, software and user access. They monitor performance, organise maintenance and intervene when a service deteriorates. They also contribute to infrastructure changes. Depending on their assigned responsibilities, they may test solutions, prepare deployment to production and document operations.

The scope of the role depends on the organisation and the authority delegated to it. Some administrators cover both systems and networks; others specialise.

Systems administrator, network administrator and security specialist: who does what?

• The systems administrator looks after the systems, software and access within their remit.
• The network administrator focuses on the infrastructure that connects equipment. Both functions may be combined in a single role.
• Security responsibilities are shared between the administrator and specialist contacts. Define which operations the administrator carries out themselves and which they must refer to those specialists.

The sysadmin works with IT management, technicians, users and the relevant service providers.

An unavailable system can prevent teams from accessing the tools or data they need. The role therefore involves connecting technical decisions to how the business uses its systems: which services should be maintained, which service degradations should take priority and which interruptions should be planned with users? These priorities give monitoring indicators meaning.

Backups are another critical consideration. Their configuration must account for the nature of the data and the organisation’s constraints. A documented restoration procedure and tested recovery arrangements give those involved a process to follow. For a business leader, the useful question is whether a usable service can be restored after an incident.

Hypothetical example: a company changes the system hosting its shared documents. The files are backed up, but the restoration procedure has not been adapted to the new environment. If the migration fails, the team has to improvise part of the recovery. Preparing and testing that recovery before the change reduces this uncertainty.

Access management also has consequences for the organisation. Permissions unrelated to users’ responsibilities can expose data; overly restrictive access rights can block their work. The sysadmin implements the agreed access rights and keeps their administration up to date. They therefore need people who can make decisions about access needs.

Finally, a poorly defined recruitment brief can leave responsibilities unassigned. Expecting one person to cover all systems, the network and security matters, without specifying their delegated authority or available support, makes priorities difficult to maintain.

• Install, configure and maintain the systems and software within the assigned remit.
• Monitor service performance and availability using indicators suited to how services are used.
• Diagnose incidents, prioritise interventions and record the responses.
• Administer accounts and permissions in line with users’ responsibilities and agreed access rights.
• Configure and test backups, then document restoration procedures.
• Automate identified recurring operations using suitable scripts and tools.
• Test infrastructure changes and prepare their integration into production, together with the associated recovery arrangements.
• Update documentation and give those involved the information needed to operate the systems.

Useful training for the role should develop skills in systems administration, securing operations and making infrastructure changes. The French professional qualification administrateur d’infrastructures sécurisées is one possible route. Its scope also includes networking and security activities, so the relevant skills depend on the precise responsibilities of the role.

This qualification can be obtained by completing a training programme or accumulating blocks of competencies. Learning can take a practical form through projects: installing a system, configuring a backup or writing a restoration procedure. These tasks connect technical knowledge to the operations the administrator will need to prepare, carry out and document. They can be completed under supervision, without assuming immediate autonomy in production.

Professional experience complements this learning through the responsibilities undertaken: maintaining an existing environment, contributing to a change or handling incidents. It develops within a defined scope of delegated authority, with support that varies by organisation. Taking part in a project and deciding on a production change therefore represent different kinds of experience.

To prepare for a new role, further learning may focus on operations that the person has had little opportunity to practise or on the company’s environment. Support should reflect these needs and the expected level of autonomy, without requiring one particular qualification or a uniform number of years of experience.

To assess a sysadmin candidate, use the following situations and adapt them to the systems and delegated authority planned for the role.

1. Define the criteria before the interviews

Separate the skills needed from day one from those that can be acquired with support. Choose criteria relevant to the role: diagnosis, access management, restoration, changes and communication.

For each criterion, specify the expected level of autonomy. You can distinguish between an operation carried out with help, a task handled independently and a decision requiring input from someone with decision-making authority. Use the same benchmarks to compare candidates.

If you lack the technical expertise, involve an IT manager or an expert in the relevant area. Assign them the technical assessment and retain responsibility for assessing communication with users and suitability for the responsibilities.

2. Discuss an incident the candidate handled

Ask the candidate to describe an incident they personally handled. Ask them to specify the symptoms, the information available, their actions and the people they consulted. Ask how they established that the service had been restored.

A strong answer distinguishes observed facts from assumptions. It explains why a line of investigation was pursued and, where applicable, abandoned. Also examine the record left for others involved.

Probe an answer that remains collective or vague. The candidate should be able to explain their contribution without disclosing confidential data. Do not confuse confident storytelling with technical competence: return to the decisions made.

3. Set a scenario relevant to the role

Hypothetical example: after an update, several users can no longer access a service. You provide a description of the environment and some monitoring information.

Ask what further information the candidate would like and how they would organise their response. Invite them to explain their priority checks, the limits of their actions and when they would call on someone else.

Observe how they proceed with incomplete information. Acting immediately without clarifying the scope merits discussion. Explicit reasoning and attention to the effects of changes are positive signs.

4. Examine a restoration and a change

Ask how the candidate would prepare to restore data in the environment presented. Ask them to specify the information needed, the procedure to follow and the checks that would establish whether the result is satisfactory.

For an infrastructure change, ask what they would test before deployment to production. Explore the recovery arrangements planned in case of difficulty. Distinguish concrete answers from a simple list of tools.

If automation is an important part of the role, ask the candidate to talk through a short script suited to it. Ask about its purpose, what triggers it and how its execution can be monitored. Keep the exercise proportionate to the expected responsibilities.

5. Assess handover skills and cross-check responsibilities

Ask the candidate to explain the same incident to a user and then to a technical contact. Observe whether they adapt the detail and make the consequences for people’s work understandable.

Examine an anonymised example of documentation or ask them to write a short handover note. Look for a usable description of the actions completed and the points still to be addressed.

If you take references with their consent, focus your questions on their remit and autonomy. Cross-check the situations discussed, then set out the support needs that still need to be planned for.