IT Support Associate – Interview Prep

Common technical and behavioral questions for entry/mid-level corporate IT support roles, with sample answers.

Technical Questions

Q: What is the OSI model?

A 7-layer framework describing how data travels across a network – from physical cables (Layer 1) up to the application (Layer 7). It helps structure troubleshooting from the bottom up.

Q: What’s the difference between TCP and UDP?

TCP is connection-based and reliable (used for web browsing, email). UDP is faster but doesn’t guarantee delivery (used for streaming, gaming).

Q: A user says “I have no internet” – what do you check first?

Physical connection (cable/WiFi), then run ipconfig to check for a valid IP address. If it’s a 169.254.x.x address, that’s a DHCP failure. Then test ping to the gateway, then to an external site.

Q: What is DHCP and why does it matter?

DHCP automatically assigns IP addresses and network settings to devices. Without it, every device would need manual IP configuration – error-prone at scale.

Q: What is Active Directory used for?

Centralized management of users, computers, and permissions in a Windows domain. Most account/access issues are resolved by checking AD – account lockouts, group membership, expired passwords.

Q: How would you troubleshoot a printer that won’t print?

Check it’s powered on and connected, restart the print spooler service, try removing/re-adding the printer, and check/update drivers.

Q: What’s the difference between a switch and a router?

A switch connects devices within the same local network (Layer 2). A router connects different networks together and directs traffic between them (Layer 3).

Q: How do you prioritize multiple tickets at once?

Based on urgency/impact – e.g., a full department outage takes priority over a single user’s minor issue. Communicate expected timelines to affected users.

Behavioral Questions (STAR Method) – Worked Examples

STAR = Situation, Task, Action, Result. Below are real example answers built from common IT support scenarios – use these as templates and swap in your own details.

Q: Tell me about a time you dealt with a difficult or urgent situation.

Situation: “A manager called me, very stressed, because their laptop screen went black 10 minutes before an important client presentation.”
Task: “I needed to quickly diagnose a hardware issue remotely and either fix it fast or get them a backup solution before their meeting.”
Action: “I stayed calm and asked them to hold the power button for 5-10 seconds to force a restart, then plug in the charger and try again. While they did this, I checked their device status and AD profile remotely to rule out a software/account issue. When the screen stayed black, I immediately escalated to the onsite team and opened a ticket with full documentation.”
Result: “This gave the user a fast initial fix attempt while in parallel getting hands-on help moving quickly, minimizing disruption to their presentation.”

Q: Tell me about a time you made a mistake and how you handled it.

Situation: “I once gave a user incorrect information about how to resolve their issue.”
Task: “Once I realized my mistake, I needed to correct it quickly before it caused further confusion.”
Action: “I first informed my team lead about the mistake, then called the user back directly, apologized for the confusion, and gave them the correct information with clear steps to follow.”
Result: “The user appreciated the quick correction and follow-up, and the issue was resolved properly without further delay.”

Q: Tell me about a time you had to investigate a problem with limited information.

Situation: “A user called saying she couldn’t log in, but only gave me her name – not her username – and was in a hurry.”
Task: “I needed to verify and resolve her account issue without enough identifying information, especially since her surname matched several employees.”
Action: “I checked the account using just her name and confirmed it wasn’t blocked, but she dropped the call before I could clarify further. I opened a ticket, investigated further, and found multiple users with the same surname. I tried calling her back; when she didn’t answer, I informed my team lead and continued trying to reach her, planning to verify her identity via company email if needed.”
Result: “I didn’t just give up after the first call dropped – I escalated transparently to my team lead and kept investigating systematically to resolve it securely.”

STAR Tip

When asked “tell me about a time…”, interviewers want ONE specific real story, not a general process description. If you find yourself saying “I would…” instead of “I did…”, pause and think of an actual example from your work experience.

Questions to Ask the Interviewer

• What does a typical day look like for this role?
• What ticketing system and tools does the team use day-to-day?
• How is the team structured (L1/L2/L3 escalation)?
• What opportunities are there for learning/certifications?