[daviddever23box]

I'd be careful to call that out as a negative; if the culture fit wasn't right, and the candidate would have been a net negative to the team, it shouldn't matter where they end up next, unless (of course) the candidate that was actually hired ends up being an even worse fit (ergo the need to fix your hiring process).

[RNCTX]

> I'd be careful to call that out as a negative; if the culture fit wasn't right, and the candidate would have been a net negative to the team, it shouldn't matter where they end up next

I'd be careful to presume you can know these things from an interview.

> unless (of course) the candidate that was actually hired ends up being an even worse fit (ergo the need to fix your hiring process).

Total lack of self awareness in the corporate world really is an amazing thing to behold. I suppose this is "iterating" (in HR speak, not code speak): taking a set of criteria which generates a wrong conclusion, and then applying all that to ancillary things to find more wrong answers.

[kspacewalk2]

On the other hand, "they would not have been a good fit" sounds suspiciously like a blanket, non-falsifiable denial of failure. I other words, bullshit.

[chaosharmonic]

See also: "you don't have enough experience," one which I most recently heard myself after four interviews and a technical assessment, in which my (passing) solution included a bugfix to the test itself.

[kovac]

"Culture fit" has become like the currency of recruitment. Supposedly what you may have to pay with for a potentially great engineer (technically) about whom the hiring team didn't feel comfortable with. I think the original question is a great one. Do we actually put these intuitions to the test?

[sosborn]

Is it bullshit if it is true? Hiring the wrong fit can bring a team down.

[kspacewalk2]

It's not bullshit if it's true. It can be true, or it can be bullshit. Which makes it such an awesome bullshit excuse.