Google

  www.google.com
  www.google.com

Google Systems Engineer Interview Questions

17 Interview Reviews

Interview Experience

Interview Experience

46%
7%
46%

Getting an Interview

Getting an Interview

58%
27%
8%

Interview Difficulty

4.0
Average

Interview Difficulty

Hard

Average

Easy

17 Candidate Interview Reviews Back to all interviews

Sort: Popular Date Difficulty

 

Systems Engineer Interview

Anonymous Interview Candidate
Anonymous Interview Candidate
Application Details

I applied through a recruiter. The process took a weekinterviewed at Google.

Interview Details

The initial screening was straightforward. The problem arose when my first phone screening was with a network engineer despite my indication that I was not strong in the area of networking.

He repeatedly asked networking questions despite my reiteration that networking was not my area of expertise.

Interview Questions
No Offer
Negative Experience
Difficult Interview

Other Interview Reviews for Google

  1. 6 people found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter. The process took 3 weeksinterviewed at Google in April 2013.

    Interview Details

    I was contacted by a Google recruiter via LinkedIn to see if I was interested in exploring an opportunity with the Site Reliability Engineering team. Even though I'm very happy in my current position, who turns up their first chance to interview with Google? I was contacted on a Thursday and had an initial recruiter phone screen set up for the following Monday.

    The recruiter started by asking me to talk about my background and experience, then explained the position to me. After rating myself on a number of different topics (networking, UNIX internals, UNIX administration, Python, Java, C++, C, Shell scripting, etc.), I was asked six fairly basic questions. I got all of them correct (none were very difficult), and the recruiter told me that someone would reach out to me in the next few days to schedule a technical phone interview in a couple weeks. She also let me know that she'd be providing me with some documents that discussed what kind of information I should brush up on to prepare myself.

    A couple days later, I received an email with a time for the phone interview as well as the link to a Google Doc they'd use for scripting questions to simulate a whiteboard. The interview was scheduled for about a week and a half later, so I had time to review the interview prep docs.

    The docs themselves were definitely helpful. After reviewing them, I was able to identify places that I needed some refreshers and concentrated there.

    When the interview itself came, the call came on time. The interviewer was friendly and easy to talk to. He introduced himself and asked if I had any questions (I told him I'd wait until the end in case any were answered during the interview, though I was never given a chance to ask again -- probably due to time constraints), and then we dove right in to the technical questions.

    I was asked a series of increasingly complex networking questions that started out *very* basic (How does a switch work?) and became more complex as he got a feel for my skill levels. After a while, we moved on to Linux/UNIX internals (processes, signals, etc.).

    The second half of the interview was a scripting exercise in the shared Google Doc. Without giving too much away, I was asked to write a script that would parse data from a passwd file and return some information. Though I expected this, I found scripting in a word processor significantly more difficult than I had anticipated. It took me much longer than I'd hoped, and after the interview I kept thinking of little problems I hadn't caught.

    By the end of the scripting exercise, the interviewer seemed pretty disinterested and abruptly ended the call with a promise that the recruiter would follow up after he'd submitted his feedback.

    A great credit to Google, I received a call about a week later from my recruiter who let me know that they decided to pass. She also mentioned that the feedback from the interviewer was that I was very strong in networking and UNIX questions, but that they felt that I didn't have enough scripting experience. She invited me to apply again down the road and told me that she'd keep me in mind in the future for similar positions.

    All in all, though I'm disappointed, it was definitely refreshing to be provided actual feedback on the results of my interview as well as a phone call rather than a canned email or complete silence.

    Interview Questions
    • How much faster is DNS considering that it uses UDP instead of TCP?   View Answer
    No Offer
    Difficult Interview
  2. 5 people found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Anonymous Interview Candidate in Mountain View, CA
    Application Details

    I applied through an employee referral. The process took 6 daysinterviewed at Google in March 2010.

    Interview Details

    I am a seasoned software engineer with 15 years of excellent experience in developing highly performant software systems, and am well-rounded enough to have participated in everything from design of hardware, operating systems components, all the way to GUI widgets and interface systems.

    A friend of mine who works at Google worked hard to convince me to interview there, and submitted my name to his manager, who arranged for the recruiter to contact me.

    The recruiter was extremely arrogant from the start. He never really understood my core capabilities and seemed to discredit much of my prior work experience. I cannot easily handle personal calls during my work house, but I agreed to be able to take some phone interviews when he explained they set them up a day in advance. In actuality, both phone interviews I had a maximum of 45 minutes to leave work and make it home to take the phone call. The recruiter was very unprofessional in many aspects of communicating important details like this to me. (Details matter, unless you work at Google!)

    Both phone interviews went poorly, primarily because the interviewers were being exceptionally obtuse. I couldn't get a straight answer out of either of them. One interviewer tried to ask me things in non-sensical language and when I tried to ask for clarification, he got mad at me. I guess his impression of engineers are that they can read minds, or perhaps can learn his special short-hand speaking style in a 30 minute call.

    The worst part was the final call from the recruiter, and he said to me "At least you got to interview with Google... not everybody can say that". What an arrogant and classless attitude. I responded by saying that they should be thankful that at least they got to interview with me, because not every company can say that.

    Interview Questions
    • Wanted to know how to implement a traceroute routine and what ICMP and TCP details would need to be developed to write the command.   Answer Question
    • Wanted to have me explain a number of different sorting algorithms that I believe are only used in file systems. The interviewer could not explain what the question was and would not clarify what he was looking for. Total failure to deliver the interview question in a way that a computer scientist could understand what was needing to be answered.   Answer Question
    No Offer
    Negative Experience
    Difficult Interview
  3. 4 people found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate in Santa Clara, CA
    Anonymous Interview Candidate in Santa Clara, CA
    Application Details

    The process took 2 weeksinterviewed at Google in December 2008.

    Interview Details

    Google has the most obtuse hiring process of any company I've spoken with in my 12-year career. Interview questions have little to no relevance to the job being applied for, and seem to be little more than a means by which the academics working there can massage their enormous egos.

    Interview Questions
    Reasons for Declining

    After meeting with several people at the company and in the group I would have been working for I found that, while the company wants to harbor a collaborative academic type of environment, the job I was applying for and the required number of hours equated to this being no better than a high-paid sweat shop. The interview process was highly misleading and deceptive, and without substantial bonuses that were promised but likely would not have been delivered upon in this economy the salary was mediocre.

    Declined Offer
    Negative Experience
    Difficult Interview
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5.  

    Systems Engineer Interview

    Anonymous Interview Candidate in Bangalore (India)
    Anonymous Interview Candidate in Bangalore (India)
    Application Details

    I applied online. The process took 3+ weeksinterviewed at Google in February 2014.

    Interview Details

    very tough

    Interview Questions
    Reasons for Declining

    depends on my mood

    Declined Offer
    Positive Experience
    Difficult Interview
  6. 1 person found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied online. The process took 3 weeksinterviewed at Google in April 2013.

    Interview Details

    1st Phone interview - questions : developer skills, preferite language, time in a day spent programming, IP, pthread, firewall, inode content, signals, python in general, C malloc, C++ delete, MAC, DNS header, quick sort
    2nd Phone interview - questions: PID, PPID, precesses, thread, zombie, init, bash command top. Python: newbie questions, range() vs xrange()
    3rd Phone interview - write a Python to read a file and extract significant data from it

    Interview Questions
    • Qhich is the relation between the init process and zombie processes.   Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  7. 1 person found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate in Zürich (Switzerland)
    Anonymous Interview Candidate in Zürich (Switzerland)
    Application Details

    I applied through a recruiter. The process took a weekinterviewed at Google in January 2013.

    Interview Details

    I got some typical and untypical questions ...

    - bunch of questions related to system calls (sockets and network programming, open/close connect/listen inode, etc. ). I had to know (in details) a large number of system calls and what they are changing.
    - mergesort in details (best, average and worst case)
    - comparison between TCP and UDP (e.g. congestion and flow control)
    - graph to find the shortest path

    Interview Questions
    No Offer
    Average Interview
  8. 1 person found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter. The process took a dayinterviewed at Google.

    Interview Details

    As others already mentioned, recruiter is gonna ask you some basic questions like how many ip addresses are in /23 subnet, inode definition, system calls name for getting the file path, how to make an executable suid. I was put off by the fact they really want you to have this information memorized instead of being able to look it up but maybe it is just me with my lazy memory. So we did not move forward.

    Interview Questions
    • They really want you to have memorised the answer rather than being able to find out in few seconds using google!   Answer Question
    No Offer
  9. 1 person found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate in London, England (UK)
    Anonymous Interview Candidate in London, England (UK)
    Application Details

    I applied through a recruiter. The process took 2+ monthsinterviewed at Google in September 2012.

    Interview Details

    I got contacted from a recruiter. I passed the initial phone interview where they asked me some very basic questions. The next stage was a Technical Phone Interview which was also easy. They basically wanted to verify if my curriculum vitae was true or not. The last stage I've done was an on-site interview. It was tough because it lasted 5 hours. It covered both theory and practice. My impression is that they want prepared people with good knowledge on Linux internals, a good scripting ability and a good attitude in large system design and troubleshooting.

    Interview Questions
    • Large system design and troubleshooting are difficult, because you cant prepare enough for them.   Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  10. 3 people found this helpful  

    Systems Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter. The process took 4+ weeksinterviewed at Google in August 2012.

    Interview Details

    Google's hiring process is everything that you might expect it to be for a technical position with the preeminent technology company at this time. I didn't apply to them, they found me, so I suggest you have filled out things like LinkedIn and any other jobs sites you are on filled out and ready.

    It is clear that they do take a lot of effort in looking for candidates, and they do multiple screens. Their questions are legendary, but I'd say that the only argument I have with the process is the idea of using corner-cases to test knowledge. A number of the questions had little to do with problem solving, and more to do with whether you remembered this or that command switch or algorithm. This makes the interview a little more haphazard as some questions I got, I would only know because I happened to do something related to it recently, and some that I know I flubbed, I would have gotten right at some point years ago where they actually came up. And all of them could have been discovered in less than five minutes of searching Google. So, if you are someone who works efficiently, but has a poor memory for certain details, you are going to be at a disadvantage. That said, there are also some coding sections and problem solving questions where you could shine, if you can think on your feet.

    One thing for systems engineers to remember with Google is that they do a lot more coding than a system engineer might do elsewhere. This is due to the high level of automation that they have to deal with. So, you will get asked questions that may well be heard more frequently in developer interviews. (I do imagine that actual coders would have gotten much worse). I was prepared for this, since I like coding as a hobby and work on a number of open source projects, but if you relied on the normal experience of many sys admins I have worked with in the past, you may well find yourself a little shocked.

    I also suggest that you have something ready to show them online about what you have worked on in the past. It's good to show that even though you may not like taking tests, you still get things done. It's hard to tell if that mattered for me, but they definitely ask you if you have worked on open source projects or if you have anything out there.

    Interview Questions
    • Design and describe a system/application that will most efficiently produce a report of the top 1 million Google search requests.

      They provided particulars that I don't recall right now, but they told you how many servers you have to work with, how big the logs are and what state they are in, and you could designate an open source product or you had to write something on your own to do it.
       
      View Answer
    Reasons for Declining

    In the end, it turns out that they do pay well, but unless you have written a book, you're not going to make much more than you could make elsewhere. For me, if I didn't have to move a few states away to work for them, I would probably have taken the job. As it was, I could not justify moving to Mountain View for what was a modest rate increase.

    Declined Offer
    Difficult Interview

Work at Google? Share Your Experiences

Google

 
Click to Rate
or

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.