Re:A note to Google recruiters (and on Google hiring practices)
by rimantas on Monday July 25, 2011 @02:05AM
(#2801541)
> For really brain-dead reasons, they didn't like me.
I may be brain-dead too, but I have no problem seeing why they might not like you.
Re:A note to Google recruiters (and on Google hiring practices)
by snikolov on Monday July 25, 2011 @12:47AM
(#2801383)
I think the point was that the interviews don't require you to be able to have published research in optimization or algorithms --- they want you to be able to solve a relatively constrained class of problems quickly, for which a specific kind of preparation is required.
Re:A note to Google recruiters (and on Google hiring practices)
by NY_Entrepreneur on Monday July 25, 2011 @01:38AM
(#2801490)
They are being too narrow.
Re:A note to Google recruiters (and on Google hiring practices)
by contravert on Monday July 25, 2011 @01:28PM
(#2803600)
I think a lot of confusion on this topic stems from what Google values from a candidate's knowledge of algorithms. From my experience, these technical interview of an algorithm, but you sure wouldn't have to prove anything formally.
Algorithm and computer science knowledge can be applied very practically. Skienn a also wrote a book called Programming Challenges, which features problems very similar to those asked in these technical interviews. The coverage of topics like dynamic programming may be very shallow from a theoretical perspective; however, an intuitive understanding and mastery of when to use the technique and how to write the code is absolutely crucial to solving many difficult programming problems.
Re:A note to Google recruiters (and on Google hiring practices)
by NY_Entrepreneur on Monday July 25, 2011 @05:13PM
(#2804666)
I like dynamic programming for various reasons, and at times it can get used as a technique for what really are computer science algorithms, but my experience is that that usage is rare.
With dynamic programming, I have to conclude that Google is just looking for ways to toss people out.
In particular, Google is showing that they are far too centered on 'computer science' where they accept low quality material just because it was hijacked from its real origins in various fields of applied mathematics into a book on 'computer science' and poorly presented there.
The post insisted that a candidate needed to know dynamic programming as in Skiena or was not "prepared", and this is sick-o, brain-dead, ignorant, arrogant, destructive nonsense: First, there is nothing serious about dynamic programming in Skiena; Google is not "prepared" in dynamic programming. Next, while I happen to know a lot about dynamic programming, I've never asked about it in interviewing people for computer science positions. One reason I know a lot about dynamic programming is that my Ph.D. dissertation was in stochastic optimal control.
What I didn't say, but which is true, and which I implied, is that the topics in Skiena should not be given so much importance. Or, to be so positive on Skiena's book is to be far too fond of a particular collection of gnats and to forget a herd of elephants.
One way and another, I happen to have a good background in nearly all the topics in that book, usually far deeper than in that book, but in interviewing I would not ask for knowledge of topics from that book. Here Google is making a mistake.
In addition, I did once have a Google interview: It was a disaster. For really brain-dead reasons, they didn't like me. Their worship of C++ as a religion showed that they have a bad interview process which meant that I didn't like them. Good riddance.
That they want their interview process to be so severe indicates both arrogance and ignorance; they should be brought down a few notches.
There is a fundamental problem in such interviewing that apparently Google has not understood: Can't hire a bunch of house painters or people who have just heard about house painting to select someone to paint the ceiling of the Sistine Chapel. Google's process would definitely filter out any Michelangelo. They'd likely also filter out a Steve Jobs, Larry Ellison, or Bill Gates.
In fact, based on a brain-dead religious devotion to C++, their process filtered out someone with expertise in nearly all the topic in Skiena's book much deeper than in the book.
Actually, mostly people who are really good with the better topics in Skiena's book never touch C++!
Google is making mistakes. Their interview process is a symptom, among others, of some serious management problems at Google.