Ga naar de inhoudGa naar de voettekst
  • Vacatures
  • Bedrijven
  • Salarissen
  • Voor werkgevers

      Geef je carrière een boost

      Ontdek hoeveel je kunt verdienen, vind droombanen en deel anoniem inzichten over werk en privé.

      employer cover photo
      employer logo
      employer logo

      Google

      Actieve werkgever

      Over
      Reviews
      Salaris en arbeidsvoorwaarden
      Vacatures
      Sollicitatiegesprekken
      Sollicitatiegesprekken
      Gerelateerde zoekopdrachten: Reviews voor Google | Vacatures bij Google | Salarissen bij Google | Arbeidsvoorwaarden bij Google
      Sollicitatiegesprekken van GoogleSollicitatiegesprekken voor Software Engineer, Site Reliability Engineering bij GoogleSollicitatiegesprek bij Google


      Glassdoor

      • Over
      • Blog
      • Contact met ons opnemen

      Werkgevers

      • Gratis werkgeversaccount
      • Werkgeverscentrum
      • Werkgeversblog

      Informatie

      • Help
      • Gedragscode
      • Gebruiksvoorwaarden
      • Privacy en advertentiekeuzes
      • Verkoop of deel mijn persoonlijke gegevens niet
      • Hulpmiddel voor instemming met cookies

      Partnerships

      • Adverteerders
      De app downloaden

      • Bladeren op:
      • Bedrijven
      • Vacatures
      • Locaties

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" en logo zijn gedeponeerde handelsmerken van Glassdoor LLC.

      Gevolgde bedrijven

      Volg de bedrijven van je dromen om als eerste op de hoogte te zijn van vacatures en te profiteren van tips van insiders.

      Sollicitatiegesprek voor de functie Software Engineer, Site Reliability Engineering

      12 jul 2014
      Kandidaat voor anonieme sollicitatie
      Dublin, Dublin
      Geen aanbod
      Negatieve ervaring
      Moeilijk sollicitatiegesprek

      Sollicitatie

      Ik heb online gesolliciteerd. Ik heb gesolliciteerd bij Google (Dublin, Dublin) in jul 2014

      Sollicitatiegesprek

      I applied online on June 9, 2014. After two weeks I received an email from a recruiter asking me to evaluate myself from 0 to 10 (0 being "no experience" and 10 being "super expert") on the following list: __TCP/IP Networking (OSI stack, DNS etc) __Unix/Linux internals __Unix/Linux Systems administration __Algorithms and Data Structures __C __C++ __Python __Java __Perl __Shell Scripting (sh, Bash, ksh, csh) __SQL and/or Database Admin __Scripting language of your choice (not already mentioned) _____ __People Management __Project Management I was really honest and evaluated myself a little low on almost all of them, except from Java, C++ and algorithms + data structures (which I thought were my strongest). However, the recruiter decided to schedule a phone interview with me. We agreed to have the interview on July 8, but something came up and I had to change it; she was really cool about it, and finally we scheduled for July 12. Some of the questions were: - What is the time complexity of Quicksort in the worst case scenario and in the average case? - What is the unix system call that returns file attributes about an inode? - Have you heard about linux 'tail' command? - Without using a calculator, tell me how much is 2 to the power of 24? The only one I got right was the first one =( because I read someone else's questions here, but I wouldn't remember otherwise. To be honest, if I needed to know any of that I would just Google it, but I don't remember it from 5 years ago when I studied them in the university. Also, it was a bit confusing because it was obvious that the recruiter was not a native english speaker, and neither am I, so sometimes I just didn't understand what she was saying, even after repeating 2 or 3 times. For example, on the 'tail' question I understood 'till' and of course I said I had never heard of it -.- In my humble opinion, it seemed more like an end of semester test rather than an interview. Besides, she didn't even ask me anything on the topics I evaluated myself the highest. At the end, she obviously concluded and kindly said that this was not the job for me.

      Sollicitatievragen [2]

      Vraag 1

      Which of these do not guarantee a time complexity of O(log n) ? - Red black tree - Binary tree - Linked list - Hash table - B tree
      1 Antwoord

      Vraag 2

      Enumerate the following from 1 to 4, being 1 the fastest to execute and 4 the slowest: - read cpu register - disk seek - context switch - read from main memory
      4 antwoorden
      10

      Overige sollicitatiereviews voor Software Engineer, Site Reliability Engineering bij Google

      Sollicitatiegesprek voor de functie Software Engineer, Site Reliability Engineering

      17 apr 2014
      Kandidaat voor anonieme sollicitatie
      Geen aanbod
      Positieve ervaring
      Gemiddeld sollicitatiegesprek

      Sollicitatie

      Ik heb via een recruiter gesolliciteerd. Ik heb gesolliciteerd bij Google

      Sollicitatiegesprek

      The recruiter first did some screening by phone, asking a few technical questions and driving me through Google's "self-evaluation" in about 10 domains (networking, *nix internals, *nix sysadmining, algorithms, and various languages) (the recruiter had a good idea of how I *should* score). I was asked to narrow down where I would work. Google picked an interviewer from one of the would-be sites of employment for a coding interview done via phone and a shared document. After that I did a day of interviews at Google's offices. Lunch wasn't an interview but I was also accompanied by a Googler who let me ask questions about the work, office life and such (all interviewers did this, but the interviews rarely left enough time). Sent back feedback to the recruiter, who called me back when the hiring committee declined to make an offer. Unfortunately the recruiter gave very little feedback when asked, claiming it wasn't shared with them. The on-site interviews featured troubleshooting, coding, large-system design, plus a bonus topic of my choosing (SRE-related) and an extra interview which I think was picked where I ranked highest. My least favourite was the troubleshooting, since there was no actual terminal prompt and I was at the mercy of the interviewer deciding how the system was built, how it would manifest symptoms, and their understanding of how my commands would work. That interviewer had asked me to pick a small number of things to monitor, without deciding what the purpose of the monitoring would be. Aside from early interaction with the recruiter, and the fact that my interviewers had access to my resume, there was very little of the traditional HR approach to recruiting; this was almost all technical, and I was the only one asking questions about the more general fit. One annoying thing is that, aside from the recruiter, everyone called me from numbers that wouldn't answer back. This plus the distance made organising some things painful. It also means you have to write down anything you might want to ask in advance, because the people calling you are more prepared than you do.

      Sollicitatievragen [1]

      Vraag 1

      see description of troubleshooting above - more of a process than a simple question
      Vraag beantwoorden
      1

      Sollicitatiegesprek voor de functie Software Engineer, Site Reliability Engineering

      25 sep 2013
      Kandidaat voor anonieme sollicitatie
      Geen aanbod
      Positieve ervaring
      Moeilijk sollicitatiegesprek

      Sollicitatie

      Ik heb via een recruiter gesolliciteerd. De procedure duurde 2 weken. Ik heb gesolliciteerd bij Google

      Sollicitatiegesprek

      The recruiter reached out to me on linked in. First the recruiter gave me a technical phone screen. She had about 5 questions related to programming and unix. I passed and moved on to a phone screen with a developer on the team I would be working on. He emailed me a shared google doc and posted a programming question in it. I was able to answer this question in about 2 minutes (similar to fizzbuzz) The he posted a harder programming question. I got a sub-optimal answer and chatted back and forth with the interviewer. I eventually stumbled to a good solution.

      Sollicitatievragen [1]

      Vraag 1

      What signal is sent by default in the unix kill command
      4 antwoorden

      Topbedrijven voor 'vergoeding en arbeidsvoorwaarden' bij jou in de buurt

      avatar
      Amazon
      3.7★Vergoeding en arbeids­voorwaarden
      avatar
      eBay
      4.0★Vergoeding en arbeids­voorwaarden
      avatar
      Booking.com
      4.2★Vergoeding en arbeids­voorwaarden
      avatar
      Meta
      4.6★Vergoeding en arbeids­voorwaarden

      Vacatures

      Zoek naar vacatures om gepersonaliseerde vacature-aanbevelingen en -updates te krijgen.