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


      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. 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 personalized job recommendations and updates by starting your searches.

      Software Engineer Interview

      Jun 17, 2014
      Anonymous employee
      New York, NY
      Accepted offer
      Positive experience
      Difficult interview

      Application

      I applied through an employee referral. The process took 4 months. I interviewed at Google (New York, NY) in Apr 2014

      Interview

      My resume was referred by a current employee. I got a call from a recruiter a couple weeks later and had a 10 minute conversation with her about the whole process, bit on my background, and what I'm looking for. She sent me an email with all of the content that is considered fair game for an interview. I asked for a month to study before the phone interview. The phone interview was 45 minutes, with maybe 35 of it being technical questions and coding in a Google Doc. The recruiter called me later that day saying they wanted to bring me in for on-site interviews. I asked for them to be scheduled as soon as possible (already been studying, didn't want to forget anything). The on-site interviews were scheduled for almost 3 weeks later. My round of interviews on-site wasn't as smooth as the recruiter claims they usually are. I was taken to a small conference that was to be my "home" for the day and the recruiter wrote the schedule of who and when on the white board. The first guy that showed up was not the one listed. Second guy was 15 minutes late. Last guy of the day turned out to be working at home and they had to substitute on the fly (15 minute delay again). Not really a big deal, but I think worth noting. The interviews themselves were 45 minutes each, again about 35 - 40 minutes of which were technical questions and coding on the white board. All questions fell within the review content suggested by the email. One interview was more of a design/approach interview and np-complete did come up once. In general the questions were designed to be challenging, but solvable in the time-frame. To study, I read Wikipedia pages and took notes for the topics mentioned in the email. I used a couple other materials for design and integration patterns. This worked as sufficient review for me. My final comment is regarding how I think they determine level. I was out of undergrad for four years when I interviewed. My experience in the field is longer than that. The recruiter said for their purposes my level was "four years", which I think worked in my favor because they expected less.

      Interview questions [1]

      Question 1

      The design/approach interview was the hardest simply because it's far more open ended.
      1 Answer
      5

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

      Software Engineer Interview

      Jun 23, 2026
      Anonymous Interview Candidate
      No offer
      Positive experience
      Difficult interview

      Application

      I interviewed at Google

      Interview

      2 rounds of interviews with the first round being a technical and a behaverial. The second round being two technicals. The format was straight forward and the interviewer was professional.

      Interview questions [1]

      Question 1

      Talk about how you resolve a conflict.
      Answer question

      Software Engineer Interview

      Jun 24, 2026
      Anonymous Interview Candidate
      No offer
      Neutral experience
      Average interview

      Application

      I interviewed at Google

      Interview

      There was a technical screen within their coding platform, followed by a first-round technical interview, followed by a first-round behavioral interview, followed by second-round interviews, both technical and behavioral interviews.

      Interview questions [1]

      Question 1

      What was your role on a technical project you've worked on?
      Answer question