Interviewed at Google
Interview Details – Google interview process can be time-consuming and complex. You are phone screened by two recruiters before they set you up for two levels of technical interviews online. If you impressed the online interviewers with all the smart answers, and finished writing a computer program (with working solution) on the fly within the minutes they set up for you, you would be invited to a full-day interview onsite with three different interviewers. Finally, a hiring committee decides hire or no-hire with votes and scores.
Interview Question – How would you design and develop Google suggest? Answer Question
I applied online and the process took 3 weeks - interviewed at Google in December 2013.
Interview Details – Applied through their website, got a call back 2-3 weeks later and was scheduled for an initial 30 minutes phone screen. The first phone call was simply to let me know about the role and what it entailed and if I had any questions. She explained the interview process.
Second interview was a 45-60 minute google hangout interview with a senior technical account manager. The questions asked were pretty technical and were mostly all related to web technologies and how to display ads on a page.
Questions I got:
1. Tell me about a time where you had to say No to a client.
2. Imagine you work at a small startup, and you have a small website. Your lawyer comes in and asks you to take down a webpage because there is a bad image that was uploaded on your page and an advertiser is threatening to sue you. You must act immediately. How can you proceed to remove the ad/shutdown the web page.
3. Imagine you are a startup with a similar service to gmail and you are running on a single server. Your service is becoming very popular and things are starting to be very slow for the users. how can you improve your performance with the limited budget you have as a startup.
4. You work at Noogle, a startup just like google that focuses on selling advertisement space for publishers and gains revenues through clients clicking the ads and advertisers paying you per click. Overnight, your revenue declined 50%. What can you do to understand why revenue has declined?
Interview Question – Do you know what a load balancing works? Answer Question
I applied through college or university and interviewed at Google.
Interview Details – 1 phone call with the technical recruiter, ~30mins.
1 phone call with the Technical Account Manager, ~45mins
- Project questions
- Behavioral questions
- Google document: Algorithm + DS questions
Interview Question – I didn't pay attention to time/space complexity of the code. Answer Question
Very Difficult Interview
I applied online and the process took 2 weeks - interviewed at Google in September 2010.
Interview Details – Google initially responded to my application just prior to September of 2010, and scheduled a phone interview that proved quite pleasant. I next had a phone interview with their Manager of Technical Account Management Services on 9/3/2010, which also proved affable, informative and promising. My third round interview, held in-person at their Chelsea office in New York, occurred on 9/9/2010. This was easily the most difficult interview I have participated in, with brain-teaser questions as well as more content-driven questions about website monetizing and so on. The onsite interview seemed surprisingly disorganized; I met with a different group of people than indicated at first. Everyone at the office seemed intelligent and satisfied, and all of my interviewers were courteous and professional.
Interview Question – You have 78 pencils, 51 files, 152 paintbrushes and 142 felt tip pens. How many writing pads do you need? View Answer
I applied through an employee referral and the process took 4 weeks - interviewed at Google in July 2012.
Interview Details – Asked a friend to send resume to recruiting. Got contacted by recruiter in a few weeks. First phone interview was ok, interviewer asked a combination of normal questions and brain teaser questions. Google is the only company I know asking brain teaser questions (how many beach balls can be fit into a room, really!). Passed that. Second interview within 2 weeks. This time more technical, which I passed. Then an onsite interview where I talked to a hiring manager, 3 other people on the team. Out of these 4, 2 were fairly easy focusing more on why you want to work here, how you solve problem etc. 1 were fairly difficult focusing on a specific problem. I got close to the root cause but took a while. 1 were really difficult (because I have not worked in that area) but I think I eventually arrived at a solution but may have taken too long or required too much prompting. In the end I didn't get the job because the team were looking for more technical depth outside of my core expertise area, which is OK. The interview process was well managed, recruiter was great to work with. Only grip I have is they ask you brain teaser question which has nothing to do with doing the job, and they spend a lot of time grilling you in areas you have told them you have little to no experience.
Interview Question – How do you build an algorithm to check for two files with identical content in the most efficient way View Answers (4)
I applied through a recruiter and the process took 2+ weeks - interviewed at Google in July 2011.
Interview Details – After 1st round of screening through phone and 2nd round of interviewing with a potential manager, I was brought to final round of interviews at the actual NYC office. The final face-to-face interview consisted of meeting 4 senior level Googlers from different departments. Two were through webcam conferences and two I met in person.
Recruiter was very nice and walked me through the process diligently. One thing I didn't like about the process was that although the recruiter told me that Google was trying to avoid those off-the-wall difficult crazy interviewing questions, I was not prepared for some case interview and estimation type questions that I had not prepared before. They were keen to try to find analytical qualities in me and since I did badly on those case-type questions, I feel like I was not able to show those qualities adequately. If I knew they would ask market-size questions or case questions, I definitely would have read a book or two beforehand to prepare more.
The decision process after the final interview actually took 1~2 weeks which sounds shorter than it seemed at the time.
Very Difficult Interview
I applied through an employee referral and the process took 4 weeks - interviewed at Google in June 2011.
Interview Details – I felt the recruiting/HR process was messy and my recruiter didn't communicate with me very well. I tried to ask questions along the way to help me prepare, but her responses were short and unprofessional. The phone interview was pretty average and lasted for maybe 30 minutes. I heard back within a few days to schedule an onsite interview with 3-4 people. I ended up only having 2 onsite interviews since the third person was on a vacation. My recruiter was a no show, so someone else helped me out. The technical interview felt off topic for the position and didn't go well. Overall, the process made me like Google less and I wonder how a company this big can have such a flawed process. After my messy onsite day, I was assigned a new recruiter who was very helpful, so I guess it was just bad luck! Since I like Google and the products, I'd apply again!
Very Difficult Interview
I applied through a recruiter and the process took 4+ weeks - interviewed at Google in November 2009.
Interview Details – Google has one of the absolute worst interviewing processes I have ever experienced. I've been a software engineer in the silicon valley for 13 years and have interviewed at many startups, midsized and large companies. Never have I experienced the slowness nor the level of absurdity with the types of questions asked in a Google interview. These guys take themselves waaay too seriously and think that they are God's gift to humankind. If "Googlers" would stop trying their darndest to weed out quality folks with questions that appear more like undergrad software engineering quizes and look at what the candidate has done and ask them questions based on that as opposed to some clever question that invariably results in using a HashTable they might stop losing so much ground to FaceBook.
Interview Question – * Given an array of numbers. Create another array that contains
* the product of all the members in the array except the current
* element. For example, if you have an array of 3 elements such as:
* A = 2
* A = 4
* A = 6
* Then the resulting array will be
* B = 24
* B = 12
* B = 8
* View Answers (9)
I applied online and the process took 1+ week - interviewed at Google in July 2010.
Interview Details – Completed an entire worksheet with information mentining by technical skills. I clearly put down 5/10 for all my technical skills and mentioned that it was 6+ years since I programmed. So, even after this a Technical Solutions Engineer calls me and asks the below questions. What I don't get it is how come the recruiters don't communicate to the employee what is required and don't communicate to the interviewer the skills of the employee. Questions:
1. What command would you use in Linux to see the current active processes. And how would you find out which is the most cpu/memory intensive process.
2. There is a text file with 500,000+ sentences. In Linux, how would you count the number of sentences that are unique?
4. Assume a file full of numbers. Explain an algorithm to compress losslessly and decompress. Encode with an encoding of your choice
5. What is UTF-8? Explain how it works.
6. Tell me 5 SQL commands
7. Write a C++ (or language of your choice) to count the number of unique characters in a string. This was done with Google Docs and expected that I write the program while the interviewer is watching me write the program. (It was not communicated by the recruiter that I need a PC with internet connection)... so I couldn't do this one.
8. Assume you have a pretty intensive web application. Walk through the advantages/disadvantages of installing the entire applicatin in one system or distribute the application across multiple systems.
Well, I couldn't answer half the questions because my background is in project management in the mobile space and all the questins were technical on a servver related space.
What I didn't like is the fact that the don't read the resume and act a little more professionally.
I applied through an employee referral and the process took 1 week - interviewed at Google in March 2008.
Interview Details – Recruiter contacted me on the phone, called me in for a 3-4 hours of onsite interviews with dev, PM and account management teams. Wasn't that hard. But, I didn't get an offer which I thought I would, so not sure what went wrong. Didn't get any feedback on that from the recruiter either.
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 –