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?

      Circa
      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 Software 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 Software Engineer

      25 gen 2022
      Dipendente anonimo
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso GitHub nel mese di nov 2021

      Colloquio

      I applied to GitHub through their careers page. I heard back from them a little over 3 weeks later. A month after that they made me an offer. It was a great experience! Here were the steps I went through: 1. The recruiter reached out asking me to complete a pre-technical exercise. This is the same exercise mentioned in other comments here to build a REST API. I had 5 hours to complete in the language of my choice. I was able to finish the assignment under the time allotted and used the remaining time to make improvements and add test coverage. In retrospect, I don't think that was necessary as this assignment didn't come back up in later stages of the interview. It took them a day to respond saying that I had passed that test. 2. A couple of days later I had an interview with the recruiter. She had a few questions about diversity and inclusion and it felt very much like a conversation. She also spoke a little bit about the role, although at this point, the team I was interviewing for wasn't defined yet. They were basically putting all SWE candidates through the same process and only assigning us to specific teams in the later stages. 3. Then came the technical interview. This took a couple of weeks to happen because of a holiday and they wanted to schedule candidates for a Tuesday and Thursday of the same week. On Tuesday, I had 2 pairing technical interviews, 90 minutes each, with a 30 minute break in between. There were 2 different GitHub engineers for each of the 90-minute blocks that were all part of different teams. The first 30 minutes of the first block were all behavioral questions. A lot of questions about managing technical debt, managing projects, resolving conflicts. Then, we started working on a problem together. I had to build a client app / script that did some data wrangling and posted to an API. It mostly involved talking out loud as I solved the problem and them asking why did I choose to do something or "what if" questions. Then I had a 30 minute break and I started the second 90 minute block with 2 different engineers. We picked up the problem where I had left off. At this point, we started working through edge cases, validations, and other considerations. Once there were 30 minutes left, they started asking behavioral questions around similar topics the previous engineers were asking me. 4. Final round of interviews. The technical interview described above happened on a Tuesday. On Wednesday, they got together to decide whether I made it through and which org I'd be a candidate for. On Thursday, I had my final interviews, which were 30 minutes with a director and 30 minutes with the hiring manager. The first thing the director asked me was how the process was going so far and I mentioned it was very positive and that I didn't have high expectations given the kinds of comments I had read on Glassdoor. He said that they had dropped the ball in the past and that they were working to improve it and I loved that. Very honest about previous mistakes and embraced continuous improvement. The director asked things like why do you want to work at Github and general experience. The hiring manger had some good questions about diversity and inclusion and also about general process of working in a production application. Both were incredibly nice and felt much more like a chat than an interview. I received an offer the following Monday. Some general thoughts: * Everyone was incredibly nice and made me feel as comfortable as possible. * They were really big into behavioral questions and no one was really asking follow-up questions to my responses, so just make sure your response is clear. * Everyone left time for me to ask questions, so I would recommend having some good questions ready.

      Domande di colloquio [2]

      Domanda 1

      What are the things that make an application production-ready?
      Rispondi alla domanda

      Domanda 2

      What was a mistake you have made that you learned from?
      Rispondi alla domanda
      20

      Altre recensioni di colloqui per Software Engineer presso GitHub

      Colloquio per Software Engineer

      21 mag 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso GitHub

      Colloquio

      There were a total of four interview rounds: a recruiter screening, a hiring manager interview, and a loop consisting of system design and coding rounds. The interviews went very well, and after each round, the interviewers seemed highly impressed and mentioned that I would hear back from the recruiter soon. However, I was ultimately rejected because the decision came down to a very close comparison between me and another candidate. Additionally, the recruiter was not very helpful throughout the process, which made the experience more frustrating.

      Domande di colloquio [1]

      Domanda 1

      Behavioral questions and previous work experience
      Rispondi alla domanda

      Colloquio per Software Engineer

      5 feb 2026
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso GitHub (New York, NY)

      Colloquio

      Gave OA after passing the interview screening. Recruiter will reach out it was only 1 problem in the OA on hackerrank to solve and recruiter will reach out immediately after that’s been solved

      Domande di colloquio [1]

      Domanda 1

      One leetcode recursive problem for Oa
      Rispondi alla domanda

      Colloquio per Software Engineer

      23 mar 2026
      Dipendente anonimo
      Offerta accettata
      Esperienza positiva
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso GitHub nel mese di feb 2025

      Colloquio

      Interviewed for SWII. Was straightforward. Had a talk with a recruiter and asked basic behavior questions then told me on the call that I am being pushed to interview day. I was given what the questions might be, Interview day was 2 technical interviews and one cultural. Technical questions was to build a game of battlefield and the other was the set up some HTTP calls.

      Domande di colloquio [1]

      Domanda 1

      A game of battlefield. Set up HTTP calls
      Rispondi alla domanda

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      Amazon
      3.7★Stipendio e benefit
      avatar
      Google
      4.5★Stipendio e benefit
      avatar
      HENNGE
      3.8★Stipendio e benefit
      avatar
      xneelo
      3.8★Stipendio e benefit