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 Software 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 Software Engineer

      18 oct. 2010
      Candidat à l'entretien anonyme
      Mountain View, CA
      Offre refusée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Google (Mountain View, CA) en juin 2008

      Entretien

      Google has a similar interview process to the other major tech companies. Their questions are very smart and designed to test computer fundamentals while giving the interviewer an easy time of making a hire/no-hire decision. The questions get progressively harder as the day progresses. Starting from simple problems like "you're trying to recover a machine, you're in single user mode, /etc/passwd is corrupt, but none of your text editors are working on the boot image due to shared library issues. how would you rebuild /etc/passwd?" they quickly progressed to divide-and-conquer approaches to merge sorting data too large to fit in memory and other standard coding puzzle questions.

      Questions d'entretien [2]

      Question 1

      How would you restore /etc/passwd on a machine with a corrupt root disk which is only barely functioning. You have a shell and most unix shell commands, but no text editors.
      2 réponse(s)

      Question 2

      How would you sort a file which is too large to fit in memory.
      3 réponse(s)

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

      Entretien pour Software Engineer

      4 mai 2014
      Employé (anonyme)
      Auburndale, FL
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Google (Auburndale, FL) en avr. 2014

      Entretien

      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

      Entretien pour Software Engineer

      4 juin 2026
      Candidat à l'entretien anonyme
      Varsovie, Mazovie
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Google (Varsovie, Mazovie)

      Entretien

      remote round - on the same day, 45 minute technical interview, then 45 minute behavioral interview. there was also plenty of time to ask questions afterwards, so be prepared at least three or so to show interest

      Questions d'entretien [1]

      Question 1

      a list of ranges like [0,1], [2, 5], ... . create a class with methods to find if element is in any range and insert a new range
      Répondre à cette question

      Entretien pour Software Engineer

      4 juin 2026
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (New York, NY)

      Entretien

      Didn't pass the phone screen. It was a leetcode medium question. I think I got it right, but maybe I was too slow in finishing the problem. Maybe it was something else