What to look for when hiring help desk techs

Help desk is the face of your IT. When someone says "our IT is terrible," they almost never mean the firewall config. They mean the person who answered the ticket. So hiring help desk techs is really hiring for how your whole company will feel about IT, and most companies screen for exactly the wrong things.

Patience beats certifications

The standard help desk resume screen looks for CompTIA A+, maybe Network+, maybe a year of ticket experience. Those are fine. They prove someone can study. What they don't prove is the trait that actually predicts success in the role: staying calm and kind with a frustrated person who describes every problem as "the internet is broken."

The technical bar for tier-one help desk is genuinely learnable. Password resets, printer queues, Outlook profiles, VPN clients, basic Windows troubleshooting: a smart, patient person picks this up in weeks. What's nearly unteachable is temperament. A tech who sighs audibly, talks down to users, or blames the person for the problem will be technically correct and universally hated. We've seen brilliant techs washed out of help desk roles because users started routing around them, and we've seen former retail and restaurant people become the most-requested tech in the building.

That doesn't mean ignore technical skills. It means rank them second. Screen for temperament first, aptitude second, current knowledge third.

Screening questions that predict user happiness

Skip the trivia. Asking someone to recite the OSI model tells you nothing about how they'll handle a VP whose laptop died before a board meeting. Ask questions that force them to show how they work with people:

• "Explain what DNS does to someone's grandmother." You're not grading the technical accuracy. You're watching whether they can drop the jargon, whether they get impatient, and whether the explanation is actually clear. Techs who can only explain things to other techs generate tickets that end in "user still confused."
• "Tell me about a time a user was angry at you for something that wasn't your fault." Listen for whether they stayed professional and whether they still solved the problem. A candidate who mostly wants to explain why the user was wrong is telling you how they'll treat your staff.
• "A user says email is down. It's not down for anyone else. Walk me through what you do." You want a structured approach: verify the symptom, check the obvious (network, credentials, client), reproduce it, escalate with details if stuck. You also want to hear them ask the user questions respectfully instead of grabbing the machine and going silent.
• "What do you do when you don't know the answer?" The right answer includes some version of "tell the user honestly, set a follow-up time, and go find out." The wrong answer is bluffing.
• "What's something you taught yourself recently?" Help desk is an entry point. You want someone who tinkers, runs a home lab, or at least reads. That curiosity is what turns a ticket-closer into your next sysadmin.

If you can, add a short practical: hand them a laptop with two or three planted problems (wrong DNS, disabled network adapter, a full print queue) and watch them work. Fifteen minutes of that beats an hour of interview talk.

Red flags

• Contempt for users. Any joke about "stupid users" or an ID-10-T error in an interview. If they'll say it to you while trying to impress you, imagine month six.
• Can't say "I don't know." Bluffing on a help desk means wrong fixes, hidden mistakes, and escalations that arrive too late.
• No troubleshooting structure. If their answer to every scenario is "reboot it" or "Google it" with nothing behind it, they'll close tickets without fixing problems.
• Certifications with nothing underneath. A candidate with four certs who can't describe how they'd actually diagnose a slow computer memorized exam dumps. It happens more than you'd think.
• Bad written communication. Half of help desk is ticket notes and follow-up emails. Sloppy, terse, or confusing writing in their application carries straight into your ticket system.
• Everything was someone else's fault. Past jobs, past managers, past users. The pattern follows them.

How to know you hired well

Give it 60 days and look at three things. First, reopen rates: are their tickets actually fixed, or do the same problems bounce back? Second, what users say unprompted. When staff start asking for a tech by name, you hired the right person. Third, their questions. A good junior tech asks more and better questions in month two than month one, because they're learning your environment instead of coasting. If instead you're hearing complaints about attitude, seeing tickets closed with one-word notes, and fielding the same problems twice, trust the pattern early. Temperament doesn't improve with tenure. That's why when we screen help desk candidates for clients, the interview is mostly about people, and the technical part is a laptop with something wrong with it.