write a review
back | Posted on May 02, 2008 at 1:15 PM for Software Engineer in Test | |||||||||
|
Number of Interviewers:
5
Total Hours Interviewed: 6 Interview Comments: 0. Have an impressive resume, advanced degree or 4.0 GPA. 1. Submit resume from Google Jobs and correctly answer all the the personality test questions. They are scored by some heuristics and the highest scorer is a personality clone of Larry Page or Sergey Brin 2. Recruiter calls you up in 2 days, asks you some general data structure and programming questions for 15min. (They just read those off a crib sheet) 3. If you passed, an engineer calls you up in 1 week and drills you with more technical skills questions, 2 algorithm/data structure problems. 4. If passed, you get an on-site interview for a full day with 3-4 more engineers. Each will test your problem solving skills, and ability to invent and code algorithms to solve problems. Free lunch after the 2nd, play some ping pong and then 2 more after lunch. Each lasts for about 45min. 5. If all the engineers say you are good, your resume goes to a hiring committee, which takes another weeks or so. 6. If the committee deems you as fit, you application goes to Larry Page. 7. If Larry Page says yes, you are hired. Important notes: Be confident, have a lot sleep before hand, be alert and definitely know your shit. When it comes to the actual interview, just relax and tickle the algorithm problems bit by bit. From my impression, as long as you reaches step 4 and don't act like an asshole, all you really need is to answer all the algorithm questions right and you should get hired. |
||||||||
| Posted on November 28, 2007 at 08:52 AM | |||||||||
|
Number of Interviewers:
4
Total Hours Interviewed: 5 Interview Comments: The interview process itself is a bit long. You have two phone interviews: one with a recruiter who will tell you about the process, and one with a tech dude who will rip you to pieces and make you cry. Not really, but it's hard. If you're lucky to get past that, you make it to round 2 - the on-site interview, where they fly you (in my case) to NYC and grill you for half the day. You'll get treated to lunch and sit (awkwardly) with one of their junior engineers talking about Google love. At the end of the day, breathe easily and wait for the call (or call them - they're so bad about getting back to you in time). Can't really go into too much detail on the questions - they make you sign a NDA (non-disclosure agreement). But you should definitely study all the generic interview programming questions. I was shocked to learn that almost all of them were out of a programming interviews book my friend gave me (I just wish I had prepared better). But in any case, be ready to go into depth on everything. No stupid mistakes, know your stuff otherwise they toss you out on the street. Not much to offer here. Just study your butt off for the few weeks before the interview. Get as many C/C++ problems down as possible, study all the generic programming questions. The whole thing wasn't that dreadful really - just relax and be ready. |
||||||||
