A tech giant with great engineers, but personal growth might be limited
A tech giant with great engineers, but personal growth might be limited
Lots of capable engineers, with experts in every computer science area.
Tech talks.
Compensation is good.
Free food.
Mountain View site is fairly crowded.
Visibility can be low as there are many talented people, and you may not get the project you like most.
A bit secluded, and everything you hear and see is about Google.
The hiring process could be made more friendly to candidates.
Was this helpful?
Google Interview Questions
Google Interview Experiences
Software Engineer
HR phone screen, Tech screen, Onsite in Mountain View. Fairly standard. Study data structures well. Be able to answer general database/web related questions. Each of the interviewers was pleasant, except for the hiring manager. I got the feeling I
Software Engineer
The process was long and arduous. First, I had a recruiter screen with typical HR questions. Then, after about two weeks, I had a phone screen with an engineer. I needed to write code on a shared document while talking to the engineer on the phone.
Software Engineer
The interviewer was not quite interactive. He kept looking at his laptop; it looked like he was working on his own stuff. He was not excited about looking at your code on the whiteboard.
Software Engineer
Mountain View, California, United StatesJuly 1, 2017HR phone screen, Tech screen, Onsite in Mountain View. Fairly standard. Study data structures well. Be able to answer general database/web related questions. Each of the interviewers was pleasant, except for the hiring manager. I got the feeling I
Software Engineer
Mountain View, California, United StatesJanuary 1, 2011The process was long and arduous. First, I had a recruiter screen with typical HR questions. Then, after about two weeks, I had a phone screen with an engineer. I needed to write code on a shared document while talking to the engineer on the phone.
Software Engineer
Mountain View, California, United StatesAugust 1, 2014The interviewer was not quite interactive. He kept looking at his laptop; it looked like he was working on his own stuff. He was not excited about looking at your code on the whiteboard.
