IT intern interviews are about troubleshooting and service. Most IT internships, whether on a company help desk, in a school or hospital IT department or at a managed service provider, involve supporting users, setting up devices and accounts, and fixing everyday problems with networks, email and software. Expect scenario questions in which your method, and your manner with a frustrated user, count as much as the right answer. This page covers the rounds to expect, the questions that come up with what a strong answer contains, two sample answers, what interviewers expect from an intern, the mistakes that cost offers, and a two-week prep plan.
What the IT intern interview looks like
| Round | What happens | How to prepare |
|---|---|---|
| Screen | Résumé, coursework, any home lab or certifications, and availability | A one-minute story about fixing a tech problem for someone |
| Technical interview | Networking basics, Windows and account tasks, hardware, and troubleshooting scenarios | Practice explaining DNS, DHCP and IP addressing simply |
| Scenario or practical (some teams) | Role-play a support call or diagnose a staged problem on a laptop | Talk through each step aloud and confirm with the user |
| Team round | Customer service, teamwork, documentation and ticketing | One story about a difficult user and one about documenting a fix |
Questions that come up, and what strong answers contain
- A user says the internet isn't working. Walk me through it. Ask what exactly fails and since when, check whether others are affected, check the cable or Wi-Fi, run ipconfig to see whether the machine has a valid address, ping the gateway and then a public IP address, then test name resolution. Each step cuts the problem in half.
- What does it mean if a Windows PC has a 169.254.x.x address? It did not get an address from DHCP and assigned itself a link-local address, which Windows calls APIPA. Check the cable or Wi-Fi, the switch port and the DHCP server.
- Explain DNS and DHCP to someone non-technical. DNS is the phone book that turns names into addresses; DHCP is the front desk that hands each device an address when it joins the network, in a four-step exchange of discover, offer, request and acknowledge.
- A user is locked out of their account. What do you do? Verify the person's identity according to policy before anything else, then unlock or reset the account in Active Directory or the identity tool, find out why it locked (an old password saved on a phone is a frequent cause), and document the ticket.
- What is the difference between a hub, a switch and a router? A hub repeats traffic to every port; a switch forwards frames by MAC address within a network; a router forwards packets between networks by IP address.
- How do you prioritize when five tickets arrive at once? By impact and urgency: an outage affecting many people or a security issue first, then single users who cannot work, then requests. Tell each person when to expect help.
- Tell me about a time you helped someone who was frustrated with technology. Stay calm, avoid jargon, fix the immediate problem, then show them how to avoid it next time.
Two sample answers
A user says the internet isn't working.
I'd start by asking what they're trying to do and what they see, since 'the internet' can mean one website or nothing at all, and whether people nearby have the same problem. If it's only them, I'd check whether they're on Wi-Fi or a cable, then run ipconfig. A 169.254 address means the machine isn't getting an address from DHCP, so I'd reconnect the Wi-Fi or check the cable and port. With a proper address, I'd ping the gateway, then a public IP address, then a website by name. If the IP works but the name doesn't, it's DNS. I'd tell the user what I'm doing as I go and log the fix in the ticket.
Tell me about a frustrated user.
During my campus help desk job, a professor came in ten minutes before a lecture because her laptop wouldn't show on the projector. She was stressed, so I said I'd get her presenting first and explain afterwards. Pressing Windows and P to switch the display to duplicate fixed it, and I walked with her to the room to check it worked there. Later I emailed her a one-line note about the shortcut. She started sending colleagues to us, which my supervisor noticed.
What interviewers expect from an intern
- A methodical troubleshooting approach: gather information, isolate, test, fix and document.
- Networking and operating-system basics; our computer networks interview questions cover the fundamentals.
- Patience and clear communication with non-technical users.
- Curiosity shown by a home lab, a PC you built, a certification in progress or a campus IT job.
For the full-time version of these questions, see IT support interview questions.
Mistakes that cost offers
- Jumping to a reinstall before diagnosing.
- Skipping identity verification in an account-reset scenario.
- Using jargon with the user in a role-play.
- Not documenting: an undocumented fix has to be rediscovered by the next person.
A two-week prep plan
- Days 1 to 3: networking basics: IP addressing and subnets, DNS, DHCP, gateways, and the commands ipconfig, ping, tracert and nslookup.
- Days 4 to 5: Windows and accounts: users and groups, Active Directory concepts, permissions, and common email and Office problems.
- Days 6 to 8: build a small home lab: a virtual machine, a shared folder with permissions, and a deliberate network fault to diagnose.
- Days 9 to 10: troubleshooting scenarios out loud: no internet, a printer that won't print, a slow PC and a locked account.
- Days 11 to 14: customer-service stories, ticket-writing practice and two mock interviews; for infrastructure-heavy roles, also read our cloud engineering intern interview questions.
Timing matters as much as preparation: see our internship recruiting timeline, and once you are in, turning an internship into a return offer. Before the last round, prepare your questions to ask at the end of an intern interview.
Where CoPilot Interview fits
Intern interviews reward clear explanations of your own projects and coursework, and that takes practice out loud. CoPilot Interview is an AI interview assistant; its free AI mock interview builds IT intern questions from your résumé and the job description, reads them aloud, scores each spoken answer out of ten and shows a model answer to compare. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included, with no card, which suits a student budget. For real interviews and online assessments, follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Do I need CompTIA A+ for an IT internship?
It helps but is rarely required. CompTIA recommends about 12 months of hands-on support experience for A+, and its Core 1 exam (220-1201) has up to 90 questions in 90 minutes, as its site described on November 12, 2026, so many students take it during or after an internship. A home lab and a campus IT job are just as persuasive.
What does an IT intern actually do?
Commonly: answering help desk tickets, setting up laptops and accounts, imaging machines, tracking hardware, documenting fixes and helping with projects such as device rollouts.
Is an IT internship the same as a software engineering internship?
No. IT internships support people and systems, with troubleshooting, networking and service at the centre; software engineering internships build products and are judged in coding interviews. Our <a href="/blog/software-engineer-intern-interview-questions">software engineer intern interview questions</a> cover the second.
Can I use AI tools during an internship interview?
Only where the instructions allow it. Online assessments and many live rounds forbid outside help. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview