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

      15 mai 2010
      Candidat à l'entretien anonyme
      Santa Monica, CA
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 3 mois. J'ai passé un entretien chez Google (Santa Monica, CA) en févr. 2010

      Entretien

      Recruiter started off professional. Originally contacted by someone in Mtn View and then transferred to someone in Santa Monica. Phone interview was intense, but I did my best. I felt like I got most of the questions wrong. My interviewer walked me through any incorrect answers and overall it was a pleasant experience. The interviewer was very good. Most of my questions were about searching and sorting, about half of them were the stupid questions from their database. He asked a good 10-15 questions during our phone call but most were short. Unlike most people, for some reason I was not asked any coding questions. The on-site interview was a disaster. 1. It started with a discussion of my thesis topic which was fine. Expect them to understand your topic no matter how esoteric or specific it is. 2. A second interviewer asked about my thesis. He did not like my topic at all claiming that it doesn't scale well. Well, excuse me for not having access to Google's data! Then proceeded to ask some dumb questions (specific to Java) from their database. Finally, I started coding on the board. If I did something wrong, he was very misleading in the "hints" that he was trying to give; he could not articulate what the problem was with my code. 3. I had lunch with my phone interviewer. It went fine, but Google food is not all it is cracked up to be. The others that I met during lunch seemed stressed out, but friendly. 4. No comments on next interviewer as he was pretty good. 5. HORRIBLE interviewer. Very arrogant, very condescending, very intimidating. He asked a very esoteric question that was very confusing and required me to read a manual before attempting to answer the question. He was very rude and mean to me and made it clear that he did not want to be there. I really just wanted to walk out of the room. 6. At this point I was shot. This interviewer asked me a question and while I was coding, I did something wrong. She said the problem was giving her a "headache" so we would move on to something else, just like that. The next question was better and was more pleasant. My recruiter told me to use whatever language I was most comfortable with. I specifically asked if I could use Python and she said "yes". I know Java, C and C++ but they are not my everyday languages. To my dismay, most of the questions were phrased "Used Java" or "Use C, C++ or Java" or "use C or C++". One of my interviewers did not even know Python. My first recruiter KNEW point blank that Python was my everyday language and said that was perfect for this interview. Apparently, I should have never even been recruited since I do not program in Java/C/C++ as an everyday thing. I was also told that the interview is about how you "think" which is not at all true. You need to know very specific things about algorithms, design patterns, and object-oriented programming, so read books before the interview. I was told that I would hear within a week. I never did. I had to call the recruiter and she pretended that she was going to tell me my result that day anyway. The recruiting process is wrought with bad information and too much power is given to the recruiters. Until they get this right, they will continue to hire the mediocre people that I have read so much about.

      Questions d'entretien [2]

      Question 1

      How would you sort 10 million phone numbers?
      3 réponse(s)

      Question 2

      How would you implement a singleton in the language of your choice?
      Répondre à cette question
      5

      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

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

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Google (Mountain View, CA)

      Entretien

      I was a bit nervous since it was my first big interview with a company like this. Wish I could of done better, but thats all learning experience for next time.

      Questions d'entretien [1]

      Question 1

      "Design and implement an LRU cache supporting get and put in O(1) average time".
      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
      Meta
      4.6★Rémunération et avantages
      avatar
      LinkedIn
      4.0★Rémunération et avantages