Google Senior Software Engineer Interview Questions

Updated Oct 15, 2014
Updated Oct 15, 2014
50 Interview Reviews

Interview Experience

Interview Experience

51%
21%
27%

Getting an Interview

Getting an Interview

53%
34%
10%

Interview Difficulty

4.1
Average

Interview Difficulty

Hard

Average

Easy

50 Candidate Interview Reviews Back to all interviews

Sort: Popular Date Difficulty

 

Senior Software Engineer Interview

Anonymous Interview Candidate
Anonymous Interview Candidate
Interview Details

Everyone at Google was easy to work with. The recruiters clearly explained the process as we went along. However, the hiring is done by committees. They have the local committee on-site which then makes a recommendation to a corporate committee. The various levels there make the process take a while and seem redundant.

Interview Questions
  • Go through different combinations of numbers to compute what sums to a given number and analyze the runtime.   Answer Question
No Offer

Other Interview Reviews for Google

  1.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Interview Details

    I was going through a conversion interview so my interview experience was likely different. Had a few standard programming questions (1 was to maintain stats on a hourly, minute, and day granularity and the other was a variant of a hash table design). I had to negotiate a lot but it had a huge impact on my offer. I also had competing offers from Facebook, DropBox, and a startup.

    Interview Questions
    Accepted Offer
    Positive Experience
    Average Interview
  2.  

    Senior Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Interview Details

    Their standard process: Applied on line through their website, was contacted by their recruiter within 3 days for initial talks, set up the phone interview for the next week which was technical and involved solving one programming question, called on site for 5 back to back technical interviews with their programmers. It was a good experience.

    Interview Questions
    • Calculate the point when the time/space complexity for a merge sort would be as good/bad as a insertion sort for given values for step executions.   View Answer
    No Offer
    Positive Experience
    Average Interview
  3.  

    Senior Software Engineer Interview

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

    I applied through an employee referral. The process took 2 weeksinterviewed at Google.

    Interview Details

    Was very quick as I already had another competing offer from Microsoft.
    Interview was scheduled as soon as I sent my resume through employee referral. And got the offer letter very fast.

    Interview Questions
    Negotiation Details
    Did not negotiate
    Accepted Offer
    Positive Experience
    Difficult Interview
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review
  5. 4 people found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied online. The process took 6+ monthsinterviewed at Google in January 2014.

    Interview Details

    Applied online and 7 months later received a phone call from recruiter.
    Phone screen appointment was setup for the following week.
    At phone screen, recruiter first described position then setup a coaching prep appointment.
    Recruiter asked questions then attacked my answers with accusations I wasn't a team player and being too excited.
    2 weeks later, hiring manager called and yelled the questions at me which I answered
    coolly and competently. 1 week later, recruiter feedback was that my answers were all correct but too detailed since this was not an on site interview. Recruiter also laughed at how I answered manager's questions.
    Most demeaning and insulting interview of my life.
    PS: I caught the hiring manager making a technical mistake about databases.
    Based on this incident and their buggy Android platform,
    their engineers are NOT superior to Silicon Valley engineers in general.
    It is all theater for the stock holders.

    Interview Questions
    • How many ants can you count living inside an ant hill?   View Answer
    No Offer
    Negative Experience
    Difficult Interview
  6.  

    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 4+ weeksinterviewed at Google in January 2014.

    Interview Details

    I was contacted through linkedin by a recruiter and after giving them a few references from friends who work at google, i was able to bypass phone screen. My friends said they received a form that they filled out. But even than, I was passed around to at least 4 different recruiters by the time I was actually onsite. I was interviewed by 6 people, plus the lunch person that had no say on the process. 3 of the interviewers asked me to code on a white board, and 3 did not. I thought that was odd, I had expected all of them to ask me to code. I made a mistake of making google my first interview in 7 years so I made silly errors. Overall it wasn't as dreadful as others described it.

    Interview Questions
    • Nothing unexpected, the recruiters sent materials to review. Definitely go through sample problems from CTCI book and Elements of Programming Interviews. C++ and Java works best for these questions. Actually, C++ works the best since Java can be very verbose at times.   Answer Question
    No Offer
    Positive Experience
    Average Interview
  7. 4 people found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in San Jose, CA
    Anonymous Interview Candidate in San Jose, CA
    Application Details

    I applied through a recruiter. The process took 2+ monthsinterviewed at Google in November 2013.

    Interview Details

    My recruiter called me to have an interview in next week and did not call me back first time. At second time, she said she can arrange an interview in next week, I was so afraid to loose the opportunity and agreed to take it even I did not have enough time to prepare for it. I think google's interview needs intensive preparation.

    Interview Questions
    • Write a probability formula to tell how many bits will be changed when 1 is added to a 32 bit binary number.   View Answers (5)
    No Offer
    Negative Experience
    Difficult Interview
  8. 10 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 a recruiter. The process took 4+ weeksinterviewed at Google in October 2013.

    Interview Details

    After initial contact last year that did not lead to an offer, I was again contacted by Google.

    I went to the New York office for the full day / 6 part interview. I will not (as I agreed and signed for) disclose the specific questions asked. However, these should not be a mystery or secret for anyone, they are about algorithms, mathematics, sorting, hashes, system design, multi-processor, multi-site problems, etc. If you rehash your Uni material, read all the recommended basic Algo and practice material, none of these questions should come as a surprise.

    One thing I will say tho is that not all interviewers are equally as enthusiastic. I do not know if this is by design or not, but out of the 6 interviews I had, 1 guy seemed outright disinterested, while another guy was courteous enough to give proper questions, but didn't seem to have his heart into it. I do understand to some extent as the interview process is grueling and you WILL be worn down at the end of the day, I assume it is equally an effort for the interviewers, especially if they have to do multiple interviews (and reject the majority). Make SURE you are RESTED the day before. Anyways, do realize that you can not afford any clear negative review, the hiring committee will allow one negative if you have great reviews from the other interviewers, but two negatives will kill any hopes, regardless how smart or good you are. Make sure not to antagonize any deadbeat interviewer you might run into. And DO practice whiteboard design and coding. It is THAT important.

    That said, I had a lot of fun with most of the interviewers. The most important aspect is that they want to see if you ARE what I understand to be 'googly'. This means smart, inquisitive, investigative, curious, a problem solver, etc. You will get challenged. How you approach a problem or question or how you proceed with each monkey wrench they throw at you is more important than getting the 'perfect answer'. There were no questions about how many elves you can fit in a coke can, etc. I had very interesting and fun interactions with the interviewers talking about the topics they asked me, and also wandering off-topic on other computer and non computer interests.

    One surprising thing is that I found out that Google actually contacted most of the professional references I provided. (Which I didn't mind, as I have very good backgrounds and well respected references who would vouch for me any day). Please make sure to put in your best references, make sure to reference the people who have good experiences with you and can vouch for your work and qualities.

    Negotiation Details
    The offer procedure was pretty straight forward. Google made me a very generous offer, my current employer announced a counter offer, Google modifier there offer, and once I was comfortable enough with the conditions, timeline and notice for my own job, I did sign.
    Accepted Offer
    Positive Experience
    Difficult Interview
  9. 3 people found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in Seattle, WA
    Anonymous Interview Candidate in Seattle, WA
    Application Details

    I applied through a recruiter. The process took 4+ weeksinterviewed at Google.

    Interview Details

    I was contacted via LinkedIn originally for a position in Mt. View. When I made it clear that I wouldn't relocate, they referred me to the Seattle office -- which turns out to be the 3rd largest Google office after Mt View and New York. Seattle recruiter was very friendly and stayed in touch up until I was handed off. After initial phone I was set up for the standard tech screen phone interview. I hit it off well with the phone tech guy and managed to work through the question. After review by hiring committee I was handed off to another recruiter and setup for onsite interview in Seattle office. One comment, although I emphasized at every turn that I felt that the Kirkland office would be an easier drive for me, I was consistently sent to the Seattle office which I found a little odd.

    I arrived on time for my 6 hour interview at the office in Seattle. Apparently this office is growing rapidly, they are taking over another building already. Parking is a little strange, if you can find their parking garage I believe they will validate your parking. If you park on the street you'd better have some cash -- I think it was $10 for the day and I didn't get reimbursed for that. It's an exciting and scenic location right on the water in the Fremont area. My first interviewer was running late and he seemed a bit rushed in general, I guess he was in the process of moving to Calif for a month. I had interviews in three different conference rooms and two different buildings, 5 tech interview and one friendly interview who told me that he does not report anything so I can ask him anything I want -- its good to be prepared with your off the record type questions to ask your lunch companion. Generally the interviewers were pretty friendly and diverse in style and personality. They were very open about the process, I found out that decisions are made by a hiring committee, not by the interviewers -- very different from Amazon for example. They have categories of questions that must be covered. Almost everyone asked me a fairly typical coding question, I was also asked questions about how I would design and test larger projects. For example, one question was to design a suggestion list for the Google Search engine.

    One nice thing about Google was that they provided me with a chromebook and I was given the option to write my code on the chromebook. I was also given the option to use the Whiteboard. I tended to use both -- the whiteboard for working out algorithms and drawing diagrams, the chromebook for serious coding. This was a little awkward since the big screen didn't seem to be working right so they had to huddle around me while I was typing.

    Overall I felt good about the onsite interview, I was very curious to see the Google facility, experience their vibe and meet some actual Googlers so in that regard I was very happy. I had mixed feelings about taking the job since it would be a long commute for me, so I wasn't terribly disappointed or surprised when the hiring committee declined to make me an offer. The recruiter did make a point of giving me that news on the phone and she also went out of her way to say that I had received much positive feedback and the door is always open if I want to try again. She couldn't give me any detailed feedback unfortunately, against policy, and she did apologize for the lack of transparency in that regard.

    Personally I think Google is probably the best of the big tech companies in terms of how they treat people and interesting projects. They encourage people to move around from project to project which I like quite a bit, and they provide lots of fun benefits. When compared to my Amazon experience I have to say that Google wins on every level.

    Interview Questions
    • Given a series of words written using a scrambled alphabet, figure out what order the letters of the alphabet are in.   View Answers (6)
    No Offer
    Positive Experience
    Difficult Interview
  10. 1 person found this helpful  

    Senior Software Engineer Interview

    Anonymous Interview Candidate in San Jose, CA
    Anonymous Interview Candidate in San Jose, CA
    Application Details

    I applied through a recruiter. The process took 2+ monthsinterviewed at Google in April 2013.

    Interview Details

    Phone screen was 100% technical, with coding via Google Docs, and was told I did *VERY* well.

    4 one-on-one onsite interviews - coding on a white board, systems design. I thought I did very well.

    Was asked to travel back for a final onsite, but declined due to existing offers on the table... and if you can't look at my resume, see my successes and figure me out after 5 interviews, don't expect me to jump through hoops for you... other companies are willing to make quicker, informed decisions.

    Interview Questions
    • Would you like to come back for another onsite?   View Answer
    No Offer
    Negative 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.