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