While interviewing for many types of Tech jobs interviewers ask candidate various types of computer networking troubleshooting questions. There will direct questions with definitive answers, but interviewers will ask open-ended questions requiring prodding by the candidates to gain additional information. The latter category gives candidates the most trouble, and that’s the focus of today’s article. I’ll explain how to approach network troubleshooting questions as an experienced Tech professional who’s interviewed a number of candidates during my career.
Here’s Why Interviewers Like To Ask Broad Troubleshooting Questions
The main reason interviewers ask broad troubleshooting questions because it helps interviewers to learn about candidates’ thought process like so:
- Does the candidate ask follow-up questions to gather more information?
- Or is the candidate the type to take action with little information?
- Does the candidate move slow and methodical to resolve the issue?
- Or will the candidate’s nerves get the better of them?
All of this helps interviewers determine if candidates will benefit to the team or not. Thus, broad troubleshooting questions aid with hiring a good fit. Sometimes they also help interviewers take a chance on some candidates who need guidance to become a good technician.
Unfortunately, if candidates answers broad questions incorrectly, and doesn’t appear to be interested in learning, it’s a good sign that person wouldn’t be a good fit. Thus, interviewers will probably reject those individuals.
How To Approach Network Troubleshooting Questions
I’ll provide a generic and broad network troubleshooting question various types of Tech jobs would ask to measure candidates’ skill. Then I’ll break down my approach to answer it.
How Would You Fix A Computer That Wouldn’t Connect To The Network?
My first step is to take a moment and think about the question. I suggest every candidate to do that. Because I’ve seen too many people just start talking and not answer the question. Or they provide a shoddy answer. As for me: I repeat the question in my mind, and think about what the interviewer is really asking. Because questions like the one above have multiple layers and need careful inspection.
The second thing I would do is ask a series of questions because I need more information:
Scenario 1
- Me: Is this an end-user’s computer or a server?
- Interviewer: Hmm…let’s say this is an end-user’s computer.
- Me: Is it a desktop or a laptop?
- Interviewer: It’s a laptop?
The reason I ask those questions because troubleshooting a regular computer versus a server requires different steps. The former uses basic network components like a wireless Network Interface Card (NIC) instead of one or more high-bandwidth Ethernet or fiber NICs that servers use. I would also ask if the computer is a desktop or laptop because there’s different ways for those devices to connect to a network (Ethernet versus wireless).
- Me: Is the end-user trying to connect to the network in the office, or outside the office?
- Interviewer: In the office.
Again, I want to get more information about the location where this takes place. Troubleshooting public Wi-Fi will require more steps because many companies use Virtual Private Networks (VPNs) on their devices, and some public networks don’t interact well with VPNs.
Scenario 2
- Me: Does the end-user provide any type of error when trying to connect to the network?
- Interviewer: Yeah. He said he gets an error “Can’t connect to network.”
- Me: Which operating system is on the laptop?
- Interviewer: Windows. We use Windows 10 and 11 here.
- Me: I would check Device Manager to verify the NIC is present and has the proper drivers installed. If that’s all right then I would remove the Wi-Fi connection by forgetting the network and reconnect to it. It could be some configuration is incorrect.
The reason I ask those questions because I want to see if there’s an error when the end-user tries to connect to the network. That will help during the troubleshooting process. Finally, I want to show my knowledge about the particular operating system the employer uses. It doesn’t help my job offering prospects to use Linux commands if the employer only uses Windows.
Scenario 3
- Interviewer: Is there anything you would do outside of Windows to verify a network connection?
- Me: Do you mean physically?
- Interviewer: Yeah. What would you do?
- Me: Hmm…oh, some laptops feature a switch for their wireless NICs. I would check to see if the switch is turned off.
Interviewer like to change the troubleshooting process in the middle of their questioning at times. That can throw off candidates, but I believe interviewers want to see if candidates can bounce back.
Comments