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 & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Google reviews | Google jobs | Google salaries | Google benefits | Google conversations
      Google interviewsGoogle Software Engineer interviewsGoogle interview
      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 personalized job recommendations and updates by starting your searches.

      Software Engineer Interview

      Jul 24, 2015
      Anonymous Interview Candidate
      No offer
      Negative experience
      Difficult interview

      Application

      I applied through a recruiter. The process took 2 months. I interviewed at Google in May 2015

      Interview

      I applied to Google and Facebook at roughly the same time. Although I did not get any offer, interview at Facebook was professional and friendly, and at the end I learned about my strong and weak sides. Interview at Google was the opposite of that. 1. Recruiter sent me an email asking when we could talk. I answered specifying when I have time for a phone call. Then there was over a week of silence, and finally recruiter called me on different hour that I specified. He said that he has one possible date for phone interview, so I accepted. 2. My first phone interview did not happen, because interviewer did not show up. Interview was rescheduled. 3. Second interview went smoothly. I answered all the questions, and interviewer seemed satisfied with the answers. 4. The same day recruiter called me and said that my evaluation was inconclusive and we need another phone interview. I asked for technical feedback, but I was not given any. The only information that I received was that "my solution was not good enough". 5. Second interview went similar to the first one. Again I answered all the questions. This time interviewer even said that he is satisfied with my answers. 6. After a week recruiter called me and said that evaluation was inconclusive again, and this ends recruitment process. I asked for technical feedback, and he said that he does not have any, but he will contact me when he get one. 7. After two weeks without information, I tried to contact my recruiter by email. Then again by phone. 8. After a month I received anonymous survey about my interview experience. I used it to complain about lack of information from recruiter and the fact that I still do not know why I was rejected. 9. The next morning I got a call from my recruiter. He apologized for not contacting me earlier and gave me technical feedback from my two interviews. I learned that first call I failed because my solution was not optimal (it was O(N log N) when O(N) was possible). On the second call I implemented optimal algorithm, but there were several issues with implementation that led to lowering my evaluation to "neutral". And two neutral opinions are not enough to qualify. Overall, recruiter never answered any of my emails, and each time we talk he was condescending and unfriendly. Overall it was frustrating and disheartening experience.

      Interview questions [1]

      Question 1

      Sort lines in very large file (large enough that it does not fit into memory).
      1 Answer
      2

      Other Software Engineer Interview Reviews for Google

      Software Engineer Interview

      May 4, 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."
      2502

      Software Engineer Interview

      Jul 16, 2026
      Anonymous Interview Candidate
      Tel Aviv-Yafo
      No offer
      Neutral experience
      Difficult interview

      Application

      I applied through a recruiter. I interviewed at Google (Tel Aviv-Yafo)

      Interview

      fit was fair process, they ask me about my expiriance and 1 logic question. they interviwers was nice and guide me to the solution. at overall it war fair process.

      Interview questions [1]

      Question 1

      about my resume and expiriance
      Answer question

      Software Engineer Interview

      Jul 11, 2026
      Anonymous Interview Candidate
      Taipei
      No offer
      Positive experience
      Difficult interview

      Application

      I interviewed at Google (Taipei)

      Interview

      The entire process was quite lengthy, taking over six months from the initial contact to the team matching stage. It started when I reached out to the HR recruiter through a friend's referral. After an initial introductory call, the recruiter informed me that they would keep my resume in their talent database. About a month and a half later, they reached back out to schedule a technical phone interview. This round primarily focused on LeetCode-style algorithmic problem-solving. After passing the phone screen, the process moved forward to a behavioral interview followed by the full onsite rounds. I have passed all the performance bars, and the hiring committee has approved my packet. Currently, I am in the team matching phase.

      Interview questions [1]

      Question 1

      I had a total of three coding interviews. The first round involved a graph-related problem, which was quite unique and not a standard LeetCode question. The other two rounds focused on high-frequency LeetCode problems, but they came with substantial modifications and challenging follow-up questions.
      Answer question


      Glassdoor

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

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & 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. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Indeed, Inc.

      Google interviews FAQs

      • Software Engineer applicants have rated the interview process at Google with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 62% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
      • Candidates applying for Software Engineer roles take an average of 34 days to get hired, when considering 5,088 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 38 days.
      • Common stages of the interview process at Google as a Software Engineer according to 5,088 Glassdoor interviews include:

        Phone interview:  37%

        One on one interview:  22%

        Skills test:  17%

        Presentation:  7%

        Background check:  4%

        Personality test:  4%

        Group panel interview:  3%

        IQ intelligence test:  2%

        Other:  2%

        Drug test:  2%

      • Here are the most commonly searched roles for interview reports -

        1. Software Engineer(10530) ;
        2. Senior Software Engineer(1609) ;
        3. Intern(1236) ;
        4. Software Developer(1220) ;
        5. Account Manager(853) ;
        6. Product Manager(797) ;
        7. Software Development Engineer (SDE)(770) ;
    • Analyst(758) ;
    • Program Manager(630) ;
    • Project Manager(610) ;
    • SWE Intern(545) ;
    • Data Scientist(515) ;
    • Internship(502) ;
    • Software Engineer(Internship)(497) ;
    • Manager(485) .
    • Jobs at Google

      756 jobs in United States
      Software Developer, Android, Glasses System UI
      San Jose, CA
      ·
      $147K - $211K /yr
      (Employer provided)
      View job
      Software Engineer, On-Device Machine Learning
      Sunnyvale, CA
      ·
      $147K - $211K /yr
      (Employer provided)
      View job
      Staff Software Engineer, Agentic Data and Evals
      Sunnyvale, CA
      ·
      $207K - $301K /yr
      (Employer provided)
      View job
      Senior Software Engineer, AI/ML, NotebookLM Content Studio
      New York, NY
      ·
      $174K - $253K /yr
      (Employer provided)
      View job
      Senior Software Engineer, AI/ML, NotebookLM Content Studio
      Mountain View, CA
      ·
      $174K - $253K /yr
      (Employer provided)
      View job
      View all Software Engineer Jobs