The Résumé Said "Networking Experience." The Candidate Could Not Ping a Gateway.
A hiring manager at a regional managed service provider described a familiar situation: a candidate listed two years of help desk experience, held a CompTIA A+ certification, and interviewed confidently. On day three of the job, a user reported intermittent connectivity. The new hire opened a ticket, escalated immediately, and waited. The tier-2 engineer who picked it up ran ipconfig /all, spotted a DHCP conflict, and resolved it in four minutes. The new hire had never run that command in a live environment.
That gap, between what a résumé describes and what a person can actually execute at a terminal, is the central problem in help desk hiring. It costs teams time, erodes user trust, and burns out the tier-2 engineers who absorb the overflow. The fix is not a harder interview question. It is a verified, hands-on signal collected before the offer letter.
What Tier-1 Actually Requires (and Where It Stops)
Tier-1 support is not simple work. A competent tier-1 agent handles password resets, software installs, printer issues, and basic account provisioning, often across multiple tools simultaneously while managing user expectations. The skills required are real: clear communication, ticket documentation discipline, basic OS navigation, and the judgment to know when a problem exceeds their scope.
But tier-2 readiness is a different category. It requires the ability to investigate, not just report. The agent who is ready to move up can do the following without being coached through it:
- Read and interpret command-line output, not just run a script someone else wrote
- Isolate whether a problem is at the OS layer, the network layer, or the application layer
- Use built-in diagnostic tools (Event Viewer,
netstat,traceroute,nslookup,systemctl) to gather evidence before escalating - Recognize patterns across multiple tickets that suggest a systemic issue rather than a one-off failure
- Document findings in a way that a senior engineer can act on without asking follow-up questions
None of those skills show up reliably on a résumé. A candidate who lists "Windows troubleshooting" may mean they have rebooted machines and reinstalled drivers. Or they may mean they have traced a Group Policy conflict through gpresult /h and identified the conflicting OU. The résumé does not tell you which one.
The Specific Skills Worth Testing Before You Hire
Based on what actually separates tier-1 from tier-2 performers in the field, these are the skill areas that predict readiness, and the specific tasks within each area that are worth verifying.
Command-Line Navigation and File System Literacy
A tier-2-ready candidate can navigate a file system, locate log files, read their contents, and filter for relevant entries, on both Windows and Linux. Ask them to find the last ten lines of a system log. Ask them to search a directory for files modified in the last 24 hours. These are not trick questions. They are the actual first steps in most real investigations. Candidates who cannot do them will escalate everything that requires looking below the GUI surface.
Network Diagnostics
The ability to run and interpret ping, traceroute (or tracert), nslookup, and netstat is a baseline tier-2 skill. More importantly, the candidate should be able to explain what the output means. A response time that spikes at hop three is different from a request that times out at the destination. A candidate who can articulate that difference has the mental model needed to investigate network-adjacent tickets without constant supervision.
User Account and Permissions Troubleshooting
Active Directory and local account issues make up a significant portion of escalated tickets. A tier-2-ready candidate should be able to check group membership, identify locked accounts, review last logon timestamps, and understand the difference between a disabled account and an expired password. In a Linux environment, they should be comfortable with id, groups, and file permission inspection using ls -l.
Process and Service Management
When an application is unresponsive, a tier-2 technician does not just ask the user to restart. They check whether the relevant service is running, review recent errors in the event log or journal, and determine whether the issue is isolated or recurring. On Windows, that means Task Manager and Services. On Linux, that means systemctl status and journalctl. Candidates who have only worked in GUI-heavy environments often have no frame of reference for this.
Documentation Under Pressure
This one is harder to test in a terminal scenario, but it matters. Tier-2 work generates documentation that tier-3 engineers and vendors rely on. A candidate who can run the right commands but cannot write a coherent summary of what they found and what they did will create as much friction as a candidate who cannot run the commands at all. Structured written exercises, even brief ones, reveal this quickly.
Why Certifications Are Not Enough on Their Own
CompTIA A+, Network+, and similar certifications are useful signals. They indicate that a candidate has studied a defined body of knowledge and passed a multiple-choice exam. That is not nothing. But the exam environment is not the work environment. A certification tells you that a candidate knew the answer to a question about DNS record types at a specific point in time. It does not tell you whether they can run nslookup -type=MX domain.com in a live terminal and interpret the output correctly while a user is waiting on the phone.
The gap between certification knowledge and applied skill is well-documented in IT hiring. It is not a knock on certifications. It is an argument for pairing them with a hands-on verification step before extending an offer.
What a Verified Hands-On Signal Looks Like in Practice
OpsTicket, a product of IT Custom Solution LLC, is built specifically for this verification step. Candidates work through real terminal scenarios, the kind that mirror actual tier-1 and tier-2 work, and their performance is scored against a deterministic rubric. Not an algorithm's judgment, not a self-reported skill level, but a documented record of what the candidate did and did not do in a live environment.
For help desk hiring, the platform covers the helpdesk track with scenarios that test the skills described above: file system navigation, network diagnostics, account troubleshooting, and service management. Recruiters and hiring managers receive a verifiable certificate tied to the candidate's actual performance. The Pro tier is available at $49 per month. Full pricing is at tryopsticket.com/pricing, and the platform is live at tryopsticket.com.
The result is a hiring signal that does not depend on how well a candidate describes their experience. It depends on what they actually did when given a terminal and a problem.
A Short, Useful Takeaway
If you are screening help desk candidates for tier-2 potential, focus your evaluation on three things: can they navigate a command line without prompting, can they read diagnostic output and draw a conclusion, and can they document what they found in a way that is useful to someone else. Those three capabilities predict more about tier-2 readiness than years of experience or certification count. Build your screening process around verifying them, and you will spend less time on escalations that should have been resolved at tier-1.
If you want to talk through how hands-on assessment fits into your current hiring workflow, reach out for a brief consult. No pitch, just a practical conversation about what verification looks like for your team size and hiring volume.