The process began with a 30-minute call by a recruiter. All positions were remote.
I was given a 4-hour timed assignment to complete on my own time.
I was rejected, and they could not elaborate on the reason why. It was a canned response: "We had many other great candidates apply." This was disappointing, especially considering there was an ambiguous requirement with no opportunity to ask clarifying questions. I felt there was more than one way to implement the requirements, and depending on the chosen route, the outcome could be a hit or miss. It seems they were looking for a specific answer.
Your time means nothing to GitHub, and many other companies, until you are hired. This speaks volumes about a company when, after joining, the emphasis is on "we live and breathe our core values and value everyone."
On the plus side, it wasn't a multi-day assignment, and at least they bothered to reply.
Was asked to create an API solution (CRUD) that can handle multiple parallel requests.
The following metrics were computed from 2 interview experiences for the GitHub Sr. Software Engineer role in United States.
GitHub's interview process for their Sr. Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for GitHub's Sr. Software Engineer interview process in United States.