Tech questions

[BuLkHoGaN]

I am about ready to hire another tech and want to be sure they are knowledgable like there resume' will say they are

Wanted to put a little test together with about 20 or so questions to see if they know there stuff.

I dont want to use A+ BS questions either. I want to use stuff that pertains to working on computers now. I always ask in the interview if they know what msconfig is. That is one good indicator for me. Any others would be helpful. Thanks

Jamie

[MacGyver]

Ask what their troubleshooting methodogy is. They should start with "check everything is plugged in and has power" or something similar. If they say "reinstall Windows" too quickly, they probably don't know their stuff.

This will give you a good idea of their skills as a tech.

[Radical Dreamer]

A good indication of what they know is asking them what acronyms, that way you know that they arent just trying to use "buzz words" like see if the know that IDE is integrated drive electronics or that SCSI is small computers system interface.

[NeuromancerIV]

Mac really hit it there: METHODOLOGY

I'd give them speific trouble shooting scenarios, a persons methodology of trouble shooting can be as important as their base of knowledge.
stuff like

1. Tell them a box cant read its floppy drive *reverse a floppy drive cable on the box and have the prospect TS it.*

2. Tell them the modem stopped working *Mess up the com port settings in the bios*

3. Tell them the CD-RW drive won't come up *in correctly jumper the drive/leave the ide cable of*

4. Tell them the comp won't boot *leave floppy in drive*

5. Tell them to diagnose the POST beep coded *unseat memory, agp card, etc

I like to see them working. Its not as much about how long it takes to fix, as much as what do they try 1st..and last. 'Cause anyone can memorize the "right answers" to tech questions, but to see them with hands-on..then you get (IMHO) a more true feel for their skill level.

As far as specific written questions? Well that needs to be tailored to the position they want, bench tech, network tech, cabling tech etc or any combo thereof. Heck HW questions are easy, I'd have to put a bit more thought into specific SW/OS questions though...

[Stalemate]

If they get NeuromancerIV's #4 question wrong, or spend too much time on it, I'd consider them unfit.

How about asking them to list every software that starts automatically on a given PC? They'll think of the obvious (Startup menu, msconfig), but may miss registry entries or network login scripts. That would be a good question in my mind to see if a tech has a good grasp of where progs could be disabled for troubleshooting purposes.

[DANIMAL]

Put the klez virus on the system and give them a kinked telephone wire and a 28.8 modem, 10 blank cd's (only one having the drivers)and an old version or norton antivirus, hide the power cord in your repair room and give him 20 min to fix the system. <img border="0" title="" alt="[Wink]" src="wink.gif" />

LOL

[Gabriel]

Let them play on BIOS Settings, Dos Commands, Printer and Port Settings.
All the hardware stuff - the hardware is the most important part.

[Ruslan]

Like Mac,I would also ask for methodology of troubleshooting.
Ask him a lot of questions like "what would You do in case "xxxx device" is not working". What would You check first & why?
Also few questions about typical OS/HW problems like BSODs,crashes,network problems and so on.
Then probably give him few real examples for fixing (cables connected vise-versa,BNC network without one terminator connected,wrong UTP cable type,HDD with deleted command.com,msdos.sys,lost/deleted drivers etc).
And of course, a lot of things You will know later about his abilities in real everyday work...

[silencio]

Having dealt with a number of creative "dumbasses" for lack of a better work, tell one of these guys that you have a problem with one of the servers and you think that the problem is in one of the banks on the 6 gig of ram (in the machine/OS) that will only take 2 gig of ram.

It's a quick way to eliminate... people.

P.S. Make sure the box doesn't actually take 6 gig of ram.

[kingtbone]

Yeah, I think usually a practical test is the best way to go about it. I know from experience that it can be easy to BS people about certain things. You should get them to try to fix some actual problems in the shop or wherever you work.

[BuLkHoGaN]

I think that is what I will do Is have a pc here with a few of the problems listed here to see how he goes about fixing it. I would like to find someone who's answer to every window blue screen is not " hardware is bad" or "needs to be formatted" I hope I can find someone that knows how to use the internet to find answers. So many techs dont use the best tool given to them, the net. I have consistantly gone behind a tech before he switched a part or formatted a drive and found a fix on the net that didnt involve a format or a part change.

I'll bring the applicants in today and let you know how it goes.

Thanks for the help

Jamie

[EvilCabbage]

Heh, could always offer me a job

Willing to travel, and Im damn good looking too. Heh.

[Fubar]

Methodology is the key. A good tech will ask enough of the right kind of questions before trying to fix a problem. He/She will also be able to ask a question several different ways. A good tech will also be able to break down a multi-faceted problem into its componants and work on them one by one and not just try to fix "everything at once." People skills are also important for a tech. Make sure your candidates can just chat. Putting users/customers at ease is a plus. And look for someone you can work with and have a good working relationship with.

Good luck!

[Visgothy]

I know taht the test is already done but...
A good thing to do also is to have someone to call with a problem. Phone troubleshooting with users is not given to every one. One easy and not long to make is to remove the association of certain files like Excel file's or word file and say that Word does not work anymore....

have fun!

[cisco2]

Hire the right people. Teach them what you need them to know. Many times I've seen the right people become great techs despite a thin resume. Conversely I've seen many people with impressive qualifications ruin a once productive group.
People with good work habits and people skills can be taught the skills you need them to have. With surprising speed. Difficult people are always going to be difficult people regardless of their background or existing skills. Do yourself a favor and interview people skills. Judge the person, try to figure out what their work habits, work ethic, and people skills are. Once you've narrowed it down, find a way to get a peek at their car. Lazy slobs have trash filled vehicles. Most good people are going to have a reliable ride that looks comfortable, a bit used with a small amount of functional clutter. People with spotless cars are hard to judge, might be good people, might be rigid perfectionists. I learned the previous bit from a friend who rents homes, he always gets a look at a prospective tenant's car before renting to them.