Google

  www.google.com
  www.google.com

Google Senior Software Engineer Interview Questions

Updated Nov 14, 2014
Updated Nov 14, 2014
52 Interview Reviews

Interview Experience

Interview Experience

50%
20%
29%

Getting an Interview

Getting an Interview

44%
37%
16%

Interview Difficulty

4.1
Average

Interview Difficulty

Hard

Average

Easy

52 Candidate Interview Reviews Back to all interviews

Sort: Popular Date Difficulty

5 people found this helpful  

Senior Software Engineer Interview

Anonymous Interview Candidate in Mountain View, CA
Anonymous Interview Candidate in Mountain View, CA
Application Details

I applied through a recruiter. The process took 2 weeksinterviewed at Google in July 2009.

Interview Details

The job was for a software development position. First a Google recruiter contacted me. Some initial questions to gauge fit and interest. Then a technical phone screen. If you have a solid CS background, this is pretty easy to pass. A couple general data structure and algorithm questions. And every Google interview asks about big-O notation. You need to know this or forget about working at Google.

Then the on-site interview. I interviewed with 4 engineers, 45 minutes each. They each spend about 5 minutes on my background or past projects. However, they are not really interested in this and didn't really pay attention to my answers. Next 35 minutes consists of technical grilling and about 5 minutes at the end for me to ask questions.

Each interviewer sets up a problem and asked you to solve it. Sometimes its hard to figure out what the interviewer is asking, but asking lots of clarifying questions helps. Some problems I solved and some I did with lots of hints. I was then asked the order of complexity of my solution and how I could improve the solution.

Then the real hard part, for me anyway. I was asked to write the code for the solution on the white board. Writing code in an IDE after thinking about it for a few minutes is one thing, but writing code on a white board in a short amount of time is another. I didn't do so well here.

After the interview and thinking about all the problems they asked, none of them were particularly hard and the coded solution is usually about 10 lines of code.

I found most of the engineer interviewers very polite and interesting to talk to. A couple of them were arrogant and came with an attitude that you had to prove that you were as smart as they are. But overall, I found the interview a positive experience and felt I learned something.

Interview Questions
  • Given an array of numbers, replace each number with the product of all the numbers in the array except the number itself *without* using division.   View Answers (14)
  • Create a stack of numbers where the maximum number is always known.   View Answers (6)
  • Create a cache with fast look up that only stores the N most recently accessed items.   View Answers (4)
  • Explain the difference between Array Lists, Linked Lists, Vectors, Hash Maps, (from Java's JDK) etc. and when one choice is better of another.   Answer Question
No Offer
Positive Experience
Difficult Interview

Other Interview Reviews for Google

  1.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Anonymous Interview Candidate in Mountain View, CA
    Application Details

    The process took a dayinterviewed at Google in December 2009.

    Interview Details

    The interview was pretty technical and they don't really care about your previous experience. They have a slip that is passing around to interviewers and they put comments on what they already asked just to avoid asking the same question. They tried to cover different technical aspects, but I had 3 interviewers asking me about writing algorithms to solve given problems and all sorts of efficiency big-O discussion.

    Interview Questions
    • Given a list of iterator, write an wrapper iterator that can iterator thru all the iterators in the list   Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  2.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Anonymous Interview Candidate in Mountain View, CA
    Application Details

    I applied through a recruiter. The process took 2+ weeksinterviewed at Google in June 2008.

    Interview Details

    I had two rounds of phone interviews. In the first round the interviewer asked me about my current experience, motivation to work in google etc. I believe this was mostly to get an understanding of who should be interviewing me. In the second round, the interview was mostly technical. I was asked some coding questions, questions about memory management, and data structures.

    Interview Questions
    • I was asked a question about the following. If a user types in a n digit number on the telephone, how do you write a function to deduce if the number constitutes a valid word. For example, if the user enters 123, then can a valid word be made out of (a/b/c) + (d/e/f) + (g/h/i)   View Answers (4)
    No Offer
    Positive Experience
    Difficult Interview
  3.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    The process took 2 daysinterviewed at Google in September 2009.

    Interview Details

    While working at Google may (or may not) be great fun, the interview process there is much less so. After a very technical phone interview, my in person interview was all about tricky logic problems with no focus on the engineering process itself (optimal card shuffling, How many golf balls can fit in a school bus?,etc.)

    Interview Questions
    No Offer
    Neutral Experience
    Difficult Interview
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5. 2 people found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Anonymous Interview Candidate in Mountain View, CA
    Application Details

    The process took 2 weeksinterviewed at Google in December 2009.

    Interview Details

    One screening phone interview with recruiter, on-site interview thereafter with 6 engineers at Googleplex. All the engineers looked very smart but the interview questions were somewhat consistent (Big O notation and hash table) and not practical in real scenarios. They definitely look for particular engineers and they basically have no interest in your past experience. Not recommended for career development.

    No Offer
    Negative Experience
    Difficult Interview
  6. 2 people found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in New York, NY
    Anonymous Interview Candidate in New York, NY
    Application Details

    I applied through an employee referral. The process took 2 daysinterviewed at Google in May 2008.

    Interview Details

    I was able to skip phone interview due to friend recommendation but typically you will be screened by phone. Your on site interview will be a full day and you will be quizzed by 4-5 developers. You will be asked technical questions and be asked to write some programs on a white board. These will tend to be computer science type problems: Convex Hull, String manipulation, List manipulation, and so on.

    Interview Questions
    • Develop a solution to convex hull and state its complexity.   View Answer
    Reasons for Declining

    Salary too little

    Declined Offer
    Neutral Experience
    Difficult Interview
  7.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter. The process took a dayinterviewed at Google in May 2010.

    Interview Details

    The google recruiter found me from internet and contacted me for phone interview. The phone interview was very technically difficult and I partially failed to answer 3 of the total 15 technical questions.

    Interview Questions
    No Offer
    Positive Experience
    Difficult Interview
  8.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in Boulder, CO
    Anonymous Interview Candidate in Boulder, CO
    Application Details

    I applied online. The process took 1+ weekinterviewed at Google in April 2008.

    Interview Details

    Initial stages of the interview were fairly routine. Phone interview was a little bit technical, but reasonable.
    In person interview ended up with me failing to properly code an algorithm on the board, and the interviewer basically ending the interview at that point. Memorize your algorithms before this one, because merely knowing the algorithms properties and being able to look it up won't be good enough for this guy.

    Startup got bought out by google and ended up with a bit of an attitude. Google thinks they walk on water.

    Interview Questions
    • What sort would you use if you had a large data set on disk and a small amount of ram to work with?   View Answers (5)
    • What sort would you use if you required tight max time bounds and wanted highly regular performance.   View Answers (5)
    No Offer
    Negative Experience
    Difficult Interview
  9.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied online. The process took 3 daysinterviewed at Google in August 2011.

    Interview Details

    there are phone interviews and on site interviews.
    for on site, they paid for plane, hotel and food expenses. the recruitier and five skilled software engineers interviewed me each a time, asking software design and development questions. that was a tiresome but very fun and enriching experience

    Interview Questions
    No Offer
    Positive Experience
    Difficult Interview
  10. 1 person found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in Newport Beach, CA
    Anonymous Interview Candidate in Newport Beach, CA
    Application Details

    I applied online. The process took 2 weeksinterviewed at Google in December 2008.

    Interview Details

    After a phone interview and an engineering interview in which I wrote code in a Google doc while talking with the interviewer, I was invited in for a face to face. I met with about twelve engineers and managers over eight hours with a break for lunch. They asked very tough questions and really dug in to see how you think.

    Interview Questions
    • They gave me printouts of a couple of classes that worked together but were badly designed. The goal was to talk about how to better design the classes so they had clearer roles and better implementation.   View Answer
    No Offer
    Positive Experience
    Difficult Interview

Work at Google? Share Your Experiences

Google

 
Click to Rate
or

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.