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 Infrastructure 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.

      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

      Colloquio per Infrastructure Engineer

      2 giu 2025
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva

      Altre recensioni di colloqui per Infrastructure Engineer presso GitHub

      Colloquio per Infrastructure Engineer

      11 mag 2019
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso GitHub nel mese di apr 2019

      Colloquio nella media

      Candidatura

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

      Colloquio

      Overall a very positive experience. I'm unable to go into any real detail due to the NDA you have to sign, but so far it's easily the best interview process I've been through, and it feels the interviewers are looking for more of a realistic metric of how you perform rather than the leetcode style "can you remember X obscure algorithm and implement it in 5 minutes" kind.
      3
      La procedura ha richiesto 3 settimane. 

      Colloquio

      Applied online. First interview was with a recruiter and just talked about my experience and the role. Then later had an interview with a manager, which was also similar. Following that I had a take home coding exercise. This was done via Github, basically you're given access as a collaborator to a private repo and there is a single issue which states the problem and you have to code the solution. The communication regarding this exercise was somewhat confusing as one email said I had 3 hours to do it, and another said I had 5 hours to do it, and that the repository would become read-only after the allotted time. Overall I felt pretty rushed as I did not know how long I had. Solved the problem in Go (one of the languages specified in the position and what drew me to it) so it worked as the issue stated. Following the take home I was scheduled two more interviews back to back. First was 1.5 hour long interview with two other senior engineers / managers. This involved discussion of experience and some questions as well as discussion about the role. 2nd interview was 1 hour interview and code review of my solution to the take home exercise. My assumption was that these interviewers already reviewed and were familiar with my solution. As we went on with the interview based on the questions I received I began suspecting that they had not seen my solution at all. Also one of the interviewers was not familiar with Go at all and kept asking questions about the basics of the language and syntax. The other interviewer seemed more competent with Go. Also the questions asked by interviewers were somewhat weird and unrelevant to the program, and also like they were looking for very specific answers. Overall this was a strange experience compared to a good previous interview with the 2 engineers. Few days later got a generic rejection email.

      Domande di colloquio [1]

      Domanda 1

      Code a program utility used in DSN replication that queries DNS and based on separate input determines what changes need to be made for DNS records. Example usage and input is provided. Explain pros and cons to microservice and monolithic architectures Give an example of something you're proud of and you're role in it. Give an example of a production incident you were involved in and describe resolution and your role in it.
      Rispondi alla domanda
      2