Google Engineer Interview Questions

54 Interview Reviews

Interview Experience

Interview Experience

49%
35%
15%

Getting an Interview

Getting an Interview

62%
24%
4%

Interview Difficulty

3.5
Average

Interview Difficulty

Hard

Average

Easy

54 Candidate Interview Reviews Back to all Interviews

Sort: Popular Date Difficulty

 

Engineering Interview

Anonymous Employee in San Jose, CA
No Offer
Positive Experience
Easy Interview

Application

I applied through other source. The process took 2 weeksinterviewed at Google (San Jose, CA) in April 2010.

Interview

After recruiter's phone call with general organizational questions, I had short technical phone interview. Interviewer was late for 10 minutes, thus we talked only 30-35 min. For this time he was able to ask me not very much: some of my previous experience, most difficult bug I've faced recently, and one technical question with coding in shared doc. After that he let me to ask him something about google. He answered one question and finished interview, so I had no change to fund out everything I planned. Also I had a feeling, the guy was not interested to be there, coz he was not leading me through resolution process and talked very little. Also his communication skills could be better - I hardly understood his questions in Indian English and asked to repeat several times. Google should sent better skilled and more open English speakers to interview, IMHO. I successfully resolved technical coding question in two different ways (time and memory efficient) with commenting my resolution thoughts, but have got negative response from recruiter in 1 week.

Interview Questions

  • Write a code to find out if two string words are anagrams   4 Answers

Other Interview Reviews for Google

  1.  

    Engineering Interview

    Anonymous Employee in Mountain View, CA
    No Offer
    Positive Experience
    Easy Interview

    Application

    The process took 2 daysinterviewed at Google (Mountain View, CA) in March 2010.

    Interview

    first a phone interview with some technical questions that were straightforward. invited to the googleplex for 1:1 interview with 4 people. pretty relaxed interview about background and skillsets. informed a week later that it was not a fit for the position.

    Interview Questions

  2. Helpful (2)  

    Engineering Interview

    Anonymous Employee in Mountain View, CA
    Declined Offer
    Neutral Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 2+ monthsinterviewed at Google (Mountain View, CA) in January 2010.

    Interview

    First there is a phone interview. Then you go to the company campus and sit in a room and stressed people turn up late to ask you a series of technical questions of increasing difficulty. Some of the interviewers were interested in thinking about their problems, but most were acting more like it was their duty to come to these meetings. One interviewer was outright rude when I pointed out that he was in fact wrong in his solution to a problem he posed. Generally the process felt mechanised, impersonal and ineffective. Having worked in similar firms and been involved in the hiring process there it felt that Google was more interested in being different than actually finding good candidates. The food on offer was so on, nothing special compared with other bay area high tech companies.

    Interview Questions

    Reasons for Declining

    Took too long to make an offer.

  3. Helpful (1)  

    Engineer Interview

    Anonymous Employee in Cambridge, MA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through an employee referral. The process took 2+ monthsinterviewed at Google (Cambridge, MA) in January 2010.

    Interview

    Lots of red tape and bureaucracy to get to the on-site. Then a bunch of really good questions in a series of 5 one on one interviews. Some basic questions but then lots of algorithmic stuff, pointer arithmetic, optimization questions, scaling questions. LOTS of questions about how to make things work well on 100k+ computers at once. They also do a surprisingly good job of selling a company that practically sells itself.

    Interview Questions

    • Solve the "game of life" problem in C++ so that it will be both OO and efficient. Scalability and parallelism are also pluses.   1 Answer
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5.  

    Engineering Interview

    Anonymous Employee in Mountain View, CA
    No Offer
    Negative Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 4+ weeksinterviewed at Google (Mountain View, CA) in January 2010.

    Interview

    Google basically does not care what you have done, and doesn't interview you for any particular position. They mainly want to know if you are talented at answering academic computer science questions. Does this build a good company? I don't think so, but it's up to them to decide that, I guess. Six interviewers asked me incredibly detailed data structure and algorithm questions. Nothing that anyone asked me would have distinguished me from a recent graduate. I thought I did pretty well, but apparently not well enough. My recruiter sounded as surprised as I was that I didn't get an offer. Apparently anyone who interviews you can veto - so it's everyone's loss that one of my interviewers was a terrible interviewer. Be sure to buy, and at least skim, a copy of "Programming Interviews Exposed; Secrets to Landing Your Next Job" (Mongan/Suojanen/Giguere?), recommended directly by Google recruiters. Best of luck.

    Interview Questions

    • Let's say you have a lot of numbers and you want to sort them. What do you do?   1 Answer
  6.  

    Engineering Interview

    Anonymous Employee in Mountain View, CA
    No Offer
    Neutral Experience
    Difficult Interview

    Application

    I applied online. The process took 2 weeksinterviewed at Google (Mountain View, CA) in November 2009.

    Interview

    Applied for an entry-level engineering position online. Was contacted pretty quickly by an HR rep, who checked my basic credentials (school, when I could start, etc) and scheduled two phone interviews with engineers. I was expecting some of those weird "Google" questions like "How many ping pong balls can fit in a school bus?" but apparently they don't ask anything like that anymore. Most of the questions were about algorithms and data structures, so definitely brush up on those. (Hint: when in doubt, just say you'll use a hash table)

    Interview Questions

    • How can you find a cycle in a singly-linked list (a place where the last node links back to a previous node)?   1 Answer
    • Given two arrays of integers, return a new array containing only the common elements.   1 Answer
    • How would you write an algorithm to search across many machines?   1 Answer
  7. Helpful (2)  

    Engineering Interview

    Anonymous Interview Candidate in Mountain View, CA
    Accepted Offer
    Negative Experience
    Difficult Interview

    Application

    I applied online. The process took 6 weeksinterviewed at Google (Mountain View, CA) in October 2009.

    Interview

    Don't bother reading these questions. It won't help. Google's interviews are set up such that the questions either have impossible answers, or the problems are changed so much looking them up won't matter. You just have to have very solid computer science fundamentals and show enthusiasm. For such a large company, the interview process feels so ad hoc that it almost deterred me from accepting an offer. I ended up accepting, but I'm hoping the interview process will be improved so others won't make a decision the other way.

    Interview Questions

    • How would you build Google search?   1 Answer
  8.  

    Engineering Interview

    Anonymous Employee in Palo Alto, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a staffing agency. The process took 1 dayinterviewed at Google (Palo Alto, CA) in October 2009.

    Interview

    People were friendly, there were easy interview questions about all kinds of fun stuff like trees, searching, arrays, optimizing code, etc.

  9. Helpful (1)  

    Engineering Interview

    Anonymous Employee in Mountain View, CA
    No Offer
    Neutral Experience
    Difficult Interview

    Application

    I applied online. The process took 4+ monthsinterviewed at Google (Mountain View, CA) in July 2009.

    Interview

    It takes FOREVER from when you apply to get an interview (in the ballpark of 4 months, easily). You'll get contacted by various HR people, who don't really coordinate with each other. The interviews themselves were fairly difficult technical questions; I'd recommend studying extensively and being systematic in your approach.

    Interview Questions

    • Find the maximum rectangle (in terms of area) under a histogram in linear time.   2 Answers
  10.  

    Engineering Interview

    Anonymous Employee in Seattle, WA
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied through an employee referral. The process took 1 dayinterviewed at Google (Seattle, WA) in June 2009.

    Interview

    I interviewed for a network architect position, stating clearly at the beginning of the interview that I was involved in application and TCP level performance analysis. However, the interviewer kept questing me about layer 2 material because that's what he knew. It was clearly not the right role for me, but I decided not to continue the interview process after that.

See What Google Employees Are Saying

Marketing

 Current Anonymous Employee

Pros: “Everyone is so friendly and I enjoy working here”“Everyone is so friendly and I enjoy working here” – Full Review

Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.

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.