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

      22 févr. 2014
      Candidat à l'entretien anonyme
      Mountain View, CA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez Google (Mountain View, CA) en janv. 2014

      Entretien

      I was first contacted by Google in 2012 a couple months after I took up current employment. This recruiter was energetic, interesting and seemed genuinely interested in finding the right spot for me at Google. Unfortunately, I had just started my new job and have a personal policy of staying at a place of work for at least a year. That, and the project was interesting and exciting so I did not follow up and let him know why. Time passed and eventually he moved on from Google. About a year later another recruiter contacted me. She seemed nice but nowhere near as enthusiastic. We setup a time to talk over a Hangout but unfortunately she cancelled at the last minute. Not good, I'd changed my plans around to fit. So I agreed to her request to setup a new Hangout the next week. Nothing happened. After about two weeks (I waited due to work commitments) I got back in contact with her and we worked out a new time and the interview went ahead. She was courteous and seemed reasonably enthusiastic, but nothing like the previous guy who had a specific position in mind. No, this was now very open ended, non-specific and I started to feel like just another candidate. Despite this I decided to see where it went. So a technical phone interview was setup and it was possible one of the worst phone interviews of my career. I could not hear a thing. The call quality was terrible. This made it extremely hard to hear what I was even supposed to be doing. Fortunately, the Googler on the other end was very helpful, polite and understanding. We eventually nutted out what he wanted me to do via Google Docs. Then I waited over two weeks for feedback. I passed the interview but then I was transferred unceremoniously to recruiter the 3rd. This guy was even less enthusiastic but communication was clear and to the point. He ignored my request to talk to him over Hangout. But, the second interview got organised with a team I was interested in. The second interview however was far worse than the first. Call quality was better but still not great. Worse still however was the interviewer who, seemingly, had zero interest in being there. He explained what he was looking for, a basic problem, and for the rest of the interview ignored most of my questions. I was trying to talk through the problem, explain what I was doing and also try and see how he would work with me. From what I heard I'd expected this from a Google interview. And indeed, the last interviewer was great. However, this guy did not answer my questions - aside from some grunts - and seemed more worried that I wasn't using STL. I told him I just wanted to keep it simple as it was a simple question. Did I forget to mention that he was a full 15 minutes late to the interview? I cannot stand this and it is disrespectful and very tardy. Also, the question asked had nothing to do with the specific position I was interviewing for. In the end, I've no doubt I gave a sub-optimal impression on my second interview. But what do you expect from a sub-optimal interview? Garbage in, garbage out. So in the end I did not get an offer. While I understand that I am perhaps in the minority here as far as Google interviews go I can see from the stats that I am certainly not alone. From my experience I can only conclude that Google does not take its recruitment seriously and it has big issues with process.

      Questions d'entretien [1]

      Question 1

      They were only of average difficulty.
      Répondre à cette question

      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

      23 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Talk about how you resolve a conflict.
      Répondre à cette question

      Entretien pour Software Engineer

      24 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      What was your role on a technical project you've worked on?
      Répondre à cette question