Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Google

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Google reviews | Google jobs | Google salaries | Google benefits | Google conversations
      Google interviewsGoogle Software Engineer interviewsGoogle interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Software Engineer Interview

      12 May 2010
      Anonymous interview candidate
      New York, NY
      No offer
      Neutral experience
      Difficult interview

      Application

      I applied through a recruiter. The process took 5 weeks. I interviewed at Google (New York, NY) in Apr 2010

      Interview

      I was contacted by a Google recruiter by phone. My resume was on file from a previous interview 3 years ago which did not result in an offer. We had a short conversation about what was available at Google and about what my experience was. The questions and information were very high level and it didn't seem like this was even a phone screen of any sort. She then passed me on to the HR person at the NY office. I was told that there would be a phone interview where I would need to be at a computer and would need to be able to code, but since I has already been onsite previously they decided to skip this. I was handed on to yet another person to actually schedule the interview and then back to the HR person. The onsite interview was from 10 to 3 and consisted of 5 interviews and a lunch conversation. Each interview was 45 minutes and they ran pretty much right on schedule. They were difficult, but pretty much what was expected. There almost no discussion of work history or anything other than technical questions. Most of the time was spent at the whiteboard working on and then refining the answer to a question. They mainly focused on data structures and algorithms around them. Things like BST, hash tables, tree traversals. The questions were not standard algorithm questions that you tend to see around, but a bit more involved. They were interested in your speaking about the algorithmic complexity of your solution and how to choose appropriate data structures. Hash vs. BST came up a bit. The coding that had to be done was a bit awkward for a whiteboard. The solutions were not necessarily short. One interview revolved around a higher level system design question that was refined throughout the discussion. There was very little to no time to ask questions or discuss working at google and the inteviewers did not seem interested in selling me on google. The lunch conversation was not an interview and did not contribute towards the assessment. The person I ate with was very nice and seemed honest about the way things are at google. Over 2 weeks after the interview I was contacted with the rejection. Overall the process was smooth and people were helpful and nice. Though I did not find anyone to be particularly interested in selling the company. The interviewers were hard but fair for the most part. One interviewer did not describe the problem particularly well and had me coding a solution to the wrong problem for a while.

      Interview questions [1]

      Question 1

      General algorithm questions. particularly focused on algorithmic complexity. Know average and worst case time for operations on hash tables, trees, etc. The questions are not puzzles and if you know your data structures, algorithms, etc, they aren't too hard.
      Answer question
      2

      Other Software Engineer interview reviews for Google

      Software Engineer Interview

      4 May 2014
      Anonymous employee
      Auburndale, FL
      Accepted offer
      Positive experience
      Difficult interview

      Application

      I applied through an employee referral. I interviewed at Google (Auburndale, FL) in Apr 2014

      Interview

      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."
      2501

      Software Engineer Interview

      4 Jun 2026
      Anonymous interview candidate
      Warsaw, Masovia
      No offer
      Positive experience
      Average interview

      Application

      I interviewed at Google (Warsaw, Masovia)

      Interview

      remote round - on the same day, 45 minute technical interview, then 45 minute behavioral interview. there was also plenty of time to ask questions afterwards, so be prepared at least three or so to show interest

      Interview questions [1]

      Question 1

      a list of ranges like [0,1], [2, 5], ... . create a class with methods to find if element is in any range and insert a new range
      Answer question

      Software Engineer Interview

      4 Jun 2026
      Anonymous interview candidate
      New York, NY
      No offer
      Positive experience
      Difficult interview

      Application

      I interviewed at Google (New York, NY)

      Interview

      Didn't pass the phone screen. It was a leetcode medium question. I think I got it right, but maybe I was too slow in finishing the problem. Maybe it was something else

      Top companies for "Compensation and Benefits" near you

      avatar
      Amazon
      3.7★Compensation and benefits
      avatar
      Meta
      4.6★Compensation and benefits
      avatar
      Amazon Web Services
      3.9★Compensation and benefits
      avatar
      Booking.com
      4.2★Compensation and benefits