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

      29 déc. 2009
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      Le processus a pris 8 semaines. J'ai passé un entretien chez Google en déc. 2009

      Entretien

      One of my friends was contacted by a Google recruiter. He was not interested in interviewing at the time, but gave my name to the recruiter, who emailed me and requested my resume. After receiving my resume, the recruiter arranged a 45min technical phone interview, which consisted of one "soft" question (e.g. describe a current project and its challenges), one algorithm question, one Java question, and one design question involving concurrency. The recruiter had previously mentioned there might be a second phone interview, but I did well enough in the first phone interview that my candidacy was forwarded to the on-site interviews. I had five on-site interviews, all of which focused on technical knowledge and problem solving skills. My lunch conversation was truly a conversation and not an interview - I was the one asking all the questions! :) Although I enjoyed the interviews themselves, lunch was a wonderful experience. It was great to see all the engineers sitting together talking and interacting. There was an incredible sense of community, friendship, and potential. (that sounds pretty weird, but it's really what it felt like) I was asked only two soft questions the entire day and was not asked any brainteaser or logic puzzle questions. There was more emphasis on Java knowledge than I expected. Even though I was not asked any brainteaser or logic puzzle questions, I feel like studying them helped me improve my technique in approaching a new problem.

      Questions d'entretien [2]

      Question 1

      Describe a current project. What was challenging about it? What did you learn from it?
      Répondre à cette question

      Question 2

      What is the relationship between equals(Object o) and hashCode() in Java? How would you implement each method?
      2 réponse(s)
      4

      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