Google Interview Questions

Updated Oct 16, 2014
Updated Oct 16, 2014
3,257 Interview Reviews

Interview Experience

Interview Experience

52%
28%
19%

Getting an Interview

Getting an Interview

35%
24%
24%

Interview Difficulty

3.5
Average

Interview Difficulty

Hard

Average

Easy

Candidate Interview Reviews

Sort: Popular Date Difficulty
  1. 179 people found this helpful  

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

    Interview Details

    Direct onsite because I interviewed in the past and did well that time. From the time I sent my resume to interview day: 2 weeks. From interview day to offer over the phone: 2 weeks.

    The syllabus for the interviews is very clear and simple:
    1) Dynamic Programming
    2) Super recursion (permutation, combination,...2^n, m^n, n!...etc. type of program. (NP hard, NP programs)
    3) Probability related programs
    4) Graphs: BFS/DFS are usually enough
    5) All basic data structures from Arrays/Lists to circular queues, BSTs, Hash tables, B-Trees, and Red-Black trees, and all basic algorithms like sorting, binary search, median,...
    6) Problem solving ability at a level similar to TopCoder Division 1, 250 points. If you can consistently solve these, then you are almost sure to get in with 2-weeks brush up.
    7) Review all old interview questions in Glassdoor to get a feel. If you can solve 95% of them at home (including coding them up quickly and testing them out in a debugger + editor setup), you are in good shape.
    8) Practice coding--write often and write a lot. If you can think of a solution, you should be able to code it easily...without much thought.
    9) Very good to have for design interview: distributed systems knowledge and practical experience.
    10) Good understanding of basic discrete math, computer architecture, basic math.
    11) Coursera courses and assignments give a lot of what you need to know.
    12) Note that all the above except the first 2 are useful in "real life" programming too!

    Interview 1:
    Graph related question and super recursion

    Interview 2:
    Design discussion involving a distributed system with writes/reads going on at different sites in parallel.

    Interview 3:
    Array and Tree related questions

    Interview 4:
    Designing a simple class to do something. Not hard, but not easy either. You need to know basic data structures very well to consider different designs and trade-offs.

    Interview 5:
    Dynamic programming,
    Computer architecture and low level perf. enhancement question which requires knowledge of Trees, binary search, etc.

    At the end, I wasn't tired and rather enjoyed the discussions. I think the key was long term preparation and time spent doing topcoder for several years (on and off as I enjoy solving the problems).

    Conclusion: "It's not the best who win the race; it's the best prepared who win it."

    Negotiation Details
    You can and should negotiate politely. You are in a stronger position if you have another offer, but even otherwise, you should ask for more of every type of payment!
    Accepted Offer
    Positive Experience
    Difficult Interview
  2. 63 people found this helpful  

    Software Engineer Interview

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

    I applied online. The process took 4 weeksinterviewed at Google in August 2014.

    Interview Details

    My interview and hiring process was extremely tiring but satisfactory. I dropped out of college and cancelled my plans to study in an university because I wasn't learning anything there. I studied and mastered computer science alone at home within 2 months. Although I am just 19, I decided to apply for Google and I wouldn't care if I got rejected really. I applied online and quite suprisingly; they replied back the next day to set-up an phone interview. They asked a few question and then told me "Alright, we'll call you again next week." And when they did that the next week, they invited me for an on-site interview. I met some interesting people there, and most of them were amazed due to the fact that I dropped out of college but had the abilities and in-depth knowledge of a Harvard-graduate software engineer, also because I am just 19. Some guy named Paul came to me and asked me a brain-teasing question about algorithms and I gave him back a cheesy, but informative answer and he told me "You're probably going to get accepted."

    During the on-site interview, they asked me long questions and gave me difficult tests/tasks on:
    1. Recursions
    2. Dynamic Programming
    3. Graphs
    4. Data Structures
    5. Problem-solving query test
    6. Array and Tree
    7. Computer architecture (binary search, low level enhancement...etc)

    They gave me some stuff related to graphs and recursion to build over, it was mind-boggling like hell. But that doesn't mean I didn't enjoy it. I like challenges, and Google managed to give me those....a LOT of those.

    The interviewer's name was Caleb, and he said that I fulfill the criteria of a Google software engineer, and thus; they hired me immediately. Caleb was a fun person, I enjoyed being interviewed by him. He also said that I am the YOUNGEST software engineer in the history of Google, I felt really proud at that time. He gave me lots of compliments after the interview like "You're an exceptional person" - Google interviewers are extremely nice and respectful, you don't need to be nervous around them.

    Interview Questions
    • You dropped out of college, and you're just 19. Do you think you can handle Google at this age?   View Answers (6)
    Negotiation Details
    Tiring but satisfactory. I negotiated a $190,000 per-year salary and an $5k starter bonus.
    Accepted Offer
    Positive Experience
    Difficult Interview
  3. 167 people found this helpful  

    Associate Account Strategist Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through an employee referral. The process took 5+ weeksinterviewed at Google in September 2013.

    Interview Details

    A little over 2 weeks after I submitted my application, I was contacted by a recruiter via e-mail. She asked if we could arrange a time to speak over the phone. We scheduled some time for later that week. During that initial phone screening we discussed my interest in the position, my current job, and established a deeper understanding of the role I was applying for.

    After about 25 minutes, the recruiter said she'd like to arrange a time for me to speak with someone else who was actually in a similar position to the Associate Account Strategist role. A few days later, this call took place. There were a lot of situational questions.

    - Tell me about a time when you overcame a challenge in the workplace
    - How have you improved a certain process at work?
    - Why Google?
    - Tell me about a time when you spoke with a dissatisfied client and what did you do to appease them?
    - Name 3 advantages of AdWords
    - Have you ever improved the efficiency of a process/task at work?

    Despite a lot of nerves, I got a call back and was asked to do an 'onsite' interview with 3 Googlers. I did this via a Google hangout since I was interviewing for a position in another country. Prior to the onsite interviews, the recruiter kindly walked me through how these interviews would be. She gave me lots of details including resources for how to prepare. They were right on point and helped to set a realistic expectation of what these interviews would entail.

    The first interview was with the manager of the team. She asked questions about AdWords/Google products and my familiarity with role relevant skills like data analysis and client interaction. Example Questions:

    -improvements you would make to your favourite Google product.
    -Experence pulling and analysing data.

    The second interview was with someone from another language team but in a similar role. She asked a lot of questions that started with, "Tell me about a time when..." or "Have you ever..." Example Questions:

    - What accomplishment are you most proud of?
    - A time when you took the initiative and led a project

    Final interview was with someone else on the team I was applying for. He was friendly and asked situational questions as well as questions related to my personal interests. Example questions:

    -What would you bring to the team?
    -Why this particular position?
    -How do you show creativity?

    Overall, everyone I interviewed with was very professional and kind. I liked that everyone was polite, approachable but also to the point. I spent a lot of time preparing and used the following resources:

    Glassdoor interview feedback
    Google jobs website
    Actual job posting description (read this many times so that I could have a firm understanding of the role)
    Recruiter--Make sure to ask questions if you're unsure of anything. The lady I worked with was great about letting me know what to expect. It was incredibly helpful in planning on how to prepare.

    Interview Questions
    • If Google decided to charge g-mail users, how would you recommend implementing this? Would it be sustainable and what would be the advantages and disadvantages?   View Answers (4)
    Negotiation Details
    Their offer was firm, no negotiations.
    Accepted Offer
    Positive Experience
    Difficult Interview
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review
  5. 16 people found this helpful  

    Product Manager Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter – interviewed at Google.

    Interview Details

    Phone Screen for Google Product Manager -

    The questions were:
    * Why Google?
    * Tell me about the most exciting project you've worked on in the past, and why it was the most exciting for you.
    * Design scenario: The alarm clock industry is really waning as of late. What could you do to curb this trend?

    Interview Questions
    • Design scenario: Let's say you have a tv remote with 3 buttons, mute, vol up, vol down. What would you expect to happen if a user hits vol up button when its muted? Talk through the scenarios and what the user is trying to do. What would you expect to happen if you hit vol down button when it's muted?   View Answers (2)
    Accepted Offer
  6. 3 people found this helpful  

    Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Interview Details

    Phone screen, I applied online for the position and the very next week a recruiter emailed me to set up an interview. An interview was set up 4 or 5 days later.

    Interview Questions
    No Offer
  7. 1 person found this helpful  

    Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

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

    Interview Details

    I was contacted by a recruiter on LinkedIn. She set up an initial phone "interview" with me to find job openings at Google that were suitable for my background. The recruiter was very nice and helpful. She informed me about the interview stages and how to prepare for them. The initial stage was a technical phone interview which would involve coding in Google docs. I gave her my availability and the interview was set up.

    Take as much time as you need to prepare for the technical phone interview. It is best to be prepared than to rush into it. I wasn't well prepared, so I didn't make it to the next stage.

    Interview Questions
    • Agreed to an NDA, so I cannot disclose. But it was a graph related question, very similar to the graph related questions on hiredintech.   Answer Question
    No Offer
    Neutral Experience
    Average Interview
  8.  

    Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied online. The process took 2 weeksinterviewed at Google.

    Interview Details

    I applied online and got an email back the next day. The recruiter was very nice and very quick to reply. We set up two back-to-back phone screen interviews requiring live coding. The first was pretty straightforward and we completed 3 questions. The second was a tougher question that took longer.

    Interview Questions
    • I'm not allowed to post anything about the specific questions.   Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  9. 5 people found this helpful  

    Software Engineering Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through college or university. The process took 4+ weeksinterviewed at Google.

    Interview Details

    Met Google at campus career fair. Signed up for interview.

    Had two on-campus interviews - one on algorithms, one on data structures. Both interviews were about 45 minutes long and pretty much launched right into the problem. There wasn't much small talk beforehand. I did the coding on a sheet of paper.

    After that, had a phone interview which was more informal - just a discussion of my technical background and projects.

    Interview Questions
    • Problem 1: Effectively boiled down to: "Find the ith largest integer in an array of integers". The solution was order statistics (http://en.wikipedia.org/wiki/Selection_algorithm)

      Problem 2: Given a simple cellular automaton. Asked to design a data structure to represent it using the least amount of memory I could. Then asked to implement an algorithm to make the automaton take a step (following a set of rules) and make it as efficient as possible.
        Answer Question
    Negotiation Details
    No negotiation
    Accepted Offer
  10.  

    Software Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

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

    Interview Details

    Got my initial phone interview through an employee referral. This was followed up with a second phone interview since I didn't do too well on my first one, I think. I did manage to get to an onsite interview in San Bruno with four interviewers. However, I ultimately failed to get hired.

    Interview Questions
    • None of the questions were really difficult in a logical sense after preparation from provided materials, but I think I misinterpreted the question the second interviewer gave me after later reflection.   Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  11.  

    Intern Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied online. The process took 6 weeksinterviewed at Google.

    Interview Details

    The process took over a month. Took a couple weeks to schedule the interviews after submitting my application and then a few more weeks to receive a decision. Two back to back interviews were scheduled. The interviews went well and they said that I passed them, however they didn't offer me a position.

    Interview Questions
    • First interview focused on basic data structures and the second involved navigating a 2d array. There were also a few questions on big-Oh notation and pros and cons of various data structures.   Answer Question
    No Offer
    Positive Experience
    Average 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.