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

      27 mai 2014
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Google (New York, NY) en mai 2014

      Entretien

      I applied and was contacted by a recruiter within 2 days. I was given a long checklist of things to review and told I would be given a phone interview in about 10 days. I prepared quite a bit, but there's only so much you can do. You have to be a little lucky with who you get and hope you both find the same topics important. That said, I've been told the interview process at Google is a bit silly and I have to agree. It did not feel very kind, at least. My interviewer started with "Hi I'm an Engineer at Google and you have an interview schedule for this time. Is this still a good time? Okay good. Let's start with the following question: ". Very little small talk, straight into a coding question. Okay, no prob. Except I could hear him typing away on his keyboard the whole time. There was basically zero commentary while I was coding, and nothing to say about my "thinking out loud". I completed the question, perhaps it took a bit longer than it should have, but it's an interview....nerves are gonna play a part. Anyway, I was definitely being scored on a timer. There is little doubt about that in my mind. If I wasn't given a timed score, then I lost points for there not being enough time to get around to other questions. He did go through it line by line, and I fixed all the little mistakes (which of course never would have happened in an IDE) and wound up with some decent code. It wasn't the best thing in the world, but it was fast and it worked. After the weekend I was told they would be going with some more experienced candidates. So again, little doubt in my mind that my score was somehow lessened due to the amount of time I took on the problem. I didn't sit and do nothing, I just wrote out code, then replaced it with something cleaner or better. Moved some sloppy stuff into a new function, etc.

      Questions d'entretien [1]

      Question 1

      Google asks that we do not share their questions, so I won't share the entire thing. I will however say that it was a common question (Think along the lines of reverse a string, calculate fib sequence, etc) with a little twist thrown in which should just cause you to hesitate and think a bit, even if you've seen the core of this problem before. It was by all means a fair question.
      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

      23 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      2 rounds of interviews with the first round being a technical and a behaverial. The second round being two technicals. The format was straight forward and the interviewer was professional.

      Questions d'entretien [1]

      Question 1

      Talk about how you resolve a conflict.
      Répondre à cette question

      Entretien pour Software Engineer

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

      Candidature

      J'ai passé un entretien chez Google

      Entretien

      There was a technical screen within their coding platform, followed by a first-round technical interview, followed by a first-round behavioral interview, followed by second-round interviews, both technical and behavioral interviews.

      Questions d'entretien [1]

      Question 1

      What was your role on a technical project you've worked on?
      Répondre à cette question