During a job interview for many types of Tech jobs the interviewer asks the candidate various types of computer hardware troubleshooting questions. Some will be direct, while others will be broad. It’s the latter category which causes candidates the most trouble, but the direct questions can be difficult too. This article explains how to approach computer hardware troubleshooting questions from an experienced Tech professional who’s interviewed a number of candidates during my career.
First, Allow Me Explain Why Interviewers Like To Ask Broad Troubleshooting Questions
The main reason an interviewer like to ask broad troubleshooting questions because it helps the interviewer to learn about the candidate’s thought process:
- Does the candidate ask follow-up questions?
- Is the candidate impulsive and rushes into action? Or is the candidate slow and methodical?
- Does the candidate get nervous and freeze up? Or does the candidate fight off the nervousness and pushes ahead?
The way a candidate approaches a problem helps the interviewer determine if that person will be a benefit to the team, or a potential problem. Thus, these broad questions can help the interviewer hire a good fit, or take a chance on an individual that needs guidance and mentorship to become a good technician.
Unfortunately, if a candidate answers broad questions incorrectly, and doesn’t appear to be interested in learning, it’s a good sign that person would hurt the team. Thus, the interviewer will reject that person.
How To Approach Computer Hardware Troubleshooting Questions
I’m going to provide a generic and broad computer hardware troubleshooting question various types of Tech jobs would ask to gauge a candidate’s skill. Then I will break down how I would approach answering it.
How Would You Find A Defective Hard Drive In A Computer?
The first thing I would do is take a moment and think about the question. I’ve seen too many candidates just launch into talking. That’s the wrong process. I take a few seconds, repeat the question in my mind, and think about what the interviewer is really asking. Because some questions may have layers. Thus, I need to read in-between the lines.
The second thing I would do is ask a series of questions because I need more information:
Scenario 1
- Me: Is there an error on the computer stating there is a missing or bad hard drive?
- Interviewer: Yes.
The reason I ask that question because I want to see if there is an error or not. The answer I get determines my troubleshooting process. If there is an error, great! I can get more information. If there isn’t, then I need to readjust my troubleshooting steps.
- Me: Where does that message appear?
- Interviewer: During POST.
With the message appearing during the Power-On Self Test (POST) I know the computer detects the missing hard drive early on during the boot process. Thus, I can focus my answer on that part of the machine.
Scenario 2
- Me: Is there an error on the computer stating there is a missing or bad hard drive?
- Interviewer: Yeah. It shows up after the operating system boots up.
- Me: Which operating system does the computer use?
- Interviewer: Pick the one you’re most familiar with.
- Me: Which type of operating system does this company use the most?
- Interviewer: We use Windows.
The reason I ask those questions because I want to tailor my answer to showcase the skill-set the employer needs the most. If the company uses primarily Windows, and I start troubleshooting using Linux commands the interviewer will probably not understand what I’m doing. However, if the company uses many types of operating systems on their computers (which is reasonable nowadays), then choosing the operating system I’m strongest in gives me the best chance at a successful answer.
Finally, I like to form my answer around the operating system the employer uses the most. This way the interviewer sees my knowledge and experience in action. Hence, I set myself up for a successful interview and a possible job offer.
Scenario 3
- Interviewer: Is there anything you would do outside of software to find a defective hard drive?
- Me: Do you mean physically?
- Interviewer: Yeah. What would you do?
Again, I would take a moment and collect my thoughts. Because now the interviewer changed tactics and wants to change the troubleshooting process. Here’s how to approach computer hardware troubleshooting questions like that:
- Me: Do I have physical access to the computer?
- Interviewer: Yes.
- Me: Great! Then I would open the computer and verify the connections to the hard drive. For a PATA or SSD hard drive I would make sure the SATA connections are plugged in properly in the device and on the motherboard. For a M.2 drive, I would make sure it’s seated in the slot properly. That’s what I would do.
Comments