I first met with the Engineering Manager for a session that was more behavioral and culture-focused.
Next, I completed a coding exercise. I was given two hours to solve it but could start at any time. I followed all instructions, solved the exercise, wrote tests, and opened a PR with a detailed description of my solution, yet I was still rejected. I have no idea what they were looking for.
Perhaps I didn't solve the problem in the way they preferred. However, the instructions didn't detail any preferred method, and I only did exactly what the instructions asked, without much extra, given the time constraints.
All I received was an automated email stating my rejection with no reason provided. The email was clearly generated from a template, as the signature at the bottom literally said, "Thanks, ENTER NAME AND TITLE HERE". :)
Why do you want to work at GitHub?
What are your expectations of your ideal team?
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.