I ask them to spell Czechoslovakia. I get a lot of stupid looks until I give the reason. I do maintenance work and while some people are good at certain things there are other task that they may not know how to do. I want to see if they will attempt it, if so how far will they go before admitting they don't know how. Or will they say from the start I don't know but will find out and get back with you.Its important to know your limitations and not make the problem worse than you found it.
When you look in the bathroom mirror (or any standard mirror really, so yes, like a car mirror), your left hand is on the right, but your head is not at the bottom.... How can it only switch left and right, but not up and down?
Most common question I have seen over the last few weeks sitting thru 3-4 interviews is..... What is your favorite color and describe why.
Be very careful interviewing technical people and asking abstract questions or what may be thought as "clever" questions to try and catch them off guard. You have to understand that they want to work for a great company and a great company wants to hire the best talent. Asking silly questions (at least perceived as silly by technical people) may result in them not accepting an offer.
You hire a technical person to solve technical issues and want them to be able to do so effectively while interacting with your client. Ask questions relevant to those skill sets.
Honestly, if you asked me a series of silly questions I'd probably politely stop the interview, thank you for your time, say I don't believe this company would be a good fit for me, and leave.
When you look in the bathroom mirror (or any standard mirror really, so yes, like a car mirror), your left hand is on the right, but your head is not at the bottom.... How can it only switch left and right, but not up and down?
It, like a lot of the "interview questions", is a trick question from the start. A mirror really flips toward and away from the mirror (ie objects in mirror are closer than they appear), but the question sets you up to agree that it flips left and right.... and it works because no one really thinks about it.
Here is the best answer to it that I could find on the interwebs ....
Be very careful interviewing technical people and asking abstract questions or what may be thought as "clever" questions to try and catch them off guard. You have to understand that they want to work for a great company and a great company wants to hire the best talent. Asking silly questions (at least perceived as silly by technical people) may result in them not accepting an offer.
You hire a technical person to solve technical issues and want them to be able to do so effectively while interacting with your client. Ask questions relevant to those skill sets.
Honestly, if you asked me a series of silly questions I'd probably politely stop the interview, thank you for your time, say I don't believe this company would be a good fit for me, and leave.
I'm with you on that one. Interviews are the time to bust out the riddle book.
Most common question I have seen over the last few weeks sitting thru 3-4 interviews is..... What is your favorite color and describe why.
Wonder what they would say if I answered with, "Orange because that was the color of the General Lee in the Duke's of Hazard which was my favorite show as a kid".
Non-pertinent, non-troubleshooting, or non-skillset questions have no place in a technical interview.
(*tell me about yourself, what are your hobbies, and where do you see yourself in 5 years are normal personality questions)
I would have thanked the interviewer asking about a favorite color for the opportunity to evaluate his company for future employment and walked out.
If I was the interviewers boss, I would have told barbera walters they wouldn't be interviewing anyone ever again and that all the work they've done for the past year is going to be reviewed.
I've done a lot of interviews and a few things that come to mind.
1) If the candidate is currently employed by another company, it's always a good question to ask them why they are looking to move on. Perhaps it's just the lack of upward mobility, office location, too much/too little travel, etc.
2) Ask them what they know and would like to know about the company. I don't like if a job candidate at the very least hasn't done a brief internet search on the company to stage up a few basic questions.
3) Ask about how their past experience would help the company and fill the open position.
4) Depending on the level of position, sometimes asking about reliability of transportation to and from work. and perhaps their proximity from work.
Oh and don't be a boring interviewer. Be open to conversation. There's a lot of people that go into an interview very timid, but once they get comfortable, will talk a lot more. Even if it's something like describing the history of the company, operations, etc.
I have been in HR for over 30 years and have conducted 1,000s of interviews – I have done over a dozen in the last two weeks. I will add to 12 RingKing's comments, he is close but not quit there. Ask behavioral based questions and look for specific elements in the answer. To be effective at behavioral based interviewing it takes more training than you will get on TBH. I was a certified coach on this type of interview tactics and will tell you if you do your homework, the process will improve your success rate of hiring the best person for the job.
A good question to ask everyone is, “How do you know what to work on next?” The answer is very revealing.
Another tool I like is the use of a Pugh Diagram if you have more than one candidate for the same job. I like to start out with a panel interview followed by individual half hour interviews with different members of the team, both functional and cross-functional.
I could write a book about some of the terrible answers that I got during a job interview.
My personal favorite....
QUESTION: As a member of my team, you will be required to work simultaneously on many different projects for many different customers with many different priorities. Can you explain to me your project management method in specific relation to multitasking.
ANSWER: I just work on one thing at a time or I will just screw it up. (silence and content look on face)
Comment