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 interviewsGoogle Site Reliability 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.

      Site Reliability Engineer Interview

      28 Oct 2011
      Anonymous interview candidate
      Mountain View, CA
      No offer
      Neutral experience
      Average interview

      Application

      The process took 3 weeks. I interviewed at Google (Mountain View, CA) in Oct 2011

      Interview

      Ever since I joined LinkedIn, I've been receiving emails from Google recruiters. I replied to the first one saying that as I'm an established contractor with my own company its difficult to switch to permanent employment. The emails kept coming in on a monthly basis. After around a year, I was on the look out for something different so I decided to look into it. The job description looked interesting and matched the work I'd been involved with in the previous years. I had the initial pre-screening which had some technical questions and we discussed the role a little. A week later I was offered a technical phone interview. It started with one question, which kept getting expanded until it covered a wide range of topics. It was clear they were after someone who knew how to approach a new problem, rather than someone who had memorized a bunch of commands suitable only for a particular situation. I felt it went really well, except at the end when I made some silly mistakes, but it was 10pm on a Friday, so I'm sure most people wouldn't be completely switched on at that point. Over all the interview was positive - it was relevant to my skills and the questions were fair. A few more days passed and I got an email saying that they don't have any jobs which match my qualifications, with the usual "thank you for your interest in our company etc.." Not knowing what that really means, I wrote back asking for a reason, and feedback on the technical interview. I explained where I thought I went wrong, and asked if that was the issue. I only got another email thanking me for my interest in the company and to try again in a few months. As I only had the technical interview, I was expending something like... "we need someone with more experience/knowledge in xxx", or "someone who has used xxx for xxx years". I did get the impression from the emails that there actually was no job available which was waiting to be filled, but they are constantly on the lookout - in the same was that job agencies sometimes post bogus jobs on job boards to get candidate information, and find out where gaps are in the job market. I fail to see how applying again in a few months will change things as I'm not sure what went wrong, so will probably make the same mistake again, unless asked exactly the same questions.

      Interview questions [1]

      Question 1

      Topics: Filesystems, networking, scripting I will not write the question
      Answer question

      Other Site Reliability Engineer interview reviews for Google

      Site Reliability Engineer Interview

      2 Mar 2026
      Anonymous employee
      Waterloo, ON
      Accepted offer
      Positive experience
      Difficult interview

      Application

      I interviewed at Google (Waterloo, ON)

      Interview

      HR round after applying, then coding screening round, if passes, then final round which consists of four coding round or three coding and one design round. Problem difficulty medium to hard.

      Interview questions [1]

      Question 1

      Complexity of the solution I provided.
      Answer question

      Site Reliability Engineer Interview

      11 Apr 2026
      Anonymous interview candidate
      Zürich
      No offer
      Positive experience
      Difficult interview

      Application

      I applied online. I interviewed at Google (Zürich) in Mar 2026

      Interview

      Frist had one roughly 20 to 30 minutes screening call with a recruiter, then had one online 45 minutes technical interview with a Google Site Reliability Engineer. The technical interview covered data structure and algorithm topics.

      Site Reliability Engineer Interview

      7 Apr 2026
      Anonymous interview candidate
      Dublin, Dublin
      No offer
      Positive experience
      Difficult interview

      Application

      I applied online. I interviewed at Google (Dublin, Dublin) in Mar 2026

      Interview

      The interview lasted 45 minutes and was conducted one-on-one. I was required to walk through my thought process before coding and then implement an optimized solution with a focus on time complexity.

      Interview questions [1]

      Question 1

      They asked me a string based question
      Answer question