Process
The interview process involved several steps: talking to the recruiter, then the hiring manager, completing a take-home assessment, a video call to review the assessment, and finally, a "final" interview. I made it as far as the video call to review the take-home assessment. They did not ask any "BS LeetCode" questions; all inquiries were straightforward. Everyone I interacted with was incredibly nice. However, the recruiter ghosted me after the take-home assessment. I had to reach out after a week to get a status update, and she then provided feedback on why I wasn't selected.
Questions
Signed NDA. Can't answer, sorry.
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
- 4.0Remote work and autonomy, but management issues persistSoftware Engineer • Current EmployeeNew York, NYMarch 24, 2026Pros: Fully remote (if you like that), autonomy, and a developer platform.Cons: Questionable management, losing the AI cold war, and a lack of funding in the right places.
- 2.0Do not join GitHub IndiaSoftware Engineer • Current EmployeeJune 10, 2022Pros: - Great culture - Good workCons: - High attrition - Low comp
- 5.0Best work everSoftware Engineer • Current EmployeeJanuary 1, 2023Pros: Flexibility, working from home, and interesting stuff to do.Cons: None at the moment that I can think of.
GitHub Interview Questions
