Google Site Reliability Engineer Interview Questions | Glassdoor

Google Site Reliability Engineer Interview Questions

Interviews at Google

103 Interview Reviews

Experience

Experience
72%
15%
13%

Getting an Interview

Getting an Interview
62%
22%
6%
5
4
1

Difficulty

3.6
Average

Difficulty

Hard
Average
Easy

Helpful (6)  

Site Reliability Engineer Interview

Anonymous Interview Candidate in Seattle, WA
No Offer
Positive Experience
Difficult Interview

Application

I applied through a recruiter. The process took 1 day. I interviewed at Google (Seattle, WA) in March 2013.

Interview

A basic recruiting call to find out about my abilities and experience. Also took the time to explain that they were recruiting for the SRE (Site Reliability Engineer) team. Asked some screening questions and to rate myself on a list of technologies. By the end of the interview, both the recruiter and myself knew I wasn't a direct fit for the job but they did send my resume to other entities within Google.

Interview Questions

Other Interview Reviews for Google

  1. Helpful (6)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Santa Monica, CA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 4+ weeks. I interviewed at Google (Santa Monica, CA) in June 2011.

    Interview

    Google still doesn't know how to hire ops personnel - their interviews are geared towards Ph.D. comp sci candidates for software engineering, not sysadmins and people with deep operational experience. Interview questions rarely touch on experience or problem solving or troubleshooting, and instead focus on reciting manual pages and protocol stack layers and behavior. Expect a 6-hour process with multiple people.

    Interview Questions

    • heavy programming discussion in one session, and deep TCP options and switch protocol questions in another. relevant to the role, but not to the degree the interviewers were pursuing.   2 Answers

  2.  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Declined Offer
    Negative Experience
    Difficult Interview

    Application

    I applied online. The process took 2 weeks. I interviewed at Google (Mountain View, CA) in January 2009.

    Interview

    Phone screen followed by in person half-day interview. Two people interviewing, one with laptop recording what I said.

    Interview Questions

    • Something about how a switch works in its internals.   1 Answer

    Reasons for Declining

    Lowball salary.

  3. Helpful (22)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Declined Offer
    Positive Experience
    Average Interview

    Application

    I applied online. The process took 2+ months. I interviewed at Google (Mountain View, CA) in June 2012.

    Interview

    Google has a long process. I've interviewed with them several times before, the occasionally refresh their past candidates and call them back. The last time i spoke to them was about 3 years ago. The recruiter emailed me and asked to chat with me again, thru this process they explained the phone interviews that would be done, the skills assessment/packet preparation, then the onsite panel interview. Then the panel participants submit written feedback to a committee who makes the decision. You never speak to the people making the decision, sometimes this causes a loss of fidelity between who is being spoken to and who is making the decision. I don't care for the in-personal approach of never talking to the decision maker, but google is reported to be a good employer.

    Interview Questions

    • This wasn't difficult, but it was an important question: They wanted the name of a google employee i knew or worked with. If you know someone or worked with the, ahead of the interview have their email or full name all worked out as well as to be sure they will vouch for you.   2 Answers
    • Describe on a scale of 1 to 10 your familiarity with TCP/IP?   1 Answer
    • Describe on a scale of 1 to 10 your familiarity with Unix/Linux Internals?   1 Answer
    • Describe on a scale of 1 to 10 your familiarity with systems administration. Followup: which system call returns inode information? What signal does the "kill" command send by default ? How many IP addresses are usable on a /23 network. Can you describe a connection setup in TCP   3 Answers
    • Describe your familiarity on a scale of 1 to 10 familiarity with Algorithms and Data Structures? Describe on a scale of 1 to 10 each of these: C, C++, Python, Java, Perl, and Shell Scripting, MySQL.   2 Answers

    Reasons for Declining

    The location did not justify the pay they were offering in the offer. I just can't live on that salary in Mountain View.


  4. Helpful (3)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Kirkland, WA
    No Offer
    Neutral Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took a week. I interviewed at Google (Kirkland, WA) in March 2011.

    Interview

    Interview is very highly technical. This position requires a knowledge of systems admininstration, kernel internals, and scripting. Recommend brushing up on "Understanding the Linux Kernel" which would help. High amount of breadth and depth in this position. Also keep it simple. This is a screening process so there are a number of things that can disqualify you. Being too inquisitive will hurt more than help. Finally I would say don't be afraid to use Google against them. Look things up during the interview. Have a Linux system at the ready. There are some questions with answers fairly easily found in man pages.

    Interview Questions

    • What's the default signal used in a kill command?   2 Answers

  5. Helpful (2)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in New York, NY
    No Offer
    Positive Experience
    Difficult Interview

    Application

    The process took 7+ weeks. I interviewed at Google (New York, NY) in October 2009.

    Interview

    Interview process is very disorganized. Be prepared to have to shepherd it along yourself with follow up phone calls to ensure phone screens and whatnot actually take place. The on-site interview was actually pretty fun. Be sure you know your UNIX internals down cold. I'm actually surprised I wasn't offered the job, the interviews went fairly well. I suspect I was probably torpedoed in committee... I've been told that hiring decisions are made by arbitrarily chosen (volunteer driven) committees where applicants are regularly torpedoed for silly reasons or nitpicks on the part of one person on the committee.

    Interview Questions


  6. Helpful (10)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    Declined Offer
    Negative Experience
    Difficult Interview

    Application

    I applied through an employee referral. The process took 4+ months. I interviewed at Google (Mountain View, CA) in January 2010.

    Interview

    Protracted process from the recruiting team after initial contact. I went more than two months without a call back, followed by an offer to fly me out.

    The engineering team doing technical interviews were very professional and personable and asked interesting questions. These centered around Linux knowledge and engineering background.

    Interview Questions

    • A good example: "describe exactly what happens when you type 'telnet google.com 80' at a bash prompt, including shell interpretation, network connections".   1 Answer

    Reasons for Declining

    Several reasons. Primarily, it was impressed upon me that people with no coding background are second-class citizens at Google. Other employees out of the interview process told me that people are overworked and underpaid. Lastly, I decided I'd rather not relocate.


  7.  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Dublin, CA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    The process took a week. I interviewed at Google (Dublin, CA) in April 2011.

    Interview

    I was contacted by a recruiter asking if i am interested in working at google and scheduled a phone interview.first round is a recruiter screen with basic unix/linux commands which went well.second interview is more technical,it included topics from networking,Tcp/ip protocols,RAID etc,They would dig little deeper as you keep answering.It ended with a writing a program in language of your choice.I chose perl.
    3rd phone screen was mostly into Data structures and algorithms which required coding in C or Java.
    implementation of hash tables and binary trees etc and more of open ended questions.3rd interviewer was hurrying up and did not give much time to think because you fail to answer the first question correctly.Overall it was a good experience.

    Interview Questions

  8. Helpful (1)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    No Offer
    Neutral Experience
    Average Interview

    Application

    The process took 3 weeks. I interviewed at Google (Mountain View, CA) in October 2011.

    Interview

    Ever since I joined LinkedIn, I've been receiving emails from Google recruiters. I replied to the first one saying that as I'm an established contractor with my own company its difficult to switch to permanent employment. The emails kept coming in on a monthly basis. After around a year, I was on the look out for something different so I decided to look into it. The job description looked interesting and matched the work I'd been involved with in the previous years.
    I had the initial pre-screening which had some technical questions and we discussed the role a little.
    A week later I was offered a technical phone interview. It started with one question, which kept getting expanded until it covered a wide range of topics. It was clear they were after someone who knew how to approach a new problem, rather than someone who had memorized a bunch of commands suitable only for a particular situation. I felt it went really well, except at the end when I made some silly mistakes, but it was 10pm on a Friday, so I'm sure most people wouldn't be completely switched on at that point. Over all the interview was positive - it was relevant to my skills and the questions were fair.

    A few more days passed and I got an email saying that they don't have any jobs which match my qualifications, with the usual "thank you for your interest in our company etc.." Not knowing what that really means, I wrote back asking for a reason, and feedback on the technical interview. I explained where I thought I went wrong, and asked if that was the issue. I only got another email thanking me for my interest in the company and to try again in a few months.

    As I only had the technical interview, I was expending something like... "we need someone with more experience/knowledge in xxx", or "someone who has used xxx for xxx years". I did get the impression from the emails that there actually was no job available which was waiting to be filled, but they are constantly on the lookout - in the same was that job agencies sometimes post bogus jobs on job boards to get candidate information, and find out where gaps are in the job market.

    I fail to see how applying again in a few months will change things as I'm not sure what went wrong, so will probably make the same mistake again, unless asked exactly the same questions.

    Interview Questions

    • Topics: Filesystems, networking, scripting
      I will not write the question   Answer Question

  9. Helpful (6)  

    Site Reliability Engineer Interview

    Anonymous Interview Candidate in Mountain View, CA
    No Offer
    Negative Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 3 weeks. I interviewed at Google (Mountain View, CA) in April 2013.

    Interview

    An initial phone screen with recruiter followed by two technical interviews, one involved coding in a shared document. Recruiter came back each time and said I did very well, then invited me on-site for an all day interview. The on-site just consisted of the same types of questions from the phone interviews in 1-1 form with a series of 5 people. Nobody seemed to care much about getting to know me or learning about my skills I have to offer -- just doing random homework exercises.


Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.