IT support specialist phone screen questions: tier, on-call, a spoken troubleshooting check and reset requests
On this page
- What do you need from the IT manager before the call?
- How should a 25-minute IT support specialist phone screen run?
- Which knockout questions come first?
- How do you test troubleshooting on a phone screen?
- How do you check security judgment on a reset request?
- Which tools and certifications should you check?
- How do you test motivation on an IT support phone screen?
- How do you ask about pay without asking salary history?
- When should you advance an IT support specialist?
- What should you not ask an IT support specialist on a phone screen?
- Questions people ask
An IT support specialist phone screen is a 20 to 30 minute recruiter call that places the candidate on the right tier and in the right environment before the IT manager spends time on them. Confirm the tier they work (phone and chat service desk, walk-up desktop support or tier 2 escalations), the platforms they support every day, how many users and tickets they handle, and whether they can work the hours, on-call and on-site days the seat needs. Then have them talk through one problem out loud and ask how their desk verified a caller before a password reset. "IT support" on a resume can mean reading a reset script or imaging laptops and running access requests for a 400-person office; the screen should tell you which.
This page is the first-call version. The deeper bank, with a longer troubleshooting scenario, desk metrics and documentation questions, is in help desk technician screening questions; the IT manager's loop, with a ticket queue exercise and a social engineering role-play, is in the interview guide for IT support roles. The general call structure is in phone screen questions for recruiters.
What do you need from the IT manager before the call?
The title covers very different desks, so the intake decides what you screen for. The IT support specialist job description template shows where each fact belongs in the posting, including the overtime classification.
| Fact | Why the screen needs it | A usable answer (example) |
|---|---|---|
| Tier and channel | A phone-only tier 1 desk and a walk-up desktop role need different strengths. | "Tier 1 on phones and chat; tier 2 is a team of two." |
| Users and sites | Supporting one floor is different from driving between branches. | "About 450 users, a head office and two branches 20 miles apart." |
| Platforms | Lets you ask one task question per platform instead of reading a list. | "Windows 11 laptops, a few Macs, Microsoft 365, Intune." |
| Ticketing tool and volume | A candidate from a ten-ticket week may struggle on a busy desk. | "ServiceNow; about 25 tickets a day per technician." |
| Hours, on-call and weekends | Schedule fit is the knockout that surfaces at the offer if nobody asks. | "7 to 4 on site; one week in six on call by phone; quarterly patch weekends." |
| Physical work and driving | Carrying equipment and driving between sites must be stated the same way to everyone. | "Moves monitors and laptops between floors; drives a pool car to the branches." |
| Admin rights the role holds | Tells you how much the security questions matter. | "Resets passwords and MFA, adds users to groups; no server access." |
How should a 25-minute IT support specialist phone screen run?
- Opening (1 to 2 minutes). Who you are, the seat in two sentences, the length of the call, and your consent line if you record.
- Knockouts (4 to 5 minutes). Tier, platforms, hours and on-call, location and driving, work authorization.
- The troubleshooting talk-through (6 minutes). One scenario, answered out loud.
- The reset-request check (3 minutes). Identity verification and pressure from a senior caller.
- Tools and certifications (3 minutes). One task question per tool the desk uses.
- Motivation, pay expectations and logistics (4 minutes). Why now, pay needed, notice, other processes.
- Their questions and the next step (2 minutes). Consent to submit and availability for the hiring manager.
The timings are a planning example. If a knockout fails, say so kindly and end the call or redirect.
Which knockout questions come first?
| Question | What a good answer sounds like | Weak answer or red flag |
|---|---|---|
| What tier do you work now, and how do tickets reach you: phone, chat, walk-up or a queue? | A tier and a scope: "Tier 1 on phones for 600 users. I close password, printer and Outlook tickets and escalate network and server issues." | "I fix everything", with no tier, no users and no escalation path. |
| Which platforms do you support every day, and what do you do in each? | Names them with a task: "Windows laptops, I enroll them in Intune; Microsoft 365, I manage mailboxes and licenses." | A list matching the posting word for word, with no task behind any item. |
| The seat runs [hours], with [on-call rotation and patch weekends]. Is that workable? | A yes to each part, or a specific limit stated now. | "Whatever they need", then a no-on-call request at the offer. |
| The role is on site at [location] and [drives between branches]. Does that work, and if driving is part of the job, do you hold a valid driver's license? | A direct answer matched to the order. | Expects fully remote work for a walk-up desktop role. |
| Are you legally authorized to work in the US, and will you now or in the future need visa sponsorship? | A direct answer to both parts. | None from the answer. Ask the same two parts of everyone. |
The authorization wording follows the Justice Department's Immigrant and Employee Rights Section FAQ, which says an employer may generally ask whether applicants have the legal right to work in the United States and whether they will need visa sponsorship (as of November 2026). Ask about a driver's license only when driving is a real part of the job, and ask every candidate for the seat.
How do you test troubleshooting on a phone screen?
Read one short scenario and ask the candidate to talk through what they would do. There is no single right answer: you are listening for questions before fixes, the order of checks, a workaround for the users and the point of escalation. Use the same scenario for everyone for the seat. The deeper bank uses a password and Outlook scenario; this one tests whether the candidate scopes a problem before touching anything.
Scenario: "It's 9:10 on a Monday. Three people on the second floor call to say the internet is down. People on the first floor are working normally. What do you do?"
A strong answer usually includes:
- Scoping questions first: which users, wired or wireless, every site or one application, since when, and whether anything changed over the weekend.
- Reasoning out loud that a working first floor points to something local to the second floor, such as a switch, a wireless access point or a network closet that lost power, rather than the building's internet connection.
- A quick check they can run: whether the wireless network is visible, whether the laptops received a network address, whether a known-good laptop works on a wired port up there.
- A workaround so people can work: a wired port, a desk on the first floor, or web access by phone for anyone with a deadline.
- A clear escalation to the network team or provider, with what has been checked so far.
- An update to the affected users and a ticket note the next technician can follow.
Red flags: starts restarting laptops one by one without asking a question; calls the internet provider first; never tells the users what is happening.
Follow-up questions that show depth:
- "What would you tell the three users while you work on it?" Good: an honest estimate and a workaround, in plain words. Weak: jargon, or nothing until it is fixed.
- "When would you hand it to the network team, and what goes in the ticket?" Good: a time or test threshold, and a note with symptoms, scope and steps already tried.
- "Tell me about a ticket you got wrong. What happened next?" Good: an honest story and what they changed. Weak: has never been wrong.
How do you check security judgment on a reset request?
Password and multi-factor resets are where help desks get attacked. A joint CISA and FBI advisory on the Scattered Spider group (first published November 16, 2023, last revised July 29, 2025) describes calls made "to convince IT help desk personnel to reset passwords and/or transfer MFA tokens." Three questions show whether the candidate treats verification as part of the job.
| Question | What a good answer sounds like | Weak answer or red flag |
|---|---|---|
| How did your desk confirm a caller's identity before a password or MFA reset? | A named procedure: a call back to the number in the directory, a manager's confirmation, an identity check in a tool, or a video check against the employee photo. | "If they knew their employee ID and manager's name, I reset it." |
| A caller says they're the CFO, boarding a flight, locked out, and needs MFA moved to a new phone now. What do you do? | The same verification anyway, politely, with an escalation if the caller pushes. | Makes an exception because the caller is senior and in a hurry. |
| A manager asks you to give a new starter "the same access as Sam". What do you do? | Checks the request against the approval process or the role's access list before granting anything. | Copies every group Sam belongs to. |
A candidate who describes a firm procedure and then says they would bend it for an executive is telling you what happens on a busy Monday. Score the second answer, not the first.
Which tools and certifications should you check?
Ask for a task, not a tool list. One question per tool the desk uses is enough:
- Ticketing (ServiceNow, Jira Service Management, Freshservice, Zendesk): "What do you put in a ticket before you escalate it?"
- Directory and identity (Active Directory, Microsoft Entra ID, Google Admin console): "How do you unlock an account, and how do you find out why it locked?"
- Device management (Intune, Jamf): "How did a new laptop get from the box to a user's desk at your last job?"
- Microsoft 365 or Google Workspace: "How do you give someone access to a shared mailbox or a shared drive, and how do you remove it?"
No certification is legally required. The ones that appear most on resumes, as of November 2026:
- CompTIA A+. CompTIA requires two exams, Core 1 (hardware and networking) and Core 2 (operating systems and security). Its renewal policy says A+ is valid for three years from the certification date and can be renewed through continuing education.
- ITIL Foundation. PeopleCert sells both ITIL 4 Foundation and ITIL Foundation (Version 5), plus a bridge exam for ITIL 4 holders. It shows service management vocabulary (incidents, requests, changes), not troubleshooting skill.
- Microsoft 365 Certified: Endpoint Administrator Associate. Earned by passing exam MD-102; Microsoft Learn lists a 12-month renewal frequency, renewed with a free online assessment. More common at tier 2 and in desktop engineering.
- Google IT Support Certificate. Offered on Coursera; Google says it has no prerequisites. An entry-level signal, often held by career changers.
For someone moving into IT from retail or a call center, a certificate plus a strong talk-through is a fair signal. For someone with three years on a busy desk, the troubleshooting and reset answers matter more than any certificate.
How do you test motivation on an IT support phone screen?
| Question | What a good answer sounds like | Weak answer or red flag |
|---|---|---|
| What has you open to a move right now? | A specific push or pull: wants tier 2 work, a Mac environment, a lighter on-call rotation, a move from a managed service provider to one company. | Only complaints about users, told with contempt. |
| What do you want to be doing in two years? | A direction (systems, security, cloud, staying in support as a lead) you can compare with the seat's real path. | A plan that needs a different seat within months, for a role that has no such path. |
| If your company offered more to stay, what would it take? | "Nothing realistic", with a reason. | "The promotion they keep promising", which is counteroffer risk. |
| Where else are you interviewing, and how far along? | Stages and timing, names optional. | "Nowhere", then an offer deadline appears. |
How do you ask about pay without asking salary history?
Many states and cities bar employers and their agents from asking about current or past pay, as of November 2026; the list is in salary history ban states. Ask what the candidate needs instead, in the unit the job pays. The Department of Labor's Fact Sheet 17E says the computer employee exemption covers systems analysis, design, programming and similar work, paid at the standard salary level or at least $27.63 an hour, and does not include employees engaged in the manufacture or repair of computer hardware. Most support seats are overtime-eligible as a result; confirm with the hiring manager before the call.
| Ask this | Not this |
|---|---|
| "What hourly rate do you need for this move?" | "What do they pay you per hour now?" |
| "The range is [$X to $Y] an hour, plus [on-call pay]. Does that work for you?" | "How much on-call pay do you get at your current job?" |
| "Besides pay, what matters most: schedule, on-call, remote days, a training budget?" | "Can you send a recent pay stub?" |
If the candidate volunteers a number, keep it out of your notes and the submittal and record the expectation instead. This is general information, not legal advice; check the law where the job is located.
When should you advance an IT support specialist?
Knockouts (all must be yes)
- Works at the tier the seat needs, or is ready for it in the hiring manager's view.
- Supports the main platforms, or close ones the manager accepts.
- Can work the hours, on-call rotation and weekends as described.
- On-site location, travel and any driving work as stated.
- Kept to a verification procedure on the reset question.
- Work authorization answered, and sponsorship needs known.
| Area | 1 | 2 | 3 |
|---|---|---|---|
| Tier and platform match | Different tier, unfamiliar platforms | Right tier, some platforms new | Right tier and platforms, similar volume |
| Troubleshooting talk-through | Fixes before asking anything | Some scoping, no workaround | Scopes, checks in order, works around, escalates with a note |
| Security judgment | Resets on request | Verifies, bends under pressure | Verifies every time, escalates politely |
| Tools | Tool names only | Tasks described for some tools | Tasks described for each tool the desk uses |
| Communication and motivation | Jargon, no clear reason to move | Clear with prompting, reason given | Plain words unprompted, specific reason and timeline |
An example rule to agree with the hiring manager: advance when every knockout passes, troubleshooting and security judgment score at least 2, and two other areas score 3. Hold when one fact, such as the on-call rotation, needs the manager's view. Decline when a knockout fails. For the hire's first quarter, see the 30-60-90 day plan for IT support specialists.
What should you not ask an IT support specialist on a phone screen?
The EEOC says pre-employment inquiries should be limited to what is needed to judge whether someone is qualified, and that employers may not ask about disability before an offer. Its guidance on pre-employment questions allows asking whether a candidate can perform the job's functions, with or without reasonable accommodation. IT screens drift toward age, because "keeps up with new tech" gets used as a proxy.
| Do not ask | Ask instead |
|---|---|
| "Any back problems? You'll be carrying monitors." | "The role carries equipment up to [weight] between floors. Can you do that, with or without accommodation?" |
| "How old are you? The team is pretty young." | "Which tool did you learn most recently, and how did you learn it?" |
| "Do you have kids? On-call weeks are tough." | "On-call is one week in six, by phone until [time]. Can you commit to that?" |
| "Where is your accent from?" | "The desk takes calls in [the languages the job requires]. Can you support users in [language]?" |
If you take the screen through your computer, Interview Signal keeps the troubleshooting and reset questions pinned until you ask them and writes the candidate's own words beside each score, with no bot in the call.
Questions people ask
What should I ask an IT support specialist on a phone screen?
Ask which tier they work and how tickets reach them, which platforms they support every day, how many users and tickets they handle, and whether they can work the hours, on-call and on-site days the seat needs. Then have them talk through one problem out loud, ask how their desk verified a caller before a password or MFA reset, and finish with motivation, pay expectations and logistics.
How do I test an IT support candidate's troubleshooting on a phone screen?
Read one short scenario, such as several users on one floor saying the internet is down while another floor works normally, and ask the candidate to talk through what they would do. Listen for scoping questions before any fix, a sensible order of checks, a workaround for the users, a clear point of escalation and a ticket note. Use the same scenario for every candidate for the seat so the answers can be compared.
Is CompTIA A+ required for IT support jobs?
No law requires it; it is an employer preference. CompTIA says A+ requires passing two exams, Core 1 on hardware and networking and Core 2 on operating systems and security, and its renewal policy says A+ is valid for three years from the certification date and can be renewed through continuing education, as of November 2026. Ask when they passed and whether it is current, then rely on the troubleshooting and reset answers.
Are IT support specialists exempt from overtime?
Usually not. The Department of Labor's Fact Sheet 17E says the computer employee exemption covers systems analysis, design, programming and similar work, paid at the standard salary level or at least $27.63 an hour, and does not include employees who manufacture or repair computer hardware. Most help desk and desktop support seats are overtime-eligible, so confirm the classification with the hiring manager and ask pay expectations in hourly terms.