Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      GitHub

      Questa è la tua azienda?

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su GitHub | Offerte di lavoro di GitHub | Stipendi di GitHub | Benefit di GitHub
      Colloqui di GitHubColloqui per Site Reliability Engineer presso GitHubColloquio di GitHub


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Site Reliability Engineer

      27 apr 2018
      Dipendente anonimo
      Offerta accettata
      Esperienza positiva

      Altre recensioni di colloqui per Site Reliability Engineer presso GitHub

      Colloquio per Site Reliability Engineer

      8 ott 2021
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso GitHub

      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso GitHub

      Colloquio

      I came to GitHub through a personal referral, so my interview process started with a video chat with a Director then proceeded with an email then video chat with a Talent Partner (recruiter). About two weeks after my initial conversation with her, I was invited to sign an NDA and provide my availability for a first-round interview. The first round was scheduled on a Friday; the day before I was provided with an exercise to be discussed during the first round interviews and was instructed not to spend too many hours on it. By the following Friday I knew that I had made it to the second round of interviews. My final round was then scheduled for the next Friday. The second round included another exercise which was provided to me on Thursday via a private repo and issue before the final interview. Both first and second round interviews were done via Zoom video chat. The Monday after my final round interview, I knew that I was going to receive an offer. My talent partner stayed in close touch with me throughout the process, giving me her personal cell phon number and asking me to text or call her any time. I only had to reach out to her directly once to ask for an update (in between the first and second). My only complaint was that going into each interview I had very little idea of what each session would be like, only that I was meeting with X number of people over X hours. Overall it was an extremely positive process and solidified my interest in working in the SRE organization at GitHub.

      Domande di colloquio [1]

      Domanda 1

      What is a recent project you've worked on?
      Rispondi alla domanda
      8

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Interviewer did not show up
      Rispondi alla domanda
      8

      Colloquio per Site Reliability Engineer

      20 ago 2018
      Candidato anonimo a colloquio
      San Francisco, CA
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso GitHub (San Francisco, CA) nel mese di ago 2018

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

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

      Colloquio per Site Reliability Engineer

      26 lug 2018
      Candidato anonimo a colloquio
      Remote, OR
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso GitHub (Remote, OR) nel mese di lug 2018

      Colloquio

      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?

      Domande di colloquio [1]

      Domanda 1

      Solve this Ruby coding problem
      Rispondi alla domanda
      3