Process
I applied online, and a recruiter contacted me a few days later by email to schedule a phone interview.
During the phone interview, she asked me about my previous experience and what I was currently working on. Then, she told me more about GitHub and gave me time to ask some questions. At the end of the phone conversation, she gave me a take-home assignment in Ruby on Rails.
A few days after I submitted the completed assignment, she informed me that, at this moment, they had decided not to continue with my application.
If you don't have experience with Ruby or Ruby on Rails, don't even apply; they expect you to know it well.
Questions
Take-home assignment in Ruby on Rails
Was this helpful?
Interview Statistics
The following metrics were computed from 44 interview experiences for the GitHub Software Engineer role in United States.
Success Rate
GitHub's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for GitHub's Software Engineer interview process in United States.
GitHub Work Experiences
- 5.0Culture of a startup with the backing of an MNCSoftware Engineer • Current EmployeeHyderābād, Telangana, IndiaMay 14, 2021Pros: Awesome people, lots of new projects. Perks like upfront home office, L&D, and mobile reimbursement.Cons: In GitHub India, a shadow of MS culture can still be seen.
- 4.0Great place to workSoftware Engineer • Current EmployeeHyderābād, Telangana, IndiaMarch 15, 2023Pros: - Good work-life balance. - No micromanagement.Cons: Constant reorgs. Pay could be better.
- 4.0Great place to workSoftware Engineer • Current EmployeeBoston, Massachusetts, United StatesJanuary 30, 2024Pros: Good people. Great engineers. Good comp.Cons: Company focus is shifting towards all AI, focused on driving revenue and losing some of that GitHub magic feel.
GitHub Interview Questions
