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

      29 Apr 2010
      Anonymous interview candidate
      No offer
      Neutral experience
      Average interview

      Application

      I applied through an employee referral. The process took 3 days. I interviewed at Google in Mar 2010

      Interview

      Quick phone call with a recruiter to schedule two interviews. She asked me what language I'd like to be interviewed in. My recent experience is primarily C, but I was expecting to be given the sort of high-level algorithmic problems for which having to build my own data structures would be too time consuming, so I said I would prefer C++. We scheduled my interview to be two weeks away to give me some time to teach myself C++ and the STL. I was supposed to have two interviews on the same day, but one of the interviewers never called me. The one who did call was very friendly and intelligent, but I was caught a bit off guard that all he wanted to ask me were C string manipulation questions. I'd normally be good at this sort of stuff, but I was surprised and I panicked, and I didn't do as well as I should have. My other interview was rescheduled for a couple of days later. Once again, I really liked me interviewer. He asked me some higher-level algorithmic questions, with a bit of an AI bent to the them. Interesting stuff. It was interesting stuff, and I eventually came to the solutions he was looking for, but it took some prompting. In the end, I wasn't invited to a second round of interviews and I wasn't particularly surprised by this. There's a huge difference between writing your own code on your own time or even on a test in school and writing code with someone watching your every keystroke. I found it very stressful. The questions they asked me weren't particularly difficult, but the context in which I had to solve them wasn't something I was ready for.

      Interview questions [1]

      Question 1

      Design and write a sudoku solver.
      1 Answer

      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

      3 Jun 2026
      Anonymous interview candidate
      No offer
      Negative experience
      Difficult interview

      Application

      I interviewed at Google

      Interview

      Etapa de RH para filtragem de curriculo e fit inicial, e Screening Técnico com código em leetcode focado em algoritmos, onde o código era feito em um bloco de notas, sem uso de IDEs.

      Interview questions [1]

      Question 1

      Você conhece sobre Big O notation?
      Answer question

      Software Engineer Interview

      3 Jun 2026
      Anonymous interview candidate
      Mountain View, CA
      No offer
      Positive experience
      Easy interview

      Application

      I interviewed at Google (Mountain View, CA)

      Interview

      Round 1 consists of coding and behavioural interviews. In behavioural, it was basic questions; it can be found online, so make sure you have all the stories ready. For DSA, it was a pretty much easy question related to Intervals or Heaps, don't want to reveal the questions directly!!

      Interview questions [1]

      Question 1

      DSA question based on Intervals, Heaps
      Answer question

      Top companies for "Compensation and Benefits" near you

      avatar
      Amazon
      3.7★Compensation and benefits
      avatar
      OKG
      4.3★Compensation and benefits
      avatar
      SelfMade
      4.0★Compensation and benefits
      avatar
      Automattic
      3.8★Compensation and benefits