Fifteen common IT support interview questions
- Walk me through how you troubleshoot a problem you've never seen.
- A user can't connect to Wi-Fi. What do you check?
- A computer is running very slowly. How do you investigate?
- A printer isn't printing for one user but works for others. What next?
- How do you reset a password securely?
- A user thinks they clicked a phishing link. What do you do?
- What do DNS and DHCP do?
- How do you prioritise tickets?
- When do you escalate an issue?
- How do you explain a technical problem to a non-technical user?
- Tell me about a difficult user and how you handled them.
- How do you document your work?
- What is Active Directory, and what tasks have you done in it?
- How do you set up a new employee's laptop?
- What would you do if you couldn't solve an issue?
A troubleshooting method
Interviewers want a repeatable process: gather information (what exactly happens, since when, what changed, who else is affected), reproduce the problem, check the simple things first (power, cables, restarts, logged-in account), form a hypothesis and test it, fix and verify with the user, then document the solution. Saying “I'd ask whether anyone else is affected” early is valuable — it separates an individual issue from an outage.
Common scenarios
| Scenario | Checks in order |
|---|---|
| No Wi-Fi | Other devices working? Airplane mode, correct network, forget and rejoin, IP address (self-assigned means no DHCP), drivers |
| Slow computer | Task Manager or Activity Monitor for CPU, memory, disk; start-up apps; disk space; updates; malware scan |
| Printer, one user | Default printer, print queue, driver, permissions, try another app |
| Can't log in | Caps Lock, account locked or expired, network to domain, time sync |
| Email not syncing | Internet, account status, mailbox size, re-add profile |
Security awareness
For a suspected phishing click: disconnect the device from the network if malware is possible, reset the user's password and revoke sessions, enable or verify multi-factor authentication, report to the security team, and scan the device. Thank the user for reporting — people who fear blame stop reporting. For password resets, always verify identity through an approved method before resetting; social engineering of help desks is a common attack.
Tickets, escalation and communication
- Prioritise by impact and urgency: an outage affecting many people beats a single user's cosmetic issue.
- Escalate when the issue exceeds your access or expertise, breaches a time threshold, or affects many users — with clear notes on what you've tried.
- Communicate in plain language, set expectations about timing, and update users before they have to chase you.
- Document fixes in the knowledge base so the next technician — or the user — can solve it faster.
Customer service questions
For “tell me about a difficult user”, describe staying calm, acknowledging their frustration, focusing on what you could do, and following up. Avoid stories that blame the user. Support is a service role, and interviewers weigh empathy as heavily as technical knowledge. See customer service interview questions.
Practising
The fastest way to find gaps is to be asked. Run a spoken mock round on IT support topics — a free AI interview assistant such as CoPilot Interview builds one from your résumé and the job description and scores every answer — then study whatever you stumbled on. Rehearse three scenario answers out loud using the troubleshooting method in order. See also system administrator interview questions.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly. Everything else on this page applies whichever tool you use, or none.
Frequently asked questions
What questions are asked in an IT support interview?
Troubleshooting method, common scenarios such as Wi-Fi, slow computers, printers and log-in issues, password resets, phishing response, DNS and DHCP basics, ticket prioritisation, escalation and customer service.
How do you answer “how do you troubleshoot a problem”?
Gather information, check whether others are affected, reproduce the issue, check simple causes first, test a hypothesis, fix and verify with the user, then document the solution.
What should you do if a user clicks a phishing link?
Isolate the device if needed, reset the password and revoke sessions, verify multi-factor authentication, report to security, scan the device and thank the user for reporting.
Do I need certifications for IT support jobs?
They help, especially entry-level certifications covering hardware, operating systems and networking, but interviews mostly test your troubleshooting approach and customer service.
Practise on real interview questions
Run 145 real interview questions across 10 tracks, answer out loud and see a structured answer to compare with yours. Free, no signup.
Try a practice question