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 avr. 2011
      Employé (anonyme)
      Mountain View, CA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      Le processus a pris 1 semaine. J'ai passé un entretien chez Google (Mountain View, CA) en avr. 2011

      Entretien

      The Google interview process typically includes a phone interview or two as well as an on-site, in a process that takes a couple of weeks to a month. I had a pending offer from another company, so they expedited my interview (skipped the phone), and expedited the hiring committee review. I got flight info for two days later, flew out, interviewed the next day (Friday), and had an offer by Monday. At the on-site interview, they put you up in a pretty nice hotel and provide a rental car. GPS is recommended, as the Mountain View / Sunnyvale suburbs can be difficult to navigate. The Google campus is simply spectacular. They have dozens of buildings, with bikes for transportation between bulidings, buses in and out of different neighborhoods, multiple dining cafes, multiple gyms, etc. Google is also located all over the country (and world) - you can actually pick your location if MV suburbia isn't your cup of tea. Projects/teams are distributed across separate offices. As for the actual interview: 5 separate 45 minute interviews with other Software Engineers. The interviewers come from a wide background (infrastructure, front end, etc). Questions were all technical in nature, mostly coding oriented. They did ask pointed questions about previous experience, projects, general resume stuff, etc. The interview questions were well thought out and relatively innovative. The interviewers presented them clearly, and were very helpful in discussing solution possibilities. Some of the questions were pretty straightforward, but the trickier ones were excellent - we were able to devise solutions and optimize them multiple times, discussing what was better about different approaches. Everyone I talked to was very upbeat, intelligent, and nice. The last interviewer I had seemed a bit surly at first, but quickly warmed up and became very affable. The hiring process was very informative. The recruiters gave loads of information when asked, and were very up front about a lot of aspects of the company. The interviewers themselves were able to answer many questions about the gritty details of working at Google. The hiring itself is actually done by a separate group of people from the interviewers, and is decided somewhat up the chain of command.

      Questions d'entretien [1]

      Question 1

      Google asks interviewees to not share specific details on interview questions. They were coding-oriented questions. They required a varied set of algorithms and data structures to solve, especially including graphs, heaps, linked lists, and hash tables. Sorting algorithms were also emphasized. Some of the interview questions were quite unique, but could be abstracted in neat ways. Google does provide a significant amount of material before the interview(s) to help you study, including links to reading material and the types of questions you can expect. They were relatively difficult, but the interviewers were helpful.
      1 réponse
      3

      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