I applied through a recruiter and the process took 1+ week - interviewed at Google.
Interview Details – A recruiter found me on LinkedIn. She is very professional and super nice. I sent her my resume via an email on which I answered a few questions about my background in techniques and research; about school and employment. She planned a phone interview for me with one technician, 45 minutes. I answered 2 tech questions.
Interview Question – The tech question isn't really hard. I answered the basic solution and then was expected more efficient solution and finally the problem has to be solved in a scalable scope. I bet these should be completed in 20 minutes at most but that took me 40 min. Of course I didn't get further interview. Answer Question
I applied through a recruiter and the process took 5 days - interviewed at Google in June 2012.
Interview Details – Was emailed by internal recruiter that found me on Linkedin.
Setup phone call and discussed my qualifications and the job.
recruiter setup technical call.
Interview Question – I was not well prepared for the technical portion of the process. While I am quite capable of writing good code I was not expecting what to me seemed esoteric questions. Answer Question
I applied through a recruiter and the process took 3 months - interviewed at Google in February 2013.
Interview Details – 0) Internal referal of my email address, no resume.
1) Recruiter Contact
2) Submit resume and go over basic questions on interests and experience. Schedule technical phone interview
3) Phone Interview
4) One week later, I inquire over email whether I passed. Receive follow up immediately that they would like to schedule onsite.
5) Transferred to different recruiter. Submit a full application and more details.
6) Onsite, 3 interviews, lunch, 2 more interviews.
7) One week later, receive news that I passed interviews and first hiring committee
8) Submit references
9) Passed more committees and goes to team matching
10) Contact with actual manager, come to mutual agreement
A few notes:
Take your time, don't be afraid to ask for a later interview date to study up. I went over Cracking the Coding Interview by Gayle, its a good book to review basic concepts. No questions I got actually came out of the book, but its good mental prep for the kind of problems you'll face.
Also try top coder to work on coding if you are out of date writing actual code. I feel top coder questions are a bit brute force compared to the questions you'll get. Top coder questions ask you to accomplish a task, but the extent of what you'll end up using is arrays and strings. You won't get good coverage of things like trees, linked lists, etcs.
Don't assume you'll need to get everything right during interviews. I didn't for sure and one interviewer had a distinctly negative attitude (whether this was intended or he actually flunked me I don't know), but I still ended up doing well enough to pass. Also, don't worry about the interviewers typing or writing during the interview. Apparently, they need to take all of your code verbatim to give to the hiring committee, so however much you write, they need to write. Stay calm and talk through your answers. Don't assume you did poorly or well, its too hard to guess and treat each interviewer individually.
Overall a long process, but a fair one. In engineering its important to keep standards high and consistent.
Interview Question – Bunch of technical questions, some problem solving but basic, some knowledge related, some system design. All are fair, no riddle or brain teaser questions. Standard programming interview. Answer Question
Negotiation Details – Not much
I applied through an employee referral and the process took 2 weeks - interviewed at Google in March 2013.
Interview Details – Interviewing for Google, it turns out, is far easier than public perception would lead you to believe. Study your data structures and algorithms and it will be a breeze.
Also practice whiteboard coding before hand to get used to working without your IDE of choice. You'll make mistakes, and that's okay, but if you practice beforehand you'll get through the process far more comfortably and thus will whiteboard better code during the interview. If over the phone, expect a Google Docs session. If in person, expect an actual whiteboard.
Interview Question – My interviewer asked me a question which involved using a binary tree to solve an optimization problem, which I was very prepared for. What through me off guard was how the tree was being used for the problem. Expect to see familiar things presented to you in potentially a new light. Answer Question
I applied through other source and the process took 4+ weeks - interviewed at Google in April 2013.
Interview Details – I have no idea how they hire people. My only rule so far is "whatever you think the result of your interview with Google is - you are wrong". First time I though I did a lousy job - I got to the next phase. Next time I thought I did well - this turned out to be false. The questions during an on-site interview were not difficult, but really niche, requiring a very particular background.
Interview Question – Heap types. Answer Question
Interviewed at Google
Interview Details – Recruiters are really nice and efficient. I had 4 interviews and it takes almost 4-5 hours. The recruiter's hints in email are not very helpful. They are quite different from problems in my interview but still thanks for their help in the whole process. It was a nice experience
Interview Question – Not quite difficult if you had seen similar problems before but for me some of them are unexpected. I expected to see problems in algorithm and data structure, like tree and graph. they took me some time to figure out. Answer Question
I applied through an employee referral and the process took 1+ week - interviewed at Google.
Interview Details – 2 Phone Interviews (45mins * 2) was placed in the first round. I believe they have further rounds for people who passed phone interviews. In the phone interview, they don`t ask what you have done before. They will give you the instruction for the interview and start examining your programming skills and your abilities for the software engineer.
Interview Question – generation random number not in list Answer Question
I applied through an employee referral - interviewed at Google in January 2014.
Interview Details – 5 onsite interviews. 1 guy was *so* rude and that showed he is not experienced. Didn't allow me to think more and just pushed me to implement my first solution which I said it is gonna take a long time to implement. Clearly I didn't manage to finish ontime and he left the room with describing what a mess I did. He was so arrogant. He was being shadowed though. The 4th guy was a bit better but still had communication problems. Was just interrupting me while I was implementing my code. I had to stop him by telling him just stop and let me finish my code, and then I will review it for you and then feel free to ask questions. He ultimately appologized in the end but clearly I got rude to him this time (because he was just bugging me). in the end, this would turn against me I guess. waiting for the interview results. The other three were polite, and experienced. I would say an interview has two sides and your side is the more important side. but there is another side who might not be experienced enough to manage an interview session.
Interview Question – honestly not difficult questions. Just basic stuff. Answer Question
I applied through college or university and the process took 5+ weeks - interviewed at Google in October 2013.
Interview Details – Process was fairly straightforward, interview was alright, the interviews were kinda rude and weren't paying attention at all. They ask all coding questions, don't care about who you are your background where you come from etc
Interview Question – Regarding binary trees, stacks and queues all in one question Answer Question
Reason for Declining – Dont wanna work there
Interviewed at Google
Interview Details – quick phone interview very easy programming question just like return average of nearby 5 points.
Interview Question – nothing difficult expect the accent of indian Answer Question
Pros: “superb environment and facilities; great support to employees, such as workstation setup, ergonomic support, and experiment facilities training and support; various opportunities for…” “superb environment and facilities; great support to employees, such as workstation setup, ergonomic support, and experiment facilities training and support; various opportunities for life-long learning; good practices learned through the internship has a long-lasting effect on my further development;” – Full Review
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –