I recently applied for a senior role, and a recruiter reached out asking me to complete a coding exercise. I had 5 hours from the moment I started it.
It was a simple exercise that asked me to create basic HTTP services for uploading and downloading files. A few unit tests needed to pass.
I completed the exercise by taking into account proper solution structuring, registering DIs, creating repositories, services, and models, etc. I think it was a pretty good solution for the problem described.
I even wrote a detailed paragraph explaining how the code could be improved in a real-world use case.
The recruiter sent a rejection email a week later and did not provide any feedback.
At this point, I think GitHub's interview process is crap and would not recommend people to go through the same thing I did.
Implement a data storage API in .NET with 3 REST-based APIs and a few unit tests.
The following metrics were computed from 21 interview experiences for the GitHub Senior Software Engineer role in United States.
GitHub's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for GitHub's Senior Software Engineer interview process in United States.