Live data from Hacker News

How I build and run behavioral interviews

benkuhn.net

11–20 of 51 posts

Re: How I build and run behavioral interviews

#11
> The second sentence (context/problem/solution) is important for helping the candidate keep their initial answer focused—otherwise, they are more likely to ramble for a long time and leave less time for you to... Dig into details

How about, instead of asking "Tell me about a time you...", and you presuming to understand the situation so well that you can make judgments about nuance based on the off-the-cuff example you asked for, and trying to cut them short from "rambling"...

You instead ask them "Say you have a situation like X; how would you approach it?" And you can change the situation by adding information, "What if the report responds Y?"

Then both people are operating from closer to similar information about the situation. (Though it's still possible that the interviewee understands something about these situations in general that the interviewer doesn't.)

This also avoids dredging up past unpleasant situations (someone with more experience will have handled more unpleasant situations, but that doesn't mean it doesn't invoke a somber mood, if they're not acting or oblivious).

It also means they don't have to also think about how much they can say under NDA and being discreet about personnel matters (while a poor interviewer might take hesitation or choosing words carefully as interviewee trying to put themselves in the best light or keep a fabricated story straight).

An expected objection to this approach of spinning a hypothetical situation is that candidates might just say what they think are the correct answers. But knowing the correct answers is at least half the problem. And what do you think many candidates are doing in the interview anyway, if they are the kind to know the correct answers, but not follow them in real life.

Re: How I build and run behavioral interviews

#12
Any guide or blog post on how to interview that doesn't compare interview notes to performance reviews after hiring someone is basically bullshit.

Anyone can write a blog post about what they think is a good interview but there's no empirical proof that their interview technique works.

Re: How I build and run behavioral interviews

#13
Good advice overall, and definitely an improvement over the usual interview boilerplate that candidates have to trod through.

However, in some places it seems to be too cavalier -- in the sense that it suggests we now have a magic prism with which we can "diagnose" the candidate's shallowness or lack of candor. When really they're just saying something basically innocuous. Cause it's like, been a long and mostly boring interview process so far, has it not, and they're trying to slog their way through the canned / pre-programmed (if arguably necessary) part of the process like you are.

For example, under "Things to watch out for":

High standards: if they say there’s nothing they wish they’d done differently, this may also be lack of embarrassing honesty, or not holding themselves to a high standard

Or they had a genuinely shitty experience (with high costs to finances, relationships and/or health) that was 80 percent out of the blue and beyond their control. And they'd really rather just move on. Or if they did tell you the real context and their real reasons for doing X -- you'd very likely ding them (quite likely fatally) for doing so.

Re: How I build and run behavioral interviews

#14
The hubris of those hiring tips & tricks posts never cease to amaze me.

Hubris in the sense that they really think that they are doing something right, so much so that they blog/post about it.

Yet, if I take this post as an example, I notice a lack of self-reflection about bias en why you would interpret behaviour a certain way and not another.

In the end, it's all subjective, and everybody is doing their best, but how valuable is it really?

Especially, if you don't know anything about the company/organization that this person is hiring for?

Re: How I build and run behavioral interviews

#15

Any guide or blog post on how to interview that doesn't compare interview notes to performance reviews after hiring someone is basically bullshit. Anyone can write a blog post about what they think is a good interview but there's no empirical proof that their interview technique works.

True to the extend that you'll never get a real evaluation, because you'll never know how the people who were turned down, would have fared.

Re: How I build and run behavioral interviews

#16
post #11

> The second sentence (context/problem/solution) is important for helping the candidate keep their initial answer focused—otherwise, they are more likely to ramble for a long time and leave less time for you to... Dig into details How about, instead of asking "Tell me about a time you...", and you presuming to understand the situation so well that you can make judgments about nuance based on the off-the-cuff example…

[deleted]

Re: How I build and run behavioral interviews

#17
One thing that I've noticed makes a difference is to be positive and complimentary to the candidate at the start of the interview. Make it clear that you're excited to talk to them and that you are genuinely excited to hear what they have to say.

I've missed out on hiring good people who were nervous or worried about doing a bad job in the interview. I'm sure I still do miss out on some but I've found a method that lets some people feel more comfortable without being overly difficult on me and can live with that.

Re: How I build and run behavioral interviews

#20
> Ask how big of an effect something had and how they know. (Example: I had a head of technical recruiting tell me “I did X and our outbound response rate improved;” when I asked how much, he said from 11% to 15%, but the sample size was small enough that that could have been random chance!)

Where is this evidence in this post? What beneficial effects did your new behavioral interviewing technique produce?

Post reply on HN