I do think that the company lost out on a good hire because of this. The job requires some specialized math, as well as domain knowledge and programming ability. I don't think there are many people will this skillset.
But next time, I will most definitely review this material prior to the interview, because it really cost me.
A) I can google it if I ever need to know B) Most languages today have support for graphs, trees, and sorts, and other cs trivia things built in or via stable libraries
It seems like a potential employee's ability to 'get things done' would be more important
I don't have an issue with Gooogle's requirement to know what you are doing, but unfortunately I think the interesting jobs at Google are becoming few and far between.
Of course, a talented hacker will know the details of some data structures and algorithms. I'd be far more impressed with a candidate who could tell me in detail about recent uses of a couple more unusual data structures and algorithms than with a candidate who knew all the classics in detail but nothing unusual.
You have a lot of warming up to do. Real-world work makes you rusty.
Those quotes make it sound like Google's interview process is biased toward people who know a lot of basic-CS trivia. If real-world work makes you rusty, doesn't that imply that the interview is favoring people who have studied up on certain things such that they know them better than they actually need to? I would agree that a good candidate should have been familiar with the details of everything Yegge mentions at some point. But is there really much value in knowing these things "cold", rather than merely knowing them "warm"?