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

      17 déc. 2013
      Candidat à l'entretien anonyme
      Mountain View, CA
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Google (Mountain View, CA) en août 2012

      Entretien

      A recruiter reached out to me. Had an initial call with the recruiter to gauge my interests and my team preference at Google. Narrowed down to two teams. Had a couple of phone interviews, I guess the first one was on the fence. First phone interview was about API design and algorithm design. Second was for designing and coding an algorithm and verbally describe a game design. Second one went good enough to make me move to the next step. Primary recruiter handed me over to the secondary recruiter. It's clear that the primary recruiters are friendlier and take more time to get to know you better. Secondary recruiter didn't seem very enthusiastic. He setup my interview with with members of the two teams I had narrowed down with the earlier recruiter and referred me to a travel agency to setup the travel for the onsite interview. I was booked for a total of 5 interviews, 3 before lunch and 2 after. Lunch was in Google's cafeteria with another employee separate from the interviewers. Campus has a very nice college feel to it. Interview questions range in difficulty. When they see you are solving questions with ease, they turn it up a notch. I found a very heavy emphasis on graph algorithms in my questions. I was expecting it but not to this level, so better prep for those! esp. graph search algorithms and their variations. Lots of code writing on the whiteboard to the point where you run out of space! Had to design a data structure with certain properties and the interviewer kept asking for new methods. One of the interviewers had a thick accent and it was very hard to understand him. That was the only interview that I felt going bad because of the communication issues. Overall a positive experience. I got to brush up on a lot of things that I had forgotten since college.

      Questions d'entretien [1]

      Question 1

      Test line-of-sight in a game that accounts for obstacles to determine if the bad guy can see you or not.
      1 réponse
      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