Taro Logo

Senior Software Engineer Interview Experience

December 1, 2021
Negative ExperienceNo Offer

Process

I applied online and received a take-home assignment via email. The assignment was pretty straightforward, involving the implementation of some functionality in a simple CRUD-like application. They imposed a hard limit of 5 hours, restricted by repository access, to complete the assignment. I took about 4 hours to finish it, using JavaScript.

Subsequently, I received no correspondence for at least two weeks. I reached out, and they sent an email to schedule an onsite interview. However, by that point, I already had other offers on the table and no time to fit the onsite in.

I did not have any face-to-face or phone interaction with anyone. They had not reviewed my code submission until I emailed them a couple of weeks later. While I appreciated the absence of LeetCode questions and the focus on practical skills, there was a definite lack of human interaction and communication on their end.

Questions

Store, update, and delete data via API endpoints.

Was this helpful?

Interview Statistics

The following metrics were computed from 21 interview experiences for the GitHub Senior Software Engineer role in United States.

Success Rate

29%
Pass Rate

GitHub's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive38%
Neutral10%
Negative52%

Candidates reported having negative feelings for GitHub's Senior Software Engineer interview process in United States.

GitHub Work Experiences