interview help - I.T Helpdesk
Bit of help here, I have an interview coming up for a I.T Helpdesk role, just wondering if anyone could give me any tips, questions they might ask etc….
Haven’t had one in years so I am quite nervous to say the least! lol
Haven’t had one in years so I am quite nervous to say the least! lol
As long as you know where CTRL, ALT and Delete are, you'll be fine. 
Might be worth asking what platforms they have (Mac, Windows, Unix, etc), if the opportunity arises to show you're interested in learning about their infrastructure. Say if you have experience in the bits you know, keep schtum about the bits you don't. If you're not well versed in Mac OS X, for example, don't mention it unless you're asked. If you are asked about it, say that you've not used one since xyz, but you're sure it'll be easy to pick up. Shows confidence in your ability to learn something new, and that you're aware of new developments, even though you're not as up to date as you could be.
Is is first or second line support? I sadly do both. I AM the helpdesk.
Puts a real gripper on when you're concentrating on something important!
Just remember never take the user's word on what they say the problem is - always investigate for yourself.
Always ask the stupid questions first - "Is Caps Lock on?" solves 99% of password problems.
Always get them to check while you're on the phone - a problem might have occured half an hour ago but they've been to busy/bone-idle to report it and by now it's not a problem any more.
You'll probably only be asked to cover what's on your CV and past experience, maybe go through some hypothetical situations. As each business and it's IT infrastructure is different, you'll only really get quizzed on 'general knowledge' and generally accepted sound practice, ie backup before cockup.
Never say "I don't know". It's always a bad answer, whether in the interview or on the job. "I'll find out and get back to you" makes you sound less ignorant - won't work in the interview though
so ask to clarify what they're asking if you don't understand.
Don't be intimidated by the questioning, and don't scratch your ear or your nose - its a sign you don't believe what you're hearing or saying. Don't blabber - keep your answers to the point, and expand 'generally' - "This one time, at band camp..." won't do you any favours.
Make sure you learn about the company before you go in - remember that episode of the Apprentice where someone was asked "Do you know what Amstrad do?" and they said "No"?
Might be worth asking what platforms they have (Mac, Windows, Unix, etc), if the opportunity arises to show you're interested in learning about their infrastructure. Say if you have experience in the bits you know, keep schtum about the bits you don't. If you're not well versed in Mac OS X, for example, don't mention it unless you're asked. If you are asked about it, say that you've not used one since xyz, but you're sure it'll be easy to pick up. Shows confidence in your ability to learn something new, and that you're aware of new developments, even though you're not as up to date as you could be.
Is is first or second line support? I sadly do both. I AM the helpdesk.
Puts a real gripper on when you're concentrating on something important!Just remember never take the user's word on what they say the problem is - always investigate for yourself.
Always ask the stupid questions first - "Is Caps Lock on?" solves 99% of password problems.

Always get them to check while you're on the phone - a problem might have occured half an hour ago but they've been to busy/bone-idle to report it and by now it's not a problem any more.
You'll probably only be asked to cover what's on your CV and past experience, maybe go through some hypothetical situations. As each business and it's IT infrastructure is different, you'll only really get quizzed on 'general knowledge' and generally accepted sound practice, ie backup before cockup.
Never say "I don't know". It's always a bad answer, whether in the interview or on the job. "I'll find out and get back to you" makes you sound less ignorant - won't work in the interview though
so ask to clarify what they're asking if you don't understand.Don't be intimidated by the questioning, and don't scratch your ear or your nose - its a sign you don't believe what you're hearing or saying. Don't blabber - keep your answers to the point, and expand 'generally' - "This one time, at band camp..." won't do you any favours.
Make sure you learn about the company before you go in - remember that episode of the Apprentice where someone was asked "Do you know what Amstrad do?" and they said "No"?
Last edited by cozmeister; Apr 3, 2009 at 02:50 PM.
Trending Topics
Wohoo must be that time of year ( well it is actually! ) but I started looking for a new job, put the feelers out two weeks ago and have three interviews lined up for next week!
Fingers crossed one of them is the right position for me
Good luck to the OP as well and make sure you take note of Cozzmeisters post, some good advice there
Fingers crossed one of them is the right position for me
As long as you know where CTRL, ALT and Delete are, you'll be fine. 
Might be worth asking what platforms they have (Mac, Windows, Unix, etc), if the opportunity arises to show you're interested in learning about their infrastructure. Say if you have experience in the bits you know, keep schtum about the bits you don't. If you're not well versed in Mac OS X, for example, don't mention it unless you're asked. If you are asked about it, say that you've not used one since xyz, but you're sure it'll be easy to pick up. Shows confidence in your ability to learn something new, and that you're aware of new developments, even though you're not as up to date as you could be.
Is is first or second line support? I sadly do both. I AM the helpdesk.
Puts a real gripper on when you're concentrating on something important!
Just remember never take the user's word on what they say the problem is - always investigate for yourself.
Always ask the stupid questions first - "Is Caps Lock on?" solves 99% of password problems.
Always get them to check while you're on the phone - a problem might have occured half an hour ago but they've been to busy/bone-idle to report it and by now it's not a problem any more.
You'll probably only be asked to cover what's on your CV and past experience, maybe go through some hypothetical situations. As each business and it's IT infrastructure is different, you'll only really get quizzed on 'general knowledge' and generally accepted sound practice, ie backup before cockup.
Never say "I don't know". It's always a bad answer, whether in the interview or on the job. "I'll find out and get back to you" makes you sound less ignorant - won't work in the interview though
so ask to clarify what they're asking if you don't understand.
Don't be intimidated by the questioning, and don't scratch your ear or your nose - its a sign you don't believe what you're hearing or saying. Don't blabber - keep your answers to the point, and expand 'generally' - "This one time, at band camp..." won't do you any favours.
Make sure you learn about the company before you go in - remember that episode of the Apprentice where someone was asked "Do you know what Amstrad do?" and they said "No"?
Might be worth asking what platforms they have (Mac, Windows, Unix, etc), if the opportunity arises to show you're interested in learning about their infrastructure. Say if you have experience in the bits you know, keep schtum about the bits you don't. If you're not well versed in Mac OS X, for example, don't mention it unless you're asked. If you are asked about it, say that you've not used one since xyz, but you're sure it'll be easy to pick up. Shows confidence in your ability to learn something new, and that you're aware of new developments, even though you're not as up to date as you could be.
Is is first or second line support? I sadly do both. I AM the helpdesk.
Puts a real gripper on when you're concentrating on something important!Just remember never take the user's word on what they say the problem is - always investigate for yourself.
Always ask the stupid questions first - "Is Caps Lock on?" solves 99% of password problems.

Always get them to check while you're on the phone - a problem might have occured half an hour ago but they've been to busy/bone-idle to report it and by now it's not a problem any more.
You'll probably only be asked to cover what's on your CV and past experience, maybe go through some hypothetical situations. As each business and it's IT infrastructure is different, you'll only really get quizzed on 'general knowledge' and generally accepted sound practice, ie backup before cockup.
Never say "I don't know". It's always a bad answer, whether in the interview or on the job. "I'll find out and get back to you" makes you sound less ignorant - won't work in the interview though
so ask to clarify what they're asking if you don't understand.Don't be intimidated by the questioning, and don't scratch your ear or your nose - its a sign you don't believe what you're hearing or saying. Don't blabber - keep your answers to the point, and expand 'generally' - "This one time, at band camp..." won't do you any favours.
Make sure you learn about the company before you go in - remember that episode of the Apprentice where someone was asked "Do you know what Amstrad do?" and they said "No"?
Last edited by mac456; Feb 21, 2012 at 11:08 PM.
I've found that life I needed.. It's HERE!!
iTrader: (2)
Joined: Aug 2004
Posts: 1,301
Likes: 22
From: Manchester
biggest turnoff for me when interviewing, is someone clearly being fake to pretend the know everything for the job!
Oh and smelling of sawdust
I should say, we had a guy come in for an interview to a Internet Marketing agency I used to work for before going it alone, he was not bad at interviews, you could tell he had a lot of practise: but hte one reason we did not give him the job - he smelt like he had wood shavings in his pockets!
Oh and smelling of sawdust
I should say, we had a guy come in for an interview to a Internet Marketing agency I used to work for before going it alone, he was not bad at interviews, you could tell he had a lot of practise: but hte one reason we did not give him the job - he smelt like he had wood shavings in his pockets!
A reply I've used a few times in the past when asked oddball technical questions designed to trip people up is :-
The key to being a good support person is not necessarily knowing the answer but knowing how to find the answer.
The key to being a good support person is not necessarily knowing the answer but knowing how to find the answer.
Thread
Thread Starter
Forum
Replies
Last Post
keithG666
General Car Related Discussion.
21
Mar 18, 2005 02:33 PM
Stu.H
General Car Related Discussion.
9
Oct 4, 2004 06:40 PM



