I've been asked to screen resumes for candidates with strong server or networking skills, but a list of products and protocols doesn't tell me much. What does practical competence look like day to day, and how can I assess it fairly?
How can I spot real server or networking skills on a resume?
Answers
First, pin down what the job actually needs. Server and network work can be separate specialties, while a smaller team may need one person to cover both. Don't screen for deep expertise in both unless the role really calls for it.
Get the manager to identify the must-haves and the work the person will own. Then look for evidence of that work rather than a long product list. A candidate who maintains systems, handles updates and improves reliability may have useful experience even if their resume doesn't frame it as a big project.
Reply to this answer
Look for connections between the technologies. Someone can list Windows Server, virtualization, VLANs and DNS without explaining what they did with any of them. A stronger resume gives you something to ask about: what they maintained or changed, what their responsibility was and how the pieces fit together.
In the interview, pick one example and follow it through. What depended on that server or network? How did they check a change? What would they investigate if clients couldn't reach the service? The depth of the explanation tells you more than the keywords alone.
Reply to this answer
Use a small, relevant troubleshooting exercise after the resume screen. Give everyone the same scenario and enough context to get started, then watch their reasoning rather than expecting a magic command.
A capable candidate should ask what changed, what the system is supposed to do and what symptoms have been observed. They should be able to suggest checks, narrow down possibilities and explain a potential fix or workaround. Resumes can be misleading in either direction, so don't treat writing polish as a technical test.
Reply to this answer
For networking, ask when you'd use a layer 3 switch instead of a layer 2 switch. A useful answer should get into routing between networks rather than just switching traffic within a network.
For a Windows server role that needs PowerShell, ask them to explain objects and properties, then give them a small task relevant to the job. These aren't universal pass or fail questions, but they can start a useful conversation about the depth you need.
Reply to this answer
Don't overlook operational judgment. Ask how a candidate plans for failures, protects backups, limits the spread of an infection and communicates when a change goes wrong. Technical ability matters, but so does owning mistakes and giving people a workable path to recovery.
Reply to this answer
Add your answer
Answers are reviewed before publication.
2n!canvascompass_761:
I'd also listen for how they handle uncertainty. Saying what they would check next is more useful than pretending to know the answer.