3 ms·

Whenever I read about these interviews, I get the impression that they are designed for recruiting students - that is, they are loaded with theory and don't tes

• rsbrown 16y ago
  This was my impression when I interviewed with them. I passed two phone screens and interviewed on-site, but my resume died in committee. The on-site interview was pretty brutal for me, because it was very heavy on CS theory and I interviewed "cold" (meaning I did no preparation beforehand). I subsequently read Steve Yegge's tips on getting hired there: http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html http://steve-yegge.blogspot.com/2008/03/get-that-job-at-goog... His post made me feel simultaneously better (he also failed in his first attempt) and stupid (how could I think I would breeze through the Google hiring process without first boning up on CS theory?) The interview questions would have been better suited for me 12 years ago when I was a new graduate and sorting algorithms and low-level file structures were fresher for me. I don't blame Google, though. These are important concepts for them and it's my fault I didn't freshen my knowledge (or keep those skills honed over the years).