Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For Employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      GitHub

      Is this your company?

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: GitHub reviews | GitHub jobs | GitHub salaries | GitHub benefits | GitHub conversations
      GitHub interviewsGitHub Site Reliability Engineer interviewsGitHub interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent Posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalized job recommendations and updates by starting your searches.

      Site Reliability Engineer Interview

      Oct 17, 2017
      Anonymous Interview Candidate
      No offer
      Negative experience
      Easy interview

      Application

      I applied online. I interviewed at GitHub

      Interview

      Firstly, reference the other most recent "Site Reliability Engineer". Their interview process was almost IDENTICAL to what I went through. It was the most embarrassing (for GitHub) and frustrating interview process I have ever been through. Let's first talk about timeliness, and the fact that GitHub doesn't know what this is. At the time of my first phone screen with the recruiter I was in the later stages of interviews with other companies and made it clear to the recruiter I would like to see if we could expedite the process. She said "I have gotten a candidate through the process in as little as a week." However, I started interviewing in AUGUST and finished last week (October)! For this role the interview process starts with a standard phone screen with the recruiter over video chat (Zoom). Already red flags started to pop up. When I tried to join the Zoom conference at our scheduled time I joined in the middle of an on going conference with another person!! To add to the awkwardness the recruiter KICKED me from the Zoom chat. I sat at my computer dumbfounded and feeling awkward as to what just happened. I quickly came to realization the recruiter was using the SAME CONFERENCE IDs for their candidates WTF??? I awkwardly sent an email to the recruiter explaining what just happened, but got no response for the next 30 minutes. It was not only until I CC'd who I assume is the Recruiting Coordinator that she actually responded. She apologized for the confusion and offered to reschedule the phone screen. That's really not cool for someone who already has a job and took a personal day off to do a video interview and set the precedence for this whole terrible experience. After another week of waiting we finally got to talking about the role, requirements and interview process over the phone. The role sounded like a match and I was genuinely interested in working for GitHub. She said the SRE team was working on a homework assignment to complete as the next stage of the interview, so to hold on to when they are done and she will contact me with the details. (What happened to the process taking one week??) She also openly said "I get so many emails, so sometimes I don't respond and they get lost." Wow... This is actually coming out of the mouth of the recruiter? Another red flag. At least she offered me her phone number and said I could text her if it was urgent. Albeit kind of weird I took the number. I waited a week... Then another week... I emailed the recruiter, yup you guessed it. No response. I texted her querying about the status of the homework assignment. No response. Again I CC'd the recruiting coordinator and magically got a quick response (hmmmm). Finally she said the homework project is almost done and should be ready next week. To give them credit it was indeed ready the next week. She sent me over the homework and I had 8 hours to complete starting from the date/time I gave her. The homework project was actually quite fun and was fairly straight forward to knock out in about 2 hours. I submitted the homework and waited a week to hear back that the team would like to interview me in two separate Zoom phone screens to review my code. I unfortunately had to wait two weeks to have the tech interviews due to scheduling conflicts, just further adding to the time. I honestly don't think anyone that does not have a FTE job already would have any patience left at this point. However, I decided to move forward anyway. The first tech interview was "interpersonal," which is the cookie cutter "tell me a time when" type interview. Both interviews seemed pretty monotone and straight to the point (standard). One even admittedly said this interview was particularly robotic. It was mostly questions about my experience and how I would solve technical challenges. Next was the coding review portion of the interview where the interviewers and I look through the code I submitted with the homework. This part was pretty fun and I feel went over very well. The interviewers had some thoughtful questions and I actually implemented some of the improvements we came up with and tested them live (it worked!). Overall it was pretty awesome and I came away from both interviews thinking I did really well. I waited a few days and got the standard "Thank you for your time, we are moving forward with other candidates" email. I felt really confused at this point, I thought I did pretty well in the interviews. I sent a followup email to the recruiter thanking her for letting me know, but also wanted to ask for feedback. I knew this was moot as I never heard a response back... Overall the interview process as I and the other candidate on Glassdoor had experienced was absolutely abysmal. I cannot believe the communication problems, messed up timelines, and overall awkwardness that came from this. After experiencing this it has definitely turned me away from wanting to work here in the future.

      Interview questions [1]

      Question 1

      A homework assignment on a private repo.
      1 Answer
      7

      Other Site Reliability Engineer Interview Reviews for GitHub

      Site Reliability Engineer Interview

      Oct 8, 2021
      Anonymous Interview Candidate
      No offer
      Negative experience
      Average interview

      Application

      I applied online. I interviewed at GitHub

      Interview

      Recruiter reached out, had me sign some forms and scheduled an initial screen. Recruiter did not show up for the screen, and did not send any update beforehand or afterwards.

      Interview questions [1]

      Question 1

      Interviewer did not show up
      Answer question
      8

      Site Reliability Engineer Interview

      Aug 20, 2018
      Anonymous Interview Candidate
      San Francisco, CA
      No offer
      Positive experience

      Site Reliability Engineer Interview

      Jul 26, 2018
      Anonymous Interview Candidate
      Remote, OR
      No offer
      Negative experience
      Average interview
      Average interview

      Application

      I applied online. The process took 3 weeks. I interviewed at GitHub (San Francisco, CA) in Aug 2018

      Interview

      Honestly, I had a really great experience from beginning to end. Here is a recap of what I experienced firsthand.... I applied online after hearing about some of the new projects that GitHub is working on. After my application, I received an email from the recruiter and I scheduled a video meeting later the same week. She spent about 30 mins getting to know my background and asking some traditional questions. I scheduled a take-home assignment. Overall, it was a fun assignment. A couple of days after submitting my pull-request I received an email from someone to schedule meetings with technical staff and the hiring manager. Overall, the people I met were great and appeared to be highly capable. The hiring manager was eccentric but I warmed up to him by my second meeting with him. After a week, I spoke with the recruiter. It turns out that they didn't see my experience inline with what they were looking for. She did mention something about a "no- feedback" policy -- but in my experience, all of the technology companies have the same policy (Google, Facebook, Slack, etc.). OVerall, it was a good experience -- even if I didn't get the job.

      Interview questions [1]

      Question 1

      There is a take-home assessment and it's later the basis of a discussion with a few engineers
      Answer question
      3

      Application

      I applied online. The process took 4 weeks. I interviewed at GitHub (Remote, OR) in Jul 2018

      Interview

      I applied online for a remote SRE role and had a quick chat with a recruiter via Zoom. She was a lovely person and it seemed like everything was going well, in fact, she didn't really do anything other than make a connection and then give the next steps. I didn't realize that this is where the problems would begin. The next steps were unclear; she rattled off a series of things that would happen: a technical coding problem, code review, values interview, hiring manager interview, then more coding, then more values and then.... it was all so much, so quick. I did, however, understand that the next step was the coding challenge. I was asked to provide an availability window for the two-day challenge to begin. It was all automatic so everybody being on vacation wouldn't be a problem at all. The invite came right on time and then it came again; I was invited twice. No worry though, I'm reading through the thing and knew to leave a comment in the issue/pull request and somebody would help. The GitHub issue outlining the challenge encouraged candidates to commit their code in stages so the progress on it could be walked through in the technical interview. Well, I spent a couple hours on it and made the pull request, planning to spend a final hour the next day to polish it. It turns out the information the lovely recruiter gave me was wrong and my access was closed right away, with the steps not completed. I tried to get in touch with somebody and luckily I got an email. The email explained that the challenge was actually only eight hours and that it was unfair for me to have more time, but, go ahead. But I didn't have the right access(!), luckily I was able to work around it with a fork. I wasn't impressed with the bad information and how that was handled. Applicants beware: Verify with your recruiter just how long you have to work on it and plan for less time just in case. Evidently my code was alright enough to qualify for the next round of Zoom interviews. Again, I would have to provide availability, which I did, even though one of the two emails I received to do so wasn't valid. The sequence of interviews wasn't explained well at all because when we got to them it turned out that one of the two from the first interview wasn't there. In the second interview the subject was completely different, with the interviewers literally reading from a sheet of paper (laughing about how strict the process was). The coup de grace was the final interview. The individual explained that if the recruiter wasn't responding quickly to skip them and just email him because "have you read Glassdoor? They're not very good." I'll admit that it was a red flag and that working with that kind of attitude was kind of a danger. We had a nice enough chat, however, where he lead off with "The answers don't matter, I just care how you answer," which is bit rubbish because why are we even here if what I say doesn't matter? Anyways, we wrapped up and he said he wasn't sure about some things he had reservations about; he never asked questions to clarify or probe further. I volunteered additional sources which addressed one of his concerns. Almost an entire week passed with zero contact from anybody at GitHub and it wasn't until I emailed that I was told "Yeah we're really busy this week." Okay, that happens. Three days later the recruiter emails back to say they're going with other candidates. Along the way there was no acknowledgement of me expressing additional interest in a similar role that was published after my application was in. I wasn't given any kind of explanation other than "we're going with other candidates." Most of the people in the interviewing process seemed like very nice people, but were restricted by the system they find themselves in. However, the system needs to be improved so that candidates are provided an equal, fair and consistent experience. It is also bad form to trash talk your coworkers, so maybe work on that?

      Interview questions [1]

      Question 1

      Solve this Ruby coding problem
      Answer question
      3

      Top companies for "Compensation and Benefits" near you

      avatar
      Amazon
      3.7★Compensation & Benefits
      avatar
      Google
      4.5★Compensation & Benefits
      avatar
      Meta
      4.6★Compensation & Benefits
      avatar
      Amazon Web Services
      3.9★Compensation & Benefits