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

      22 juill. 2016
      Candidat à l'entretien anonyme
      Zurich
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 5 mois. J'ai passé un entretien chez Google (Zurich) en juill. 2016

      Entretien

      I was approached by a recruiter through LinkedIn. We first had an informal call, whereby after some general chat he asked me if I'd like to proceed to a tech part, which I did. There were a sequence of questions related to networking, processes, and linux administration, but not deep-diving, more like probing the overall orientation. After this call we agreed to follow up with a tech interview call. The tech call included two relatively involved but still fairly easy questions related to navigation through tree and graph data structures. The next day I was called and invited directly to an onsite. The onsite consisted of five whiteboard problem solving sessions, with a lunch in between. The coding tasks were fairly easy, but the interviewers did not ask to optimise the solutions, which turned out to be the killing point, as they expected me to be proactive and suggest improvements without asking. There also was a NALSD session, and a troubleshooting one. Both of which apparently went worse than they expected, though also better than I anticipated, given hardly any previous experience. Overall, the process was very smooth, with Google showing amazing patience for my limited availability. The recruiters were very friendly, the interviewers very kind, and the questions interesting and challenging. I did catch one of the interviewers on not really knowing the details of the internals he was asking about, which surprised me, as did the outcome, since they were a bit picky while showing some ignorance themselves. Nonetheless, I feel they were all very engaged, experienced, smart people, genuinely interested in learning about my skills. The entire process took a long time, but that was because I specifically asked them to wait for me to be available, which they did without any complaint, what I can only wholeheartedly admire.

      Questions d'entretien [1]

      Question 1

      I haven't signed any NDA, but was informally asked not to share the questions. You need to refresh your algorithms and data structures, system administration, and coding skills, as well as get familiar with the SRE type of work, problems, etc, best if you can get grip of their recently released book (check with O'Reilly).
      Répondre à cette question
      7

      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