Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      GitHub

      Essa empresa é sua?

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa GitHub | Vagas da empresa GitHub | Salários da empresa GitHub | Benefícios da empresa GitHub
      Entrevistas da empresa GitHubEntrevistas do cargo de Software Engineer da empresa GitHubEntrevista da empresa GitHub


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Glassdoor LLC. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Glassdoor LLC.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      As melhores empresas na categoria “Remuneração e benefícios” perto de você

      avatar
      Amazon
      3.7★Remuneração e benefícios
      avatar
      Google
      4.5★Remuneração e benefícios
      avatar
      Booking.com
      4.2★Remuneração e benefícios
      avatar
      Flipkart
      3.5★Remuneração e benefícios

      Entrevista para Software Engineer

      25 de jan. de 2022
      Funcionário(a) sigiloso(a)
      Oferta aceita
      Experiência positiva
      Entrevista com nível médio de dificuldade

      Candidatura

      Candidatei-me online. O processo levou 2 meses. Fui entrevistado pela GitHub em nov. de 2021

      Entrevista

      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.

      Perguntas de entrevista [2]

      Pergunta 1

      What are the things that make an application production-ready?
      Responder à pergunta

      Pergunta 2

      What was a mistake you have made that you learned from?
      Responder à pergunta
      20

      Outras avaliações de entrevista de vagas de Software Engineer da empresa GitHub

      Entrevista para Software Engineer

      21 de mai. de 2026
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência negativa
      Entrevista com nível médio de dificuldade

      Candidatura

      Fiz uma entrevista na empresa GitHub.

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      Behavioral questions and previous work experience
      Responder à pergunta

      Entrevista para Software Engineer

      5 de fev. de 2026
      Candidato(a) sigiloso(a) à entrevista
      New York, NY
      Nenhuma oferta
      Experiência neutra

      Entrevista para Software Engineer

      23 de mar. de 2026
      Funcionário(a) sigiloso(a)
      Oferta aceita
      Experiência positiva
      Entrevista fácil

      Candidatura

      Candidatei-me online. Fui entrevistado pela GitHub em fev. de 2025

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      A game of battlefield. Set up HTTP calls
      Responder à pergunta
      Entrevista com nível médio de dificuldade

      Candidatura

      Fiz uma entrevista na empresa GitHub (New York, NY).

      Entrevista

      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

      Perguntas de entrevista [1]

      Pergunta 1

      One leetcode recursive problem for Oa
      Responder à pergunta