Applied online, and after a few weeks, received an automated technical test to work on.
The test lasted a maximum of 5 hours. You receive a repository to work on and have to make a pull request that satisfies requirements. I managed to complete it in about 2 hours and spent some extra time explaining trade-offs in the PR description.
After that, I was contacted by a recruiter. Asked me to fill in a few answers in a form (motivation, experience with programming languages, etc.), then we had a chat in which some basic technical questions were asked.
This was followed by a virtual on-site consisting of:
The live coding interview doesn’t follow the LeetCode-style ones; it’s a more practical exercise during which you share the screen and can consult the internet and collaborate with interviewers.
The interviewers were all nice and professional, but scheduling was a nightmare. It all happened via email exchanges (having to keep in mind time zones), and it wasn’t clearly communicated that interviews only happen on Tuesdays, which made it even more difficult to organize.
Also, GitHub has a strict no-feedback policy. While I understand that feedback is difficult, it can feel pretty hard to gauge where to improve, especially due to their non-standard interview process.
Describe what is a hashmap.
The following metrics were computed from 2 interview experiences for the GitHub Senior Software Engineer role in Netherlands.
GitHub's interview process for their Senior Software Engineer roles in Netherlands is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for GitHub's Senior Software Engineer interview process in Netherlands.