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

      6 juin 2011
      Candidat à l'entretien anonyme
      Santa Monica, CA
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      Le processus a pris 5 semaines. J'ai passé un entretien chez Google (Santa Monica, CA) en avr. 2011

      Entretien

      I was contacted by a recruiter from Google Southern California (Irvine and Santa Monica) through LinkedIn and was asked if I had any interest in applying to Google. I replied yes and then had a phone call with the recruiter (about 40 minutes) to talk about my background and experience, and the recruiter talked about the interview process and answered all my questions. The recruiter was amazingly nice and very easy to talk to. The first thing I had to do was choose an office to apply to. I chose Santa Monica and asked for 2 weeks to study before the first phone interview. Two weeks later I had the phone interview. I was very nervous but my nerves calmed down as soon as I started talking to the interviewer, he was friendly and the interview felt more like we were a team working on a problem together rather than an interview (to some extent). It was very casual and the problems were interesting. The interviewer gave me a few tips and clues when I got stuck, but overall I felt like I did pretty well. One week later, the recruiter contacted me to announce I passed the phone interview and was invited to an onsite interview at the Santa Monica office. The onsite interview was scheduled for a week after that (so 2 weeks after the phone interview). I arrived at the building, but they have 3 buildings and I showed up at the wrong one! Way to make a good first impression, I felt so stupid. So if you have an interview there, make sure to follow the directions they give you by email instead of googling "Google Santa Monica" for the location. The onsite interview consisted of five 45 minutes 1:1 interviews back to back with a lunch with an engineer in the middle. Four of the interviewers were male software engineers in their early 30s, one was older (50s). All of them were nice and friendly and made the experience very pleasant. All but one of the interviewers made me feel like I was already part of the team and that we were just working together on a problem. The lunch was a little more awkward. The guy was older than me (50s) so we didn't have much in common (I am in my late 20s) and he was very hard to talk with. I had some questions and conversation topics ready to make sure the lunch would go smoothly, but I ran through all my questions in about 10 minutes because he only answered with "yes", "no", or a few words. He never asked me anything or made any effort to keep the conversation going. You could tell he was a nice guy, nothing wrong with him, just not a talker. Seems like a weird choice for a interviewee lunch, the whole thing felt like an uphill battle against awkward silence. The lunch was probably the most stressful part of the whole interview day! At the end of the day, I left the onsite interview feeling confident and happy. The problems had all been interesting and I really did enjoy most of the interviewers. One week later I received an email from the recruiter saying I was not selected for the job. I think I did pretty well, I guess I was not quite quick enough with my answers.
      7

      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

      7 juin 2026
      Candidat à l'entretien anonyme
      Los Altos, CA
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (Los Altos, CA)

      Entretien

      Went with an OA which was pretty easy. Then got to second round (1 coding and 1 behavioral). Both were pretty straight forward. Then got to the onsite. They asked me leetcode hard questions. I was able to do well in one but failed the other one.

      Questions d'entretien [1]

      Question 1

      Why do you want to work at Google?
      Répondre à cette question

      Entretien pour Software Engineer

      7 juin 2026
      Employé (anonyme)
      Seabrook, NH
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Google (Seabrook, NH)

      Entretien

      Had a good interview. Easy problems not leetcode but if you know how to solve problems and use which DSA to use for what problem then you are good.. system design as well.

      Questions d'entretien [1]

      Question 1

      Tell me about yourself ?
      Répondre à cette question