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

      GitHub

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur GitHub | Offres d’emploi chez GitHub | Salaires chez GitHub | Avantages sociaux chez GitHub
      Entretiens chez GitHubEntretiens d’embauche pour Site Reliability Engineer chez GitHubEntretien chez GitHub


      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 Site Reliability Engineer

      5 déc. 2017
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez GitHub

      Entretien

      I had the same terrible experience as the three previous SRE reviews. I thought I might do better, but the first reviewer was right - applying will be a waste of your time and energy. Their responsiveness and refusal to give feedback demonstrates a complete lack of respect for candidates that doesn't look set to change any time soon. My first call with the recruiter was rescheduled and the new time they suggested clashed with some family commitments, but I went ahead with it because I wanted to get things moving. I dialled into the call and no one arrived. I switched back and forth between the previous call ID they'd given me. I sent an email to ask if I had the right call ID. After 30mins of waiting on the call I got a reply from the co-ordinator to say that the recruiter's computer wouldn't turn on and that we'd have to reschedule again. The next rescheduled call came a month after I'd first applied. Having read the other reviews here I mentioned that I was interviewing with other companies and was keen to speed up the process. I was told that it wasn't a problem and that they'd got someone through in just 2 weeks before. I asked about how the role differed from the Platform Reliability Engineer and Infrastructure Engineer roles they were also advertising. The recruiter wasn't sure about the details but said that they'd email me some more information and I could come back to them when I had decided which I'd prefer to apply for. They made a point of sending an email to a colleague to request more information while we were on the video call. The next day I received a technical test for the PRE role, out of the blue, without any additional information or conversation. I responded with a summary of our previous conversation and (attempting to speed things up) explained that I just wanted to continue applying for the SRE role. I repeated this several times and didn't get a reply until 3 weeks later. They hadn't actually read my email though because the response said that they'd been waiting for me to complete the PRE technical exercise and proceeded to send it to me again. Eventually we managed to schedule the SRE technical exercise, but there was no apology for their mistakes. The exercise needed to be completed within an 8 hour time limit. So I arranged it for a weekend and my wife took our children out for the day so that I could concentrate. The exercise was fun and interesting, but very time consuming and it wasn't at all clear how it was being evaluated. I was happy with my submission (good README, tests, commit messages) but exhausted by the time I'd completed it and I'd lost a day with my family. I sent emails afterwards asking if they'd received my submission and when I could expect to receive feedback. 2 weeks later I got a response to say that they were still reviewing it and that it had taken longer than normal because of Thanksgiving. To my surprise I received an email the following day to setup a call with a hiring manager. The call with the hiring manager took place within the same week. I thought the call would be about my technical exercise submission, so I refreshed my memory of that and thought about some improvements to talk about. Instead the questions were about "tell me a time when" and "what are your thoughts on". I thought it went OK. The next day I received a stock email from the recruiter to say that they had "decided to move forward with other candidates". No explanation why - I have no idea why I was unsuccessful at such an early stage or what it is they're looking for. I asked for feedback but unsurprisingly haven't received a reply to my email and I know from the previous reviewers that they'll refuse to give it anyway. The stock email ends by saying that they "encourage you to continue looking at our GitHub Career's Page for future opportunities". Nope, never again. I suggest you don't either.

      Questions d'entretien [6]

      Question 1

      Homework to create a utility that compares DNS records against a YAML file.
      Répondre à cette question

      Question 2

      What does SRE mean to you?
      Répondre à cette question

      Question 3

      What are good leadership qualities?
      Répondre à cette question

      Question 4

      Can you describe an incident post-mortem process?
      Répondre à cette question

      Question 5

      How do you prioritise technical debt?
      Répondre à cette question

      Question 6

      What is the scale of the projects you've worked on?
      Répondre à cette question
      5

      Autres retours d’entretien d’embauche pour un poste comme Site Reliability Engineer chez GitHub

      Entretien pour Site Reliability Engineer

      8 oct. 2021
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez GitHub

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Interviewer did not show up
      Répondre à cette question
      8

      Entretien pour Site Reliability Engineer

      20 août 2018
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez GitHub (San Francisco, CA) en août 2018

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      There is a take-home assessment and it's later the basis of a discussion with a few engineers
      Répondre à cette question
      3

      Entretien pour Site Reliability Engineer

      26 juil. 2018
      Candidat à l'entretien anonyme
      Remote, OR
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez GitHub (Remote, OR) en juil. 2018

      Entretien

      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?

      Questions d'entretien [1]

      Question 1

      Solve this Ruby coding problem
      Répondre à cette question
      3