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

      19 mars 2014
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 mois. J'ai passé un entretien chez Google en févr. 2014

      Entretien

      I had applied through their job portal online. I was contacted by the first recruiter in January 3rd week. We exchanged emails, she had me fill out a couple of forms, and then I was handed over to another recruiter. She, in turn, handed me over to yet another recruiter. The recruiter coordination was not good, their responses were all over the place. Two recruiters were working in tandem to schedule my phone interview and they managed to convert the interview time from PST to my local time with an 1hr error. This ended up with me waiting for the phone screen call one hour earlier than it actually was. I had given up and decided that the person would not call and then I receive a call 1 hour later. The interview itself was appallingly conducted. First of all, the interviewer seemed to be in a room with a lot of echo. Second, he must have been using some kind of phone system on speaker or something similar because I could hear my own voice echoed back. I mentioned this to him twice, since it made it difficult to hear his words with the reverberation in the room blurring his voice and my voice echoing. The first time, he said I must be using a headset and that the microphone was too far away from the mouth. I told him that I wasn't using a headset. He waved it away. The second time, he said the same thing. By then I had given up on the interview. I couldn't hear much, he wasn't helping. Trying to decipher the conversation and trying to code simultaneously had become a horrible adventure. Besides, he wasn't listening to half of what I'd said, be it trying to explain my problem-solving method or be it my concern regarding the fact I couldn't hear much over the garble. Some of the start-off questions (break-ice questions) he had asked regarding my resume were pointedly patronizing or so I felt. I understand however that a phone screen doesn't give you enough indicators about these things and I could be wrong. The questions themselves were basic programming, then some threading, concurrency, map-reduce trivia questions. I understand many people have the ambition or life-goal to work for the company. Perhaps to them this process might be forgivable. Most interviews probably aren't like this and I might have had something of an exception. I consider it disrespectful of my time and an unwillingness to listen to what I could potentially provide.

      Questions d'entretien [1]

      Question 1

      nothing too difficult, many trivia questions
      Répondre à cette question
      3

      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

      25 juin 2026
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Google (Londres, Angleterre)

      Entretien

      Had an intro screening call. They were mostly interested in how well I could code in python and java. They did not give me a follow up interview. I enjoyed my experience.

      Questions d'entretien [1]

      Question 1

      What is your favourite programming language
      Répondre à cette question

      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