Glassdoor is your free inside look at Google interview questions and advice. All 1,964 interview reviews are posted anonymously by Google employees and interview candidates.
No Offer – Interviewed in Adelaide Jan 2013 – Reviewed Mar 01, 2013
Interview Details 2 phone interview
Interview Question – The project you have recently done, the problem you have come across and how you solve it. Answer Question
No Offer – Interviewed in Sydney Sep 2012 – Reviewed Feb 12, 2013
Interview Details The second phone interview which was a technical interview.
Interview Question – Define how search keyword suggestion (such as the suggestions in google search) can be implemented. Answer Question
No Offer – Interviewed in Sydney Oct 2012 – Reviewed Feb 11, 2013
Interview Details Contacted by recruiter for a initial phone interview. Later a week, i got a call from a person in Google sydney office. He was very polite and trying to get best out of me by giving hints. Interview went well. One puzzle and one simple problem. I used java to solve it. But later one week, they had mentioned, though interviewer were impressed with your accomplishments, they felt my experience was not strong match for current requirement.
Interview Question –
Suppose that you earn 100% annual interest (APY) on $1 initial deposit. How long before you'll be as rich as Bill Gates ($63 billion)?
Given a number, e.g., 314159, as an array [3,1,4,1,5,9], increment it: change it to [3,1,4,1,6,0].
View Answer
Accepted Offer – Interviewed on Sydney Feb 2012 – Reviewed Jan 06, 2013
Interview Details
I started at Google as an intern, which required one non-technical phone screen followed by three technical phone interviews (one more than most people get). The questions here were all fairly straightforward questions of the form "Write some algorithm with some performance characteristics".
After a three month internship, I took "conversion" interviews to apply for a full time position. After a practice interview (where feedback is given - a tool to help interns prepare), I took two in-person, whiteboard-coding interviews back-to-back. I was lucky enough that the questions I was asked and my skillset intersected, and was offered a job several weeks later.
There was quite a long time between my interviews and my job offer, but my HR representitive was very communicactive and helpful the entire time, letting me know which stage my application was in.
Interview Question – I don't want to leak any interview questions; but the general content of questions Google asks is no big secret. I can categorically state that there are NO stupid brain-teaser "You are shrunk to the size of a quarter" type questions at all. The questions all involve coding an algorithm. I suggest that everyone considering applying for a technical role at Google read Steve Yegge's (public) blog post about it. All you need is in there: http://steve-yegge.blogspot.com.au/2008/03/get-that-job-at-google.html Answer Question
Negotiation Details – Given that I was hired in at the new graduate level, there is very little/no negotiation. I highly doubt any new grad would even *want* to negotiate on salary given their standard offer :)
No Offer – Interviewed in Sydney Sep 2012 – Reviewed Dec 19, 2012
Interview Details
The initial recruiter was excellent. She got me very excited about Google, but may have misinterpreted my interests a little (putting me in SRE instead which seems somewhat sysadminish for a developer).
I had 2 phone interviews and got asked to interview in Sydney. The interviewers were excellent, although again there was a focus on system administration stuff which I made clear was not a strength or interest. The coding questions were good, and I particularly enjoyed the algorithms/big data questions which they saved for last.
Unfortunately the guy I was assigned to for lunch let the whole group down. He was arrogant, unhelpful and made me hope this kind of person didn't represent the usual lunchtime/peer situation.
After a long waiting time, Google asked for yet another phone interview which I really struggled on. I had been interviewing elsewhere given how long they'd taken to get back to me, and scheduled the interview after another. I did poorly and was getting quite frustrated with the Google process.
Finally after another long wait, they suddenly requested my transcript, which took some time to dig up. Another Google department gave me a phone interview almost exclusively based on Javascript despite my clearly stating I'd written about 10 lines in my entire career. This was similarly misinterpreted, and I never heard back from that department again.
Eventually I was told to try again in 12-18 months.
Interview Questions
No Offer – Interviewed in Sydney – Reviewed Dec 06, 2012
Interview Details I had three rounds of phone interviews. I made some mistake in the second round.
Interview Question – Estimate the storage usage of GMail. Answer Question
Accepted Offer – Interviewed on Sydney Aug 2012 – Reviewed Sep 26, 2012
Interview Details
The interview stage was composed of a phone interview and two one-hour coding sessions on a shared document.
The phone interview included 2-4 general questions and about 8 technical questions.
The coding interviews were composed of 2 programming problems and related theoretical questions
Coding questions were as seen on websites such as codejam and ACM
Interview Question – Implement a hashmap Answer Question
No Offer – Interviewed in Sydney Mar 2011 – Reviewed Sep 04, 2012
Interview Details The hiring and interview process is quite rigorous at Google. The first was an initial phone interview which was not too daunting, just covered general experience, achievements to note and gather my interest in the role. The second interview was quite intense. It was basically 2.5 hours of 1 case study to test problem solving, general IQ/mathematical questions, behavioural questions and questions around a real life work example to test if I could perform in the role. There was no break and the interview was conducted by 3 different employees.
Interview Question – If you had to replace every light-bulb in the UK, how would you calculate how many light-bulbs you would need? Answer Question
No Offer – Interviewed in Sydney Apr 2008 – Reviewed Jul 02, 2012
Interview Details
Phone interview asked standard code related questions, about object oriented code, defensive
programming, etc. did well at that. one to one interview was similar but more in-depth
Interview Question – how many golf balls could you fit into that building? View Answers (2)
No Offer – Interviewed in Sydney Nov 2010 – Reviewed Apr 11, 2012
Interview Details
Got contacted by a google recruiter to see if I would be interested in taking engineering interview.
The recruiter screened me with some basic Unix/networking questions and finally got accepted to go through the process.
I went through 3 phone interviews where questions were ranging from networking, sysadmin to scripting knowledge.
Went for an on-site interview to go through 5 1-to-1 interviews of 45 min. Topics where:
* scripting
* networking
* system/storage
* system, linux processes lifecycle
* design/architecture
Interview Questions
Would you like us to review something? Please describe the problem with this {0} and we will look into it.
Sorry, but your feedback didn't make it to the team. Your input is valuable to us – would you mind trying again?
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates who said that their interview experience was positive, neutral or negative.
Your response will be removed from the review – this cannot be undone.
Copyright © 2008–2013, Glassdoor. All Rights Reserved. Your use of this service is subject to our Terms of Use and Privacy & Cookies Policy. Glassdoor ® is a registered trademark of Glassdoor, Inc.
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 – I'll just look around