News for hackers. Stuff that matters.
Re:Job Interview Questions That Mean You’re Not Getting Hire... by mikeryan on Wednesday December 10, 2008 @05:35PM (#393586)
Pretty damn true.

I've done my share of hiring in the last couple of years, allow me to opine on this post.

"Tell me about yourself." Common question, usually my first question with candidates just to let them talk a bit about themselves and let them tell me what they feel is important. It also just breaks the ice even with a (hopefully) easy question. It doesn't mean you're not getting hired.

"What are your biggest flaws?" - I don't use this, its a bullshit question and I don't know anyone who does. No one in their right mind is going to tell you the truth. "What are you strengths" is however a decent question, like "tell me about yourself" it allows the interviewee to tell you something about themselves that you may have missed.

"Where do you see yourself in 5 years?" - Not actually a dumb question, most people don't use it correctly. The answer to this question can be useful from a "goodness of fit" perspective. Do their goals align with how your organization works? This isn't a make or break question but it can get interesting answers.

"Tell me about a time when you..." - Sorry this is the main type of question you should b e asking. This is the opportunity to ask the question "how are you going to solve the problems that we're going to give you?"

"How many gas stations are in the United States?" - Ya crap question, but some engineering managers like them.

Re:Job Interview Questions That Mean You’re Not Getting Hire... by njharman on Wednesday December 10, 2008 @08:54PM (#393797)
> "Tell me about a time when you..." - Sorry this is the main type of question you should b e asking. This is the opportunity to ask the question "how are you going to solve the problems that we're going to give you?"

Probably what you really want is someone who solves problems not someone who can eloquently describe problems and their solutions, under pressure, in a few minutes or less.

That question is a classic example of testing the wrong thing.

It's better for you to describe an actual problem and have them solve it or discuss how they would go out solving. Which btw is typically a needed skill (being able to reason out and weigh solutions with a team)

Re:Job Interview Questions That Mean You’re Not Getting Hire... by mikeryan on Thursday December 11, 2008 @01:42AM (#394049)
Maybe I misunderstood? I'm not assuming that this question is open ended, but that at the end of this statement is some sort of situation that needs to be resolved.

An example that I've used before, "What would you do if you're convinced a more senior developer is choosing the wrong solution? (usually I'll present something obviously inferior to another choice, point isn't technical but how someone would try to resolve a conflict)"

Re:Job Interview Questions That Mean You’re Not Getting Hire... by dhimes on Wednesday December 10, 2008 @09:56PM (#393869)
kinda like: "how many gas stations are there in the US?" Can you make quick estimates and assumptions to arrive at a conclusion?