I applied through an employee referral and interviewed at Google.
Interview Details – It is 45 mins. 2 questions, first one about distributed algorithm, not very clear about the request, which is confusing, second one about array, to delete the duplicate. For the first question, I even could not fully understand the question itself because limited information. For second one, it is very easy to answer.
Interview Question – how to design a algorithm which could run in a large computer systems? Answer Question
I applied through an employee referral and the process took 1+ week - interviewed at Google in January 2014.
Interview Details – phone screen first, asked me some questions then do coding on a shared Google Doc file.
Interview Question – Seems the questions are simple, like visit a tree, or go up/down. Need to be careful about the details, such as integer overflow in C, etc. Answer Question
I applied through an employee referral and the process took 2 months - interviewed at Google in June 2011.
Interview Details – Was submitted as a req by a Googler, had a terrible phone interview (interviewers phone kept dying, so all communication was through Google Docs),
Interview Question – All questions are covered by a NDA. Answer Question
Negotiation Details – I had offers from Intel, which I used to dramatically speed up the process.
Very Difficult Interview
I applied through an employee referral and interviewed at Google.
Interview Details – Most software engineers do a phone screen first. I had two referrals who recommended me highly, so I skipped the phone screen and went straight to on-site interviews. Five technical interviews in a single day, with a break for lunch. Interviews were heavy on coding, algorithms, and software design. Practice solving coding problems on a whiteboard.
Interview Question – I don't remember it exactly, but a coding question in my first interview with an engineer who didn't speak English very well. I had no feedback from her about whether I was even on the right track. She just typed into her laptop and said almost nothing. Answer Question
Negotiation Details – I negotiated a signing bonus of $10k so I could take a bit of time off before joining.
I applied online and the process took 2 months - interviewed at Google in October 2011.
Interview Details – I responded to a billboard in a major metropolitan area, which directed respondents to a web site whose domain name was the solution to a computer science / math problem involving prime numbers. After solving the problem and accessing the web site, I submitted my credentials and expressed interest in a position.
It took Google about 18 months to respond.
When they did, it moved quickly. I had a first-level phone screen with a recruiter, asking very simple questions about operating systems and scripting. I then had a second-level phone screen with a member of technical staff, who asked me intermediate technical questions, as well as discussing my current job content with me. Based on these phone screens, I was invited to their HQ for an on-site.
On site, it was a reasonably pleasant day. I had 6 or 7 interviews, each with a different engineer. All of them were situational, where the interviewer would open with a scenario, and build / evolve it as the interview went on. For example, the easiest one was, "How would you write a program to perform [some simple sysadmin task] in Perl?" Once I solved it, the interviewer would expand the scope, or introduce some complication that required more advanced problem solving skills.
All of the questions were good, they were really meaty and interesting. The quality of delivery varied widely though, with some of their engineers being very comfortable conducting interviews and having great people skills. Others not so much, one gentleman appeared to be inconvenienced by having to interview new hires, and had poor personal hygiene to boot, which made enduring his interview uncomfortable. Another aspect that varied widely was attitude .. many at the Googleplex were socially stunted, while others were handsome / beautiful, well dressed, and hip. Almost uniformly they were arrogant and dismissive.
Ultimately, I received a follow-up call, where they offered me a role at a starting salary of $75K. I politely countered, noting that I was already making more than $100K in an area that had much lower cost of living than the SF Bay Area. In the final analysis, Google felt that their brand equity and being able to put their name was worth more than the $25K gap, a point with which I strongly disagreed. I rejected their offer and we both went our separate ways.
Interview Question – Consider a scenario in which an trans-continental file transfer fails with the following error message: [...] This is the only information you have to go on; walk us through your mental line of troubleshooting. View Answer
Reason for Declining – At the time of my offer, Google valued its brand equity, its capabity to enhance an employee's resume, as a real piece of its compensation package. Therefore they paid less than other SF Bay Area competitors. Because I already had a job that paid more, in an area with a lower cost of living, I turned down the role and kept my current job.
I applied through an employee referral and the process took 4+ weeks - interviewed at Google in February 2014.
Interview Details – I got 2 back-to-back 45 minutes interviews. I think I was a bit too slow on answering the questions, and I got completely flustered when asked if I had any questions at the end of the first interview (don't do that, prepare questions, such what the interviewer works on and how he likes Google etc.).
I did sign an NDA, so I won't say what the questions were, though they did cover BSTs, binary search, finding intersection. I also explained how mergesort works (and I didn't do it as naturally as I should have).
Interview Question – Probabilities. I was not expecting probabilities, and I needed a lot of help to land on the correct solution.
I was also not really expecting the "tell me about yourself" type of question, though looking back, I should have. Answer Question
I applied online and the process took 4+ weeks - interviewed at Google in February 2014.
Interview Details – I submitted a resume and heard back from its technical recruiter months later for a different opening (previous opening was filled). A phone interview was set up with the hiring manager. The phone interview was 45 min long. The interviewer was pleasant, intelligent, inquisitive. I was given information on multiple managerial roles and functions for which they are looking (there were several openings). I was informed, post telephone interview, there will be 4-5 onsite (including peer-based) interviews, each 45 minute long.
Interview Question – I was asked to share two challenging projects experience from a technical role and as a a change agent as well as to rank areas of expertise pertaining to planning, cost, product data management, quality, logistics, and compliance. View Answer
I applied online and interviewed at Google.
Interview Details – Google has long and slow hiring process. I was contacted by Google candidate review associate, who sent my information to recruiter, and finally I was contacted by coordinator who schedules interview. I appeared for first phone screen. It had one coding question.
Interview Question – Given a doubly linked list as
1 <-> 2 <-> 3 <-> 4 <-> 5<->6
and input (1,2,4,3,6)
Find out longest sub sequence in doubly linked list containing max number of input elements and return its last number.
For above input 1-2-3-4 is longest sequence as per given input. And last number is 4.
for input (1,2,4,7)
Answer should be 1-2 and 2 is last element Answer Question
Interviewed at Google
Interview Details – phone interview. apply on google website. take two week for process and schedule phone interview one three to four weeks later
Interview Question – 1. Describe what happens when user surf the internet
2. What's Java Object class. Name one of its method. What will be returned for equal() if two objects have same hashcode Answer Question
Pros: “get to work with PMs who are talented and amazing and you get to have a lot of responsbility” “get to work with PMs who are talented and amazing and you get to have a lot of responsbility” – 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 –