Hire network and systems administrators

Network and systems responsibilities

List the network, server, identity, virtualization, or other administration duties actually assigned. Include the size and type of environment, supported platforms, and the team or outside provider available for help.

If the role is a generalist position, say so. Explain how user support, administration, and project work divide the week. For a dedicated network role, leave unrelated systems duties out of the opening.

Applicants need to know which changes they can make independently and which require review. State the customer or business owner for the systems and the process for approving access.

Maintenance problems and recovery

Ask about a maintenance task or account change that produced an unexpected problem. What was planned, what happened, and how did they recover or get help? Find out how the affected people were informed.

For a backup responsibility, ask how they know the recovery requirement can be met. Have them explain a restore check they performed and what was still unproven. A scheduled backup is one part of the assignment; the company also needs a clear recovery responsibility.

Use fictional examples. Don't request user lists, private logs, or exports from their current employer.

Change notes and system records

Ask for a short sample change note. It should explain the request, approval, work, result, and remaining issue. Have the candidate describe how they keep system records and support information current after a change.

Discuss a request that lacked authorization or enough information. How did they get the right decision without leaving the requester wondering what happened? This is a practical communication duty, especially in a small company where requests arrive informally.

Support and escalation

Ask how they prioritize a user issue against an infrastructure problem. What information helps establish the impact, and when do they bring in the engineer, vendor, or business owner?

Tell candidates the support queue, after-hours coverage, and handoff process. If this is the only administrator, explain the coverage available during leave. Put the real workload in the offer rather than assuming one person is always available.

Coverage, hours, and pay

Include systems, user-support duties, independent changes, required experience, credentials, training, reporting line, hours, callout terms, location, travel, pay range, benefits, and equipment.

Post the administrator role. For design and larger network changes, use network engineers. For monitoring and first response, see NOC technicians.