Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Google

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Google | Offres d’emploi chez Google | Salaires chez Google | Avantages sociaux chez Google
      Entretiens chez GoogleEntretiens d’embauche pour Site Reliability Engineer chez GoogleEntretien chez Google


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Site Reliability Engineer

      9 déc. 2016
      Candidat à l'entretien anonyme
      Sydney
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez Google (Sydney) en sept. 2016

      Entretien

      I was poached by a recruiter who felt my skills aligned to SRE. I had a total of four interviews - an initial behavioural interview, a theoretical technical, a phone screen coding and finally an on-site. The whole process took about 2 months. In my experience, Google tried to make the entire thing extremely smooth and 'fair'. They make you feel super special and give you a lot of information, study material and time to do your best. They basically tell you what to study. The first 'technical' was sort of a gauge of my skills. I was asked a bunch of basic comp sci questions as well as other SRE fields that may be important e.g. O/S and Networking questions. I didn't have to do great in all of them but I'm guessing doing generally well in at least one area is important - I got all the programming/comp sci questions correct as well as a good amount of the O/S questions. The coding phone screen was actually not so hard. I think they focus on what you claim you were good at - in my case it was Java. The on-site was the 'hardest', however, I'd say overall it was fair. The questions were pretty much CTCI style and I didn't get anything too difficult. But I messed up the first round because the guy who interviewed me was a classic elitist and whenever I asked him questions he made me feel extremely stupid. He was getting noticeably frustrated and at the end walked out with a passive aggressive: "Well, good luck with the rest". The rest were *okay* except for the system design question. I was smashed with a sort of math-driven question with a bunch of numbers and components which really threw me off. I did terrible for this part and I knew it was over for me at this point. I got a rejection email about a week later and was lucky enough to receive feedback. I can see where I went wrong. My advice to candidates is study extremely hard, focus on the important areas they hint to you, and finally - don't feel bad if you don't get it. I was told by the guys who gave me system design interview that probably close to 50% of the employees at Google applied twice before they made it.

      Questions d'entretien [1]

      Question 1

      Basic CTCI style questions - mostly around data structures System design question with lots of maths and 'numbers everyone computer scientist should know'
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Site Reliability Engineer chez Google

      Entretien pour Site Reliability Engineer

      2 mars 2026
      Employé (anonyme)
      Waterloo, ON
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (Waterloo, ON)

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Complexity of the solution I provided.
      Répondre à cette question

      Entretien pour Site Reliability Engineer

      11 avr. 2026
      Candidat à l'entretien anonyme
      Zurich
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Google (Zurich) en mars 2026

      Entretien

      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.

      Entretien pour Site Reliability Engineer

      7 avr. 2026
      Candidat à l'entretien anonyme
      Dublin, Dublin
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Google (Dublin, Dublin) en mars 2026

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      They asked me a string based question
      Répondre à cette question