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

      26 avr. 2013
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Google en avr. 2013

      Entretien

      Got two emails from a Google recruiter based on academic institutions I had listed in my Google+ profiles. I gave the recruiter a call and he called me back the same day. We had a 20 minute conversation about my current experience and about what I was looking for in a future job. He then said he would like to set up an interview in the next couple of weeks. He also requested I send him a copy of my resume. 8 days later I got an email from an interview coordinator. The interview was setup for 6 days from when this interview coordinator contacted me. The interview was to be conducted over the phone and use a Google doc. I sent an email back to the interview coordinator asking if I could setup a Google hangout interview instead, since I don't have a headset that attaches to my phone, but I do have a webcam and headset that attach to my computer. (I watched an interview preparation video on the Google jobs page that suggested that I have a headset, and not to use speaker phone). The interview coordinator sent me instructions for the Google hangout interview; these instructions said the interviewer would contact me with the URL for the hangout. I spent the weekend before my interview preparing, I practiced coding every sort and search function, some patterns that I haven't used in a while, etc., as I finished my undergrad 5 years ago, and expected the interview to be quite academic, based on feedback I've read on this site. Also reviewed OO principles, etc. I thought I would be in pretty good shape for the interview. The time for my interview came around, and no email from the interviewer containing the Google hangout link. I figured I would give the interviewer 10 minutes before I took any action. 15 minutes later, still no email. So I emailed my recruiter. I got an email back from him almost immediately saying he would contact the interviewer. I then got an email from the interviewer with the hangout link. I clicked the link and it said I did not have permission to join the hangout. I also noticed the interviewer had not joined the hangout. I then got a call from the interviewer. He said that he hadn't ever used hangout before in an interview and so we should just do the interview over the phone, as that was his preference. I asked him to give me a minute to try to get the audio worked out on my end as his voice was muffled to the point I could barely understand him. Nothing I did fixed this, so I asked him if he was on speaker, he said "yes". I asked him if he could go off of speaker because I couldn't hear him. He did and then I could hear him perfectly, but both of us had to hold our phones, which was quite uncomfortable. He continued by saying that he just had one question for me, and that it would probably take me the duration of the interview to complete. He pasted a java function into the Google doc (as I am most familiar with java). He explained briefly what the function was supposed to do, but said there were errors in the code and that it didn't currently accomplish the goal and that he wanted me to identify and fix the errors. I won't specify what the code did, but I will specify that it dealt with a domain I was only vaguely familiar with. I started walking through the code with the interviewer to understand the flow of data through the function. The code was quite simple, and with some help from the interviewer identified the first issue. The issue was an incorrect mathematical function. For example the line of code was supposed to produce f(x) = y, but it was not producing y. The function was not difficult, but I couldn't figure out what the mathematical manipulation of variables should be to produce the desired outcome. The interviewer then went on to say that we had only 15 minutes left in the interview, and that we should move onto to see if we can find more issues. So we stepped through some more code assuming the first issue was working correctly. Then I found the next issue, it was exactly like the previous issue. This time the function was a little simpler, but still not something you could solve in less than 5 minutes. I tried a few different things, talking the interviewer through exactly what I was thinking. Then the interviewer said that our time was up, but that he would give me an extra five minutes to solve the current function, as I was getting pretty close. In the five minutes, I solved that function. He then asked if I had any questions about Google that would be appropriate for an engineer that it was likely the recruiter couldn't answer. I asked two questions and then we ended the call.

      Questions d'entretien [1]

      Question 1

      Come up with a mathematical function that produces f(x) = y for multiple functions found in a given chunk of code for some random domain.
      Répondre à cette question
      2

      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

      7 juin 2026
      Candidat à l'entretien anonyme
      Los Altos, CA
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (Los Altos, CA)

      Entretien

      Went with an OA which was pretty easy. Then got to second round (1 coding and 1 behavioral). Both were pretty straight forward. Then got to the onsite. They asked me leetcode hard questions. I was able to do well in one but failed the other one.

      Questions d'entretien [1]

      Question 1

      Why do you want to work at Google?
      Répondre à cette question

      Entretien pour Software Engineer

      7 juin 2026
      Employé (anonyme)
      Seabrook, NH
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Google (Seabrook, NH)

      Entretien

      Had a good interview. Easy problems not leetcode but if you know how to solve problems and use which DSA to use for what problem then you are good.. system design as well.

      Questions d'entretien [1]

      Question 1

      Tell me about yourself ?
      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