The first interview is a recruiter screening. You will be described what the job entails and the subsequent interviews.
The second interview was a live coding exercise (in a language of your choice). It wasn't difficult, but you should be comfortable with two people observing you as you code, which can be stressful for some. I was nervous as well but performed well on the task itself.
Next, a take-home test was administered. It required approximately 5 hours of your time and, in my case, involved a Rails project where I had to implement some API endpoints. This was also not difficult.
Then, I had an interview that involved reviewing a Pull Request and debugging code to fix a bug in an API. I enjoyed this task the most because it mirrors day-to-day work. Following this, there was an interview with the engineering manager, after which you wait. In my case, it took 1.5 weeks to be approved for the final stage.
The final stage consisted of three interviews plus a wrap-up session with the recruiter. This included a cultural-fit interview with very open-ended questions and a diversity/inclusion interview. Both of these interviews felt quite scripted, but the interviewers were exceptionally nice. I attempted to engage in more conversational dialogue to make it feel like a genuine interaction rather than just answering prepared questions.
The last interview was with the director, which primarily focused on my questions about GitHub. I appreciated that they answered every question, even those that might have been uncomfortable to discuss.
During the wrap-up interview, salary expectations were discussed, and the further process was explained.
After all these interviews (which took 7 weeks), you await a decision on whether you proceed to the committee. I had to wait an additional 2 weeks to receive a rejection email. The email contained no feedback (which I was aware of beforehand) and was very generic.
I would have appreciated a call or at least some feedback via email, especially after reaching the final round.
Their interview process is generally fine, and I like that they don't use whiteboard tasks. Everyone I interviewed with was extremely nice, and I enjoyed the interviews themselves – the waiting periods between stages were the main drawback, as they took far too long.
I signed an NDA.
The following metrics were computed from 1 interview experience for the GitHub Engineer role in Austria.
GitHub's interview process for their Engineer roles in Austria is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for GitHub's Engineer interview process in Austria.