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 sept. 2011
      Employé (anonyme)
      Mountain View, CA
      Offre acceptée
      Expérience neutre
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris plus de 2 mois. J'ai passé un entretien chez Google (Mountain View, CA) en août 2011

      Entretien

      I've been contacted by their recruiters every 6 months or year for the past 6 or 7 years. Finally I was in the right place in my career to actually interview there, so I agreed. The first step was a phone interview. The recruiter suggested a whole lot of studying material. I kinda skimmed "Programming Interviews Exposed", but I don't think it really made much of a difference at any point in the interview process. I feel like you either know your CS fundamentals or you don't and reading a book about them at the last minute isn't going to help much. Maybe I'm wrong. This is my best tip for interviewing!: don't just discount your first answer because you think it's "too obvious"! It very well might be the right answer, and now you'll be lost searching for an even better answer that doesn't exist! If you think it's not right, just say "there might be a better way to do this, but I'm just brainstorming", and then explain what you're thinking. If there's a better way to do it, they'll let you know. I made this mistake twice in my interviews. First there was a 45 minute phone interview. It was just two questions, one coding, and one more conceptual. It was pretty straightforward. The coding one was just something basic like implementing a binary search with a few tweaks. Despite all the scary things people say, I felt like the in-person interview wasn't especially difficult, but I probably just lucked out with the group of interviewers I pulled. My friend told me he knows a ton of really smart people who didn't pass the in-person, so I shouldn't take it personally if I didn't either. That helped me relax and realize I just had to go in there and do my best and see what happened. I wasn't really nervous then and the interview mostly just felt like I was discussing interesting problems with co-workers. I think being relaxed really helped me get the job, so if you can... chill out. :) Then things got really boring. At this point, it had been six weeks since I first started talking to the recruiter. Within three days, I was told that I'd passed the hiring committee. And after the I didn't get the offer for FOUR AND A HALF MORE WEEKS. That's 2.5 months total. The recruiter was very nice and apologetic about the whole process, but I feel like they need to do something to speed it up. It was a frustrating experience, knowing I'd passed the hiring committee and was probably hired, but then things just kept getting held up for weird reasons passing through all the other processes. When the offer finally came, however, it was a good offer and I accepted immediately.
      10

      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

      3 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      Etapa de RH para filtragem de curriculo e fit inicial, e Screening Técnico com código em leetcode focado em algoritmos, onde o código era feito em um bloco de notas, sem uso de IDEs.

      Questions d'entretien [1]

      Question 1

      Você conhece sobre Big O notation?
      Répondre à cette question

      Entretien pour Software Engineer

      3 juin 2026
      Candidat à l'entretien anonyme
      Mountain View, CA
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Google (Mountain View, CA)

      Entretien

      Round 1 consists of coding and behavioural interviews. In behavioural, it was basic questions; it can be found online, so make sure you have all the stories ready. For DSA, it was a pretty much easy question related to Intervals or Heaps, don't want to reveal the questions directly!!

      Questions d'entretien [1]

      Question 1

      DSA question based on Intervals, Heaps
      Répondre à cette question

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      Amazon
      3.7★Rémunération et avantages
      avatar
      Mercado Livre
      4.3★Rémunération et avantages
      avatar
      Meta
      4.6★Rémunération et avantages
      avatar
      Despegar.com
      3.6★Rémunération et avantages