IT support....day to day tasks?

This question is for people with experience working in an IT support role...

I have an interview for an IT support position next week, its a second interview and in the first they said a second interview would involve a practicle test "for example we give you a laptop with a fault and see how you fix it."

Any ideas what they are likely to throw at me?

I'm guessing it will be a common problem, that I would be expected to do regulary in the position.

 

lol:-D Could be any thing Good luck,

 

IT will probably be along the lines of somethings not working due to a service being stopped or no internet due to a static IP setting or proxy setting in IE, or the PC can't see the domain due to it being a "workstation" and not joined, in other words, common stuff

 

It could be something like: "Find and install the drivers for this noname brand (custom built) computer"

Good luck. Shouldn't be something too difficult. They mostly just want to see your troubleshooting methods.

 

OH, that could be evil fun. :-D Probably an uninstalled driver, lost network, boot issue... Just look at the problem, and remember, it is usually something simple. (I tend to overthink problems, and wind up chasing my tail until I look at it simply.)

Good luck, and let us know what they throw at you!

 

Like Fred said plug it in,turn the wall socket on,work from the socket to the laptop.

Questions are good,does the laptop have important data this question would determine whether I removed the hard drive in the first place to create backups or attempt to repair the unit as a whole and they will want to know you grasp this,if they don't ask them if you should assume backups have been created and continue the exercise.

Availability of compatible spare parts,if the computer doesn't turn on the first thing I want on my hand is a few known working sticks of memory.

Tools,I would imagine you'd have to take all your own software tools with you on a flash drive "I would" stability and diagnosis checks so I guess they be impressed with what you bring with you,I'd also turn up with my own tools such a multimeter,psu tester ect.

You may wish to ask them if everything will be provided to fix the problem before hand,if it is a software problem and they want you to use their own tools and your not familiar with them your screwed so it would be wise IMO to make sure you have your own as a backup.

Maybe I'm over thinking it I'm sure it will be something pretty simple like a driver install.

Good luck!

 

Y'all are thinking as "PC enthusiasts", not what it's like in a corporate environment. Mostly connectivity to the network, network share access & printing as well as support for Office/Productivity software and such. Don't remember ever having to troubleshoot a driver issue in a test interview.

 

One other thing they might be looking at it your ability to tactfully deal with co-workers (users) who have limited skills or are basically computer illiterate.

Keep explanations of issues on-point and polite. Statements like "I can't believe some moron messed this up" (or worse) will work against you. No matter how stupid a problem (or user) is, bite your tongue and keep such thoughts to yourself.

FYI, I have worked with IT people in the past who's attitude and language would have made Chef Gordon ("Hell's Kitchen") Ramsay blush. HR departments don't like this type of thing; having a good game face may go a long way in getting the job.

Good luck on the interview.

 

I think Serious Sam is on the right track with the "corporate" view. I know most of my issues in a multi-pc, multi-employee environment are connectivity related.

Those that espouse patience when dealing with the uninitiated are also spot on . . . it's very easy to get frustrated with someone for not understanding something that, to you, seems very simple. The old saw "It's easy when you know how" fits this concept.

You can lead a mind to knowledge, but you cannot make it think . . . also never forget you can explain things to someone till you are blue in the face, but you can't understand it for them . . .