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

      17 janv. 2020
      Candidat à l'entretien anonyme
      Somerville, MA
      Aucune offre
      Expérience positive

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Google (Somerville, MA)

      Entretien

      I had two phone interviews. My understanding is that there is usually only one, and then an in-person interview for the second round. I believe they wanted a second phone interview because the first interview was strangely easy. (I won’t share the question, but it involved simple string lengths, and I could have answered it directly out of my software bootcamp.) The second interview pertained to data structures, and was certainly more challenging. I was prepared for it. However, the interviewer seemed to articulate a different problem than what was copy-pasted from the bank of questions. I won’t share specifics, but he gave me a hypothetical data structure, wouldn’t tell me what specific kind of data structure, said that it was “broken” (nonstandard speak for this kind of structure) and that I had to fix it. I asked questions about duplicate entries, and whether I could, for example, assume it was a BST or a minHeap. He said no, and that it could be any random type of this kind of structure. Then he asked me how I would represent the data structure, at which point I became even more confused. (If I’m given a hypothetical chunk of date, I can assume it’s already represented in *some* way, such as an array, a linked list, etc... So, what exactly was I given?) After the fact, I attempted to ask for the wording of the original question but was unsuccessful. It’s entirely possible the interviewer was new to interviewing, or that translation issues resulted in poor communication between us. Overall, it was an awful lot of preparation to be undone by poor articulation of the problem. Aside from the unfortunate circumstances over the phone, the interviewer (and everyone else) was very nice to work with.

      Questions d'entretien [1]

      Question 1

      Data structures
      Répondre à cette question
      1

      Autres retours d’entretien d’embauche pour un poste comme Full Stack Developer chez Google

      Entretien pour Full Stack Developer

      10 juin 2026
      Candidat à l'entretien anonyme
      San Diego, CA
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (San Diego, CA)

      Entretien

      Great process, couple of interviews and lots of technical problems they do count the behavioral interview a lot so be prepared to be able to present and demonstrate your skills. At the end of the day their hiring team is super nice and help you with any questions that you have

      Questions d'entretien [1]

      Question 1

      Algorithms, make sure you know how to fix certain coding problems leet code is your best friend
      Répondre à cette question

      Entretien pour Full Stack Developer

      28 avr. 2026
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

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

      Entretien

      I got a screening, behavioral, then 7 interviews for the final phase, around 4 coding interviews, 3 behavioral. All leetcode hards, behavioral asks about experience situations, one technical interview was more architectural.

      Entretien pour Full Stack Developer

      2 nov. 2025
      Candidat à l'entretien anonyme
      Bengaluru
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Google (Bengaluru)

      Entretien

      The interview process was structured, transparent, and challenging. It started with an online application followed by an initial recruiter screening, where basic skills, experience, and role expectations were discussed. Next came technical rounds — usually two to three online coding interviews through Google Meet. Each round involved solving data structures and algorithm problems on a shared editor while explaining the thought process out loud. For software roles, the questions often focused on problem-solving, system design, and optimization. If you perform well, you’re invited for on-site (or virtual on-site) interviews, typically consisting of four to five rounds covering coding, system design, and behavioral interviews based on the “Googleyness” criteria — how well you collaborate, take ownership, and approach challenges. The entire process is highly organized and consistent, with regular communication from the recruiter about next steps. Feedback is usually given within a week or two. Overall, it’s a rigorous but fair process that tests both technical depth and problem-solving mindset.

      Questions d'entretien [1]

      Question 1

      One of the questions I was asked during the interview was: “Given an array of integers, find the length of the longest subarray whose sum is equal to zero.” They expected me to explain my thought process clearly, discuss different approaches (like brute force vs. using a hash map for optimized time complexity), and then write clean, efficient code while handling edge cases.
      Répondre à cette question