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 Google.com 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 Google.com Software Engineer

      25 nov. 2009
      Candidat à l'entretien anonyme
      Dublin, Dublin
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      Le processus a pris 4 mois. J'ai passé un entretien chez Google (Dublin, Dublin) en nov. 2007

      Entretien

      I was contacted by an Google recruiter that found me through Linkedin. He gave me a few details about the position by mail and we agreed to talk by phone a few days later. In this first phone contact He asked me a few very basic questions like what is 2^12 and what is the worst case complexity of Quicksort. After that I went through three more phone Interviews, was asked a lot of very tough questions and passed successfully to each on of these interviews. I was then invited to travel to Dublin and there I went through a day of 6 interviews with lunch in the between. After a couple of weeks I received the negative response.

      Questions d'entretien [2]

      Question 1

      - What is 2^12? - Past experiences - Trivia - Unfortunately I cannot publish more questions (NDA)
      Répondre à cette question

      Question 2

      - What is the complexity of quicksort? - Unfortunately I cannot publish more questions (NDA)
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Google.com Software Engineer chez Google

      Entretien pour Software Engineer (Google.com)

      25 juil. 2010
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 6 semaines. J'ai passé un entretien chez Google (Londres, Angleterre) en juin 2010

      Entretien

      Went though someone who already works for them so they were able to tell me more about the process. Got a call from a HR person whit a breif chat to determine if I was serious about it. Was emailed a "rate yourself out of 10 for the following skills" which I filled in. Next week, a 45 minute call which was 20 mins of someone giving a monologue about how great working for Google is, followed by about 20 fairly random questions mainly concentrating on the skills I put as being good in. Next week first proper 45 min phone interview which was solve a single large problem along with many questions asking about details of how things work and guesstimates of speeds of various tasks. Next week second proper 45 min phone interview which was coding in an online Google docs document in pseudo-code. Involved 5 tasks each building on top of the code you have already written. Some trying to lead you into traps. Some discussion of performance. Followed by a couple obscure questions about low level libc functions I never heard of. Two/three weeks later, an onsite interview from 10AM till 3PM. Five interviews. One writing algorithmic code on paper followed by general discussion of algorithms and data structures. Second was debugging a printed out code piece of code with a very obscure bug inside, followed by a discussion of open source projects. Third was describe security methods that you know of, how can you make ssh less vulnerable to attacks, explain the internal operation of init. Then there was a free lunch and a guide around the office followed by the fourth which was a remote video one in one of their rooms. This was looking heavily at server profiling and solving weird Linux issues. And the final one was with a manager who asked things like "what will you bring to the team". Everyone kept saying how you just need inteligence but many questions were very much, if noone taught you this, you will not know it. While answering the question which was something only someone who was a data-centre admin would know, I figured out a solution after a couple prompts and was quite pleased with that. Later I was told by my friend that that was a fail. They do want you to know the answers before and no lateral thinking will help you.

      Questions d'entretien [5]

      Question 1

      Name 20 things you would record in a webserver profiler
      Répondre à cette question

      Question 2

      Tell me everything you know about hash-tables.
      Répondre à cette question

      Question 3

      What is the difference between gets and fgets and what is special about their buffers. (No you can look up man pages or get clues).
      Répondre à cette question

      Question 4

      What is the kernel call to get the inode information of a file?
      2 réponse(s)

      Question 5

      Name the function of all the process signals you can think of.
      Répondre à cette question
      1

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      Amazon
      3.7★Rémunération et avantages
      avatar
      Amazon Web Services
      3.9★Rémunération et avantages
      avatar
      TikTok
      3.6★Rémunération et avantages
      avatar
      Meta
      4.6★Rémunération et avantages