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

      22 juil. 2012
      Employé (anonyme)
      Mountain View, CA
      Offre acceptée
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Google (Mountain View, CA) en janv. 2011

      Entretien

      I was contacted by a YouTube recruiter by phone - presumably after he saw my resume on LinkedIn. After a phone screen, I was called in for a round of in-person interviews. It was around 6 people over about 4 hours. From my understanding, Google usually goes through multiple on-site interviews, but since I already had an offer from a major competitor, I convinced them to speed up the process and make do with only one on-site. I got the offer about 2 weeks later and accepted it. The questions were standard CS algorithm/design/coding questions, but cumulatively were definitely the hardest round of questions I've ever faced. I don't remember them any more, but they really made me think. Google lives up to it's tough-as-nails-interviews reputation.

      Questions d'entretien [1]

      Question 1

      The phone screen was the hardest. It was something that involved two separate concepts - one was a dynamic programming algorithm and the other was a trie data structure - and somehow combining them to make up the answer. I don't remember the exact question, but somehow it involved storing the words in a dictionary into the trie structure and then using the algorithm to determine something...
      Répondre à cette question

      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

      15 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      There are two back-to-back rounds, the first is a code interview, and the next is a BQ interview. I think my interviewees gave me positive feedback, and they are nice.

      Questions d'entretien [1]

      Question 1

      Asked me a question to design a function to find a simpler Wordle game.
      Répondre à cette question

      Entretien pour Software Engineer

      12 juin 2026
      Candidat à l'entretien anonyme
      Offre refusée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      3 rounds of coding + 1 behavior Questions from leetcode google question bank, mostly medium level questions, ask about complexity. Interviewers are generally nice, there are no test cases but need to write ur own tests and think of the edge cases.

      Questions d'entretien [1]

      Question 1

      For behavior describe a project u have worked on
      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
      Amazon Web Services
      3.9★Rémunération et avantages
      avatar
      TikTok
      3.6★Rémunération et avantages
      avatar
      Meta
      4.5★Rémunération et avantages