write a review
back | 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. |
||||||||
