Fisrt time Interviewer - ummmm.........
#1
Scooby Regular
Thread Starter
Join Date: Jan 2003
Location: Staffs.
Posts: 1,273
Likes: 0
Received 0 Likes
on
0 Posts
Fisrt time Interviewer - ummmm.........
Just been informed that in my boss's abscence I have to interview a guy this morning who's coming to work for us. Having only ever been to 4 interviews in my life I can hardly say I'm confident!
#2
Scooby Regular
iTrader: (2)
Join Date: Mar 2001
Location: Swilling coffee at my lab bench
Posts: 9,096
Likes: 0
Received 0 Likes
on
0 Posts
However nervous you may be, the interviewee will be worse. (Odd how that sounds like what people say about spiders, isn't it )
Read through the CV first, and ask open-ended questions that keep the candidate talking. Start with things like "Tell me about yourself", "Describe your most relevant experience", "What can you bring to this job and what do you hope to get out of it" and go on from there. You'll soon settle down.
Read through the CV first, and ask open-ended questions that keep the candidate talking. Start with things like "Tell me about yourself", "Describe your most relevant experience", "What can you bring to this job and what do you hope to get out of it" and go on from there. You'll soon settle down.
#3
Scooby Regular
Join Date: Sep 2002
Location: The biosphere
Posts: 7,824
Likes: 0
Received 0 Likes
on
0 Posts
Write yourself out a load points you need to cover to satisfy yourself that they are good for the job, a tick list basically. Then from those points devise some questions that will allow you to either put a tick against each point or not as the case may be.
Good preparation not only makes the interview flow smoothly, but it makes sure you are consistent between all the applicants (for comparisons sake) and that you take away a record after the interview to refresh your memory about a candidate.
Good preparation not only makes the interview flow smoothly, but it makes sure you are consistent between all the applicants (for comparisons sake) and that you take away a record after the interview to refresh your memory about a candidate.
#4
Scooby Regular
Join Date: Feb 2005
Location: Derbyshire
Posts: 12,304
Likes: 0
Received 0 Likes
on
0 Posts
Fair points Andy....but....
First you need to know what role you are interviewing them for and the skills experience you are looking for to fill that position. Ideally you should have some kind of job description for the position. This will help you devise the sorts of questions you need to ask to see if the person is suitable.
Yes you do need to ask open questions to get the basic information from them, you then need to drill down on some of the keys points to find out more, this is where you start to use some closed questions as well so that you get Yes / No answers to confirm that you are understanding them correctly.
If it is a technical role of some description I would be inclined to see if it is possible to give them some kind of practical test or a gice them a typical scenario and ask them to talk you through how they would handle the situation.
See if they are eager to offer supporting information to show the depth of their knowledge or if you have to drag everything out of them.
First you need to know what role you are interviewing them for and the skills experience you are looking for to fill that position. Ideally you should have some kind of job description for the position. This will help you devise the sorts of questions you need to ask to see if the person is suitable.
Yes you do need to ask open questions to get the basic information from them, you then need to drill down on some of the keys points to find out more, this is where you start to use some closed questions as well so that you get Yes / No answers to confirm that you are understanding them correctly.
If it is a technical role of some description I would be inclined to see if it is possible to give them some kind of practical test or a gice them a typical scenario and ask them to talk you through how they would handle the situation.
See if they are eager to offer supporting information to show the depth of their knowledge or if you have to drag everything out of them.
#5
Scooby Regular
Join Date: Oct 2003
Location: None of your business.
Posts: 11,088
Likes: 0
Received 0 Likes
on
0 Posts
Business Link website includes info about preparing for the interview and carrying it out
Last edited by eClaire; 08 March 2004 at 10:08 AM.
#6
Guest
Posts: n/a
About Technical tests .... can be good to use but I wouldn't take the result as gospel. I've interviewed (And been interviewed) for Software Roles and TBH the technical test bears very little relevance to the actual work.
I'm crap at technical tests, really dire but have been working for 7 yrs as a softie and continually am ranked in top 15% of staff, yet the blokey next to me who can spout the lastest OO guff etc is not .... why's that ? I get the work done simply, not overly complicated, that's modular, re-usable etc .. he's too busy trying to use the latest OO technique and writes code nobody else can understand.
What I suppose I'm trying to say is ask relevant questions about topics at work and don't be too hard if somebody misses out a semicolon
Doofus.
I'm crap at technical tests, really dire but have been working for 7 yrs as a softie and continually am ranked in top 15% of staff, yet the blokey next to me who can spout the lastest OO guff etc is not .... why's that ? I get the work done simply, not overly complicated, that's modular, re-usable etc .. he's too busy trying to use the latest OO technique and writes code nobody else can understand.
What I suppose I'm trying to say is ask relevant questions about topics at work and don't be too hard if somebody misses out a semicolon
Doofus.
#7
Scooby Regular
Join Date: Dec 2000
Location: In a village in Hants
Posts: 1,708
Likes: 0
Received 0 Likes
on
0 Posts
Just make sure they have "Common Sense" as well as "Qualifications" and then you'll have the ideal candidate. Or at the best common sense! I've interviewed people in the past who have all the right credentials on paperwork, but lack common sense. Needless to say really, which ones got my vote and the job ............
Trending Topics
#8
Scooby Regular
Join Date: Feb 2005
Location: Derbyshire
Posts: 12,304
Likes: 0
Received 0 Likes
on
0 Posts
About Technical tests .... can be good to use but I wouldn't take the result as gospel. I've interviewed (And been interviewed) for Software Roles and TBH the technical test bears very little relevance to the actual work
#9
Guest
Posts: n/a
OllyK .. agreed
I have had a technical test that I failed miserably about 3 yrs ago. The company handed me some sheets of paper and I was told to find the errors
I knew it had gone wrong when it was 'marked' and somebody said 'Did you not notice it had no comments?' (errrmmm, yes I thought that was the whole point - no comments so I had to figure out what it was doing ) and then 'Oh you didn't spot the semi-colon was missing' .. basically they wanted to employ a C++ compiler
I've been engineering for 7yrs+ and use C/C++ .. if I'm crap I would have been found out loooong before now. I usually find out more about what they can do by asking them about what they're last project was and what was involved .. you can tell if they are making it all up or if they are enthusiastic about software very quickly ..
Doofus.
I have had a technical test that I failed miserably about 3 yrs ago. The company handed me some sheets of paper and I was told to find the errors
I knew it had gone wrong when it was 'marked' and somebody said 'Did you not notice it had no comments?' (errrmmm, yes I thought that was the whole point - no comments so I had to figure out what it was doing ) and then 'Oh you didn't spot the semi-colon was missing' .. basically they wanted to employ a C++ compiler
I've been engineering for 7yrs+ and use C/C++ .. if I'm crap I would have been found out loooong before now. I usually find out more about what they can do by asking them about what they're last project was and what was involved .. you can tell if they are making it all up or if they are enthusiastic about software very quickly ..
Doofus.
#10
Scooby Regular
Join Date: Aug 2002
Location: Sunny Swindon
Posts: 1,167
Likes: 0
Received 0 Likes
on
0 Posts
I've conducted LOADS of interviews - in the IT world......
One of my favourite initial questions, which helps break down barriers and get's things running was "Tell me a good joke....". Ignore the joke, laugh at it out of politeness, but once that is out of the way it should become easier to communicate fluidly.
My parting, daft, question was typically "Can you tell me why a man-hole cover is round?" (If they say, they're not all round, then ask for the advtantage of them being round).
Fill the bit in the middle with open ended questions....... "Tell me about...", "How did you...", "What did you learn from...", "How would your boss describe you?", "What would your boss say were your strengths and weaknesses?", blah, blah...
One of my favourite initial questions, which helps break down barriers and get's things running was "Tell me a good joke....". Ignore the joke, laugh at it out of politeness, but once that is out of the way it should become easier to communicate fluidly.
My parting, daft, question was typically "Can you tell me why a man-hole cover is round?" (If they say, they're not all round, then ask for the advtantage of them being round).
Fill the bit in the middle with open ended questions....... "Tell me about...", "How did you...", "What did you learn from...", "How would your boss describe you?", "What would your boss say were your strengths and weaknesses?", blah, blah...
#11
Scooby Regular
Join Date: Sep 2002
Location: The biosphere
Posts: 7,824
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by MrShades
I've conducted LOADS of interviews - in the IT world......
One of my favourite initial questions, which helps break down barriers and get's things running was "Tell me a good joke....". Ignore the joke, laugh at it out of politeness, but once that is out of the way it should become easier to communicate fluidly.
My parting, daft, question was typically "Can you tell me why a man-hole cover is round?" (If they say, they're not all round, then ask for the advtantage of them being round).
Fill the bit in the middle with open ended questions....... "Tell me about...", "How did you...", "What did you learn from...", "How would your boss describe you?", "What would your boss say were your strengths and weaknesses?", blah, blah...
One of my favourite initial questions, which helps break down barriers and get's things running was "Tell me a good joke....". Ignore the joke, laugh at it out of politeness, but once that is out of the way it should become easier to communicate fluidly.
My parting, daft, question was typically "Can you tell me why a man-hole cover is round?" (If they say, they're not all round, then ask for the advtantage of them being round).
Fill the bit in the middle with open ended questions....... "Tell me about...", "How did you...", "What did you learn from...", "How would your boss describe you?", "What would your boss say were your strengths and weaknesses?", blah, blah...
oh, and its so the covers don't fall through the hole
#12
Scooby Regular
Join Date: Aug 2002
Location: Sunny Swindon
Posts: 1,167
Likes: 0
Received 0 Likes
on
0 Posts
No, I was IT Manager - and this was usually a second interview. My HR team would do initial interviews, and put them through a written technical test covering a great deal of general areas of IT knowledge.
Based on their CV, the results of the technical tests and feedback from HR, I would short list a handful of candidates and get them in for a face-to-face with me.
Very often, a good candidate is one that (a) knows the technical stuff (but that's the easy bit), (b) can communicate (written and verbal), (c) has a degree of common sense and (d) will fit with the other team members.
An interview is therefore often just an information exchange - and I try to get it on as informal a footing as possible, and thus see the "real" person and not the interview persona.
Once selected, the last stage of the interview process was to pyschometrically test. This, however, was only used to pick out the psychos or complete nutcases that could obviously hide some worrying traits at interview. The basis of the selection criteria had nothing to do with these results, they were just a final sanity check...
Shades
Based on their CV, the results of the technical tests and feedback from HR, I would short list a handful of candidates and get them in for a face-to-face with me.
Very often, a good candidate is one that (a) knows the technical stuff (but that's the easy bit), (b) can communicate (written and verbal), (c) has a degree of common sense and (d) will fit with the other team members.
An interview is therefore often just an information exchange - and I try to get it on as informal a footing as possible, and thus see the "real" person and not the interview persona.
Once selected, the last stage of the interview process was to pyschometrically test. This, however, was only used to pick out the psychos or complete nutcases that could obviously hide some worrying traits at interview. The basis of the selection criteria had nothing to do with these results, they were just a final sanity check...
Shades
#13
Scooby Regular
Join Date: Mar 2001
Location: Derbyshire
Posts: 4,496
Likes: 0
Received 0 Likes
on
0 Posts
Other things to take careful note of are how they act under the pressure of the interview and/or how they are if they are struggling to answer a question...do they ask you to clarify it or do they try and muddle their way through it.
Also think about how this person might fit in to the department as a whole, as you and the team will have to work with them day in day out.
Also think about how this person might fit in to the department as a whole, as you and the team will have to work with them day in day out.
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
28
28 December 2015 11:07 PM