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. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      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 janv. 2015
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 3 semaines. J'ai passé un entretien chez Google en déc. 2014

      Entretien

      Contacted by a recruiter after a former co-worker from another company that is now in Google recommended me. First screening interview was on site since I live close to Google's offices in Tel-Aviv. Small algorithm/data-structure question with coding in C++ and a bit of STL. The interviewer was not very nice, snobish and condescending, yet I passed without any issues and was invited to a full on-site interviews day at a later date. The on-site interviews included 3 interviews focusing on algorithm/data-structures including a bit of coding. Nothing very difficult, but requiring good knowledge of topics like trees/lists traversal, dynamic programming, binary search, etc. One interview was on C++ knowledge, basic stuff like virtual functions, multiple inheritance, etc. with a small algorithm and coding question. Last interview was a design interview - design an image sharing system in which users can upload images, then get a short URL unique for their image and use it in forum messages, social networks posts, emails, etc. I was told by the recruiter that the feedback was mixed but with enough support for passing to the hiring committee. Then I was rejected and told by recruiter that the design interview is the cause. I find this decision very wrong, considering what I accomplished in my career and am sure 100% that any former colleague of mine would testify very positively on my design skills, but think back on the design interview I'm not surprised: The interviewer gave me a pen and papers so I could draw and write my design, but as soon as he finished asking the question he picked a pen and paper and started solving it himself, he seemed to be in a hurry to reach exactly the solution that he expects. He was not nice, arrogant and unpleasant to talk to and have an open discussion. In total 3 of the 6 interviewers were not people I would like to work with, while the other 3 were very nice and were fun to talk to and think together. I wasn't asked even once on my work experience or any of my past projects, no single "behavior" question like "describe a scenario in which you had a conflict", etc. and wasn't asked why I would like to join Google or what I'm looking for in a work place. It seems the entire process revolves around solving technical questions and nothing beyond that, so it's not surprising to me that 3 of 6 interviewers (in my opinion of course) had such bad people skills. I constantly had the feeling that the interviewers (all of them) prefer meek and inexperienced candidates, that can be shaped and trained to think exactly like them and would not show independent or out-of-the-box thinking. *** It actually felt to me like my experience and knowledge is an obstacle or a disadvantage instead of an asset that the company would and should appreciate !!! *** Other than that - I enjoyed solving the questions, food was great (and the engineer that escorted me was very nice and friendly, we had interesting discussions), the offices look and feel great. The recruiter was super friendly, always kept me informed and did his best to speed up the process, I have only good words to say about him. I later passed successfully interviews in other companies (including Google's competitors), some of which were more difficult, and received excellent offers from great work places, and I definitely think the process in Google leads to bad decisions. I was offered by the recruiter to try again in 12 months, but I have no such intention, nor would I recommend it to talented people that I know.

      Questions d'entretien [1]

      Question 1

      I wouldn't describe any question as "difficult", but they definitely require you to be practiced on data structures and basic algorithms. The design question requires different skills - breaking down a very "open" question, clearly defining components in a system, interfaces between them, flow, etc.
      Répondre à cette question
      6

      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

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

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Google

      Entretien

      OA - Round1 (1 tech + 1 bh) - Round2 two tech interview OA 1 Leetcode easy + 1 lc medium R1 tech 1 lc medium ask what is Fibonacci function R2 hard + medium greedy + game design

      Questions d'entretien [1]

      Question 1

      - why google - pround proj - time mgmt issue - ask about the resume proj - ask about your comments to previous manager
      Répondre à cette question

      Entretien pour Software Engineer

      29 juin 2026
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (New York, NY)

      Entretien

      Interview process consists of 2 rounds: 1st screening round (1 technical, 1 behavioral interview) 2nd onsite round (2 technical interviews) All technical interviews are still typical leetcode style DSA interviews, not the new AI based ones.

      Questions d'entretien [1]

      Question 1

      They asked typical behavioral and technical interviews.
      Répondre à cette question