1. Tell me about yourself and why you want to be an IT Assistant.

Sample Answer: "I have always been the person friends and family call when their Wi-Fi stops working or their laptop won't start. That curiosity led me to study information technology, and I later gained hands-on experience setting up hardware and resolving basic software issues during an internship. I enjoy the mix of technical problem-solving and helping people directly, which is why an IT Assistant role feels like a natural fit for me."

Why they ask: Interviewers want a concise story that connects your background to the role, not a full resume recap.

2. What interests you about working in IT support specifically?

Sample Answer: "I like that every ticket is a small puzzle. One moment I might be reinstalling a printer driver, and the next I'm helping someone recover a file they thought was lost. I find satisfaction in that variety, and I also enjoy the immediate feedback of seeing someone's problem solved right in front of me."

3. What are your strengths as they relate to this position?

Sample Answer: "My biggest strength is patience combined with clear communication. I can explain technical steps in plain language so users don't feel overwhelmed. I'm also very organized when it comes to documenting issues, which helps the wider IT team spot recurring problems."

4. What is your biggest weakness?

Sample Answer: "Early in my career, I sometimes spent too long trying to solve a problem on my own before asking for help. I've since learned to set a time limit for myself — usually fifteen to twenty minutes — before looping in a senior technician, which keeps tickets moving without sacrificing my own learning."

Why they ask: They want to see self-awareness and a growth mindset, not a rehearsed non-answer like "I work too hard."

5. Why should we hire you over other candidates?

Sample Answer: "I bring a combination of solid technical fundamentals and genuine care for the end user's experience. I don't just close tickets — I try to understand the root cause so the same issue doesn't keep coming back. That mindset saves time for both the IT team and the employees we support."

6. How would you troubleshoot a computer that won't turn on?

Sample Answer: "First, I'd check the obvious things — is it plugged in, is the power strip switched on, and is the power cable firmly connected on both ends. Next, I'd check the monitor separately from the tower to rule out a display issue rather than a power issue. If there's still no response, I'd test with a different power cable or outlet, and if the problem persists, I would escalate for hardware diagnostics."

7. What steps would you take if an employee says their internet is not working?

Sample Answer: "I would start by asking if the issue affects just their device or the whole office, since that tells me whether it's a local or network-wide problem. Then I'd check the physical cable connection or Wi-Fi status, restart the router or modem if needed, and run a quick ping test to confirm connectivity. If it's isolated to one machine, I would check network adapter settings and driver status."

8. Can you explain the difference between an IP address and a MAC address?

Sample Answer: "An IP address is a logical address assigned to a device on a network, and it can change depending on the network you connect to. A MAC address is a physical, hardware-based identifier burned into the network interface card, and it stays the same regardless of which network you're on."

9. How do you reset a user's password securely?

Sample Answer: "I would first verify the user's identity through an approved method, such as confirming employee ID or using a callback to their registered number. Then I would reset the password through the system, such as Active Directory, and set it to expire immediately so the user must create a new one on their next login."

Why they ask: Security-conscious behavior matters even for simple tasks like password resets.

10. What would you do if a computer is running very slowly?

Sample Answer: "I would check the Task Manager to see if any application is using excessive CPU, memory, or disk resources. I would also check available storage space, since a nearly full hard drive can slow performance significantly. If malware is suspected, I'd run a security scan, and I would check for pending updates that might be consuming resources in the background."

11. What is the difference between a hub, a switch, and a router?

Sample Answer: "A hub simply broadcasts data to every device connected to it, which is inefficient. A switch is smarter — it sends data only to the specific device it's intended for based on MAC addresses. A router connects different networks together, such as your local network to the internet, and manages traffic between them using IP addresses."

12. How comfortable are you with setting up new hardware for employees?

Sample Answer: "Very comfortable. I've set up laptops, docking stations, and multiple monitors for new hires, including installing standard software packages, configuring email accounts, and making sure printers and shared drives are mapped correctly before the employee's first day."

13. What ticketing systems or helpdesk software have you used?

Sample Answer: "I've worked with Zendesk for logging and tracking support requests, and I'm also familiar with Jira Service Desk for larger organizations. I understand the importance of accurate categorization and clear notes, since that documentation helps the whole team spot patterns over time."

14. A user calls saying their printer isn't working. Walk me through how you'd handle it.

Sample Answer: "I'd start by asking what exactly happens — is there an error message, or does nothing print at all. I'd check whether the printer is powered on and connected to the network, confirm there's paper and toner, and check the print queue for stuck jobs. If the queue is jammed, I would clear it and restart the print spooler service. If the issue continues, I'd check whether other users can print to the same device to isolate whether it's a printer problem or a specific computer problem."

15. How would you handle multiple urgent tickets at the same time?

Sample Answer: "I would prioritize based on business impact. For example, an entire department losing network access takes priority over a single user's minor software glitch. I'd communicate realistic timeframes to each person so they know they haven't been forgotten, and I'd document everything as I go so nothing slips through the cracks."

16. What would you do if you didn't know how to fix a problem?

Sample Answer: "I would be honest with the user that I need to investigate further rather than guessing. I'd search internal documentation or knowledge base articles first, and if I still couldn't resolve it within a reasonable time, I would escalate to a senior technician while keeping the user informed of the next steps."

Why they ask: Nobody expects an entry-level assistant to know everything. They want honesty and a clear escalation process.

17. Describe a time you resolved a difficult technical issue.

Sample Answer: "A user reported that their email kept crashing every time they opened a specific attachment. I discovered the file was corrupted during a previous sync error. I restored a clean copy from the backup server and also identified that the sync issue was affecting two other users, which let me fix the root cause before more tickets came in."

18. How do you handle a situation where you made a mistake that affected a user's work?

Sample Answer: "I take ownership immediately rather than deflecting. I'd inform the user and my supervisor as soon as I noticed the error, explain what happened in plain terms, and focus on fixing it quickly. Afterward, I would think about what process change could prevent the same mistake in the future."

19. If a user's laptop was infected with malware, what would your first three steps be?

Sample Answer: "First, I would disconnect the device from the network to prevent the malware from spreading. Second, I would run a full antivirus and anti-malware scan to identify and quarantine the threat. Third, I would check whether any sensitive data may have been exposed and report the incident according to company security policy."

20. How do you explain technical issues to someone who isn't tech-savvy?

Sample Answer: "I avoid jargon and use everyday comparisons instead. For example, instead of saying 'your DNS cache is corrupted,' I might say 'your computer's address book for websites got mixed up, so I'm going to clear it and let it rebuild.' I also check in with simple questions like 'does that make sense so far?' to make sure I'm not losing them."

21. Describe a time you dealt with a frustrated or upset user.

Sample Answer: "A user was upset because they had lost unsaved work after a forced update. I let them vent for a moment without interrupting, then calmly explained what happened and what I could do to help recover any autosaved versions. By staying calm and focused on solutions rather than excuses, the conversation ended on a much better note than it started."

22. How do you stay organized when handling many tickets a day?

Sample Answer: "I rely heavily on the ticketing system to track status, priority, and due dates rather than trying to remember everything mentally. I also block small chunks of time for documentation so notes stay accurate, and I review my open ticket list at the start and end of each day."

23. How do you handle repetitive tasks without losing focus or making errors?

Sample Answer: "I create simple checklists for recurring tasks, like new employee setups, so I don't skip a step even when I'm doing the tenth one that week. Checklists also make it easier to train someone else or hand off a task if needed."

24. Tell me about a time you had to learn a new tool or system quickly.

Sample Answer: "When my previous employer switched ticketing platforms, I spent an evening going through the vendor's documentation and watched a few tutorial videos so I could hit the ground running on day one instead of slowing down my team while everyone adjusted."

25. How do you handle working under pressure or tight deadlines?

Sample Answer: "I break the problem into smaller, manageable steps rather than getting overwhelmed by the whole situation at once. I also communicate proactively if something is going to take longer than expected, since surprises tend to create more stress than a heads-up would."

26. How would you handle a user who keeps making the same mistake repeatedly?

Sample Answer: "I would patiently walk them through the correct process again, but this time I'd also create a short written guide or screenshot they can reference on their own next time, so they build confidence instead of relying on IT for something simple."

27. What would you do if you disagreed with a decision made by your supervisor?

Sample Answer: "I would raise my concern respectfully and privately, explaining my reasoning with specific examples. If my supervisor still decided to move forward with their original approach, I would support the decision professionally, since I trust that they often have context I might not be aware of."

28. How do you make sure users feel heard, even when you can't fix their issue immediately?

Sample Answer: "I acknowledge the impact the issue is having on their work before jumping into troubleshooting. Something as simple as 'I understand this is slowing down your morning, let's get it sorted' helps users feel like a person is listening, not just a script."

29. Describe your approach to documenting a support ticket.

Sample Answer: "I document the reported issue in the user's own words, the steps I took to troubleshoot, the outcome, and any follow-up needed. Clear documentation means anyone on the team can pick up the ticket later without having to start from scratch."

Overusing technical jargon

Some candidates try to impress interviewers with complex terminology, but this can backfire if it isn't explained clearly. Interviewers are often evaluating communication just as much as technical accuracy.

Failing to ask clarifying questions

In scenario-based questions, jumping straight to a solution without asking what the actual symptoms are can make you seem like you troubleshoot by guessing rather than by process.

Not showing enthusiasm for helping people

IT Assistant roles are people-facing. Candidates who only talk about machines and never mention the human side of the job can come across as a weaker cultural fit.

30. How would you handle a situation where a senior employee demands you skip standard security verification steps?

Sample Answer: "I would remain polite but firm. Security procedures exist to protect everyone, including that employee, so I'd explain that I need to follow the same verification process regardless of seniority. If they push back further, I'd involve my supervisor rather than bending the policy on my own."

Why they ask: This question checks whether you can hold a professional boundary under social pressure, which is critical for protecting company data.

31. A user reports that a file they need urgently has disappeared. What do you do?

Sample Answer: "First, I'd ask exactly where the file was saved and when they last saw it, since sometimes it's simply been moved or renamed. I'd check the recycle bin, recent files list, and any cloud sync history. If it's truly missing, I'd check backup systems for a recent snapshot, and I would keep the user updated throughout so they aren't left wondering."

32. How would you handle onboarding ten new employees on the same day?

Sample Answer: "I would prepare in advance by pre-configuring as much as possible — accounts, software images, and hardware — the day before. I'd create a simple checklist for each workstation so nothing gets missed under time pressure, and I would ask a colleague for support if the volume was too much for one person to handle smoothly."

33. What would you do if you noticed a security vulnerability that wasn't part of your assigned task?

Sample Answer: "I would report it immediately to my supervisor or the security team rather than ignoring it because it wasn't officially my responsibility. Even small oversights, like an unlocked server room door or a shared password written on a sticky note, can lead to serious issues if left unaddressed."

34. How do you decide when a problem needs to be escalated versus handled yourself?

Sample Answer: "I consider three things: whether the issue is within my access level, whether it requires specialized knowledge I don't yet have, and how much business impact continued delay would cause. If any of those point toward risk, I escalate quickly rather than trying to be a hero and wasting valuable time."

35. Have you used remote desktop tools to support employees working from home?

Sample Answer: "Yes, I've used remote support tools to view a user's screen and walk them through fixes without needing to be physically present. I always ask for permission before connecting and explain what I'm doing on their screen so they feel comfortable throughout the session."

36. What experience do you have with Windows and Mac operating systems?

Sample Answer: "I'm comfortable supporting both. On Windows, I'm familiar with tools like Control Panel, Event Viewer, and basic PowerShell commands. On Mac, I understand system preferences, Keychain access issues, and basic Terminal commands, though I'd say my strongest experience is on the Windows side."

37. How would you assist a remote employee who cannot connect to the company VPN?

Sample Answer: "I'd first confirm their internet connection is working outside of the VPN, then check their VPN client for error messages. Common fixes include restarting the client, checking for expired credentials, or reinstalling the VPN software if a configuration file has become corrupted. If the issue persists, I'd check with the network team for any known outages."

38. Are you familiar with basic cloud platforms like Microsoft 365 or Google Workspace?

Sample Answer: "Yes, I've helped manage user licenses, shared mailboxes, and basic permission settings in Microsoft 365, along with troubleshooting sync issues with OneDrive. I'm comfortable learning Google Workspace equivalents quickly since the core concepts of user and file management are similar."