As a recent hire at Google, I don't really think this is the case. There's not just a bias towards false negatives, there's a strong bias. It's well understood here that lots of qualified people are turned away.
And for whatever it's worth, the offer to keep your resume on file wasn't just lip service. I interviewed two years ago unsuccessfully, and was recruited a year and a half later based on the strength of that failure. It's also maybe worth mentioning that my only prior work experience was four years of desktop software development in C#, so I don't think the Microsoft thing is that much of a black mark.
This is pretty much exactly what I said. Do you think if I'd pointed out that I'm actually a google employee also, I might have been spared the down votes?
Jobs interviews at Google aren't near perfection with a slight bias towards false negatives, and it's unfair to the people who don't make it through to suggest that they are.
But you know what? From a certain perspective, that's fine. We're currently going through a hiring phase at the startup I work for, and I'd much rather turn away people who might be ok than lock someone in who slid by. From his StackOverflow profile, cletus is a top-notch developer (or at the very least passionate and knowledgeable), it just sounds like he encountered his anti-loop. The biggest problem I see (and encountered this myself with them) is that there's no real feedback, even if your raw score was only just below the mark, where it might behoove everyone if you came back and interviewed with a little more experience and/or preparation.
I am a Googler. I mentioned explicitly that false negatives happen, and stated why they are preferable. Why, then, do you preface your comment with a disagreement?
>> If the feedback from five different interviewers led to a 'no hire' decision, the chances are good that it was the right decision.
That may well be the case and I can't dispute the conclusion because I am unaware of the position. Were they looking for a hardcore C++ programmer? That's not me.
This goes to my observation that feedback is important. I've applied for positions that were slim chances before but I knew they were slim going in so I could set my expectations accordingly.
As for the lottery part, 2/5 didn't know my primary language. That seems open to interpretation.
My interview experience actually involved them hammering me on the languages I said I knew but wasn't an expert in. This is likely as they were trying to find out whether I was lying (or, put kindly, overstating) on my resume. From what I've seen there are a few people who put every language down that they've ever written hello world in ;)
(disclaimer: recent intern from Google Sydney office)
I see the same behavior with VC's -- no usable feedback. It's like in poker -- there's no game-theoretic advantage to show your cards if everyone else folds.
In many cases this is still true at the time of the hire.
In a few cases this is still true at the time the person starts on the job.
They go to great lengths to ensure this is not the case. If the feedback from five different interviewers led to a 'no hire' decision, the chances are good that it was the right decision. Of course, no system is perfect. They tend to err on the side of exclusivity; it's much cheaper to decline a suitable candidate than it is to hire someone who won't work out in the long term.