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 Developer 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 Developer

      7 déc. 2010
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Google en nov. 2010

      Entretien

      I had a pretty frustrating interview experience with Google, in particular with their recruiter. I applied online and a Google recruiter contacted me about a week later asking if we could talk over the phone about openings at Google. I replied immediately, but it took nearly 2 weeks for him to respond to my email (I even pinged him a week later, but no repsonse). He scheduled a call, and I took that afternoon off from work for the interview. He didn't call. I emailed him about half an hour after the scheduled time to make sure I had the right time. No response. A week later, he finally emailed again saying he could do the call the next day. No apology or explanation. Finally, we had the call and it wasn't even an interview. He just explained the process (which I'd read all about online) and asked if I had any questions. No questions about my background or resume. We setup a phone interview for a week later. The phone interview was about average (except again, no questions about my background or resume - straight into technical questions). I work for one of the big software companies & have conducted several technical interviews myself. The interviewer was pretty good, although there was one question in particular that he didn't explain very well and it took a couple of minutes to clarify what he was looking for. He started with a couple of C++ questions about the "static" keyword and about threading/deadlocks. He then went into coding questions. He didn't ask me to code anything, just to come up with the algorithms, and give the complexity in big O notation. We went through about 5 such questions, most of which had follow up questions to see if I could make a more efficient algorithm given different assumptions. I was getting positive feedback and felt that I did quite well. I felt it was at least a very good sign that we went through so many questions. About a week after the interview, I emailed my recruiter a quick message that politely asked if he had heard anything back about the interview and to inquire how long it would typically be until I got an answer. No response. Another week went by, and no response, so I followed up again. Nothing. After more than 3 weeks, I emailed another recruiter who had helped setup the phone screen, asking if she could do anything for me. About 15 mins later, Jeff called back and said that they decided I wasn't a good fit. I asked for any bit of feedback, but citing confidentiality, there wasn't a single bit of information he could give me. He asked me to contact him if "anything changes in my situation". Not sure what that means, since I have no clue why I wasn't hired in the first place. I currently work at another major software company which is just as competitive, and I have earned the highest possible achievements in every annual performance review. I am even in a leadership program for the top % of employees. But apparently not good enough to pass the first Google phone screen :) What bothered me most was not the no-hire. I understand that the Atlanta office only a very small number of developers. Not getting any feedback or reason for the no-hire was frustrating, but the most upsetting was the way I was treated by the recruiter during this whole process. His time was clearly much more important than my time. Spending 30 seconds to reply to an email was asking too much. I don't think I will be applying for a job at Google again.

      Questions d'entretien [1]

      Question 1

      Describe a situation in which you could have a deadlock in an application with only one thread.
      Répondre à cette question
      1

      Autres retours d’entretien d’embauche pour un poste comme Software Developer 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

      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

      Entretien pour Software Engineer

      9 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      First call with recruiter. Mainly resume questions nothing too technical. Then methods round, was a tagged question from leetcode. Interviewer pushed back on first design and steered me to the optimal solution.

      Questions d'entretien [1]

      Question 1

      Why are you leaving your current role.
      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