Staff Software Engineer Interview Experience - United States
March 1, 2021
Negative ExperienceNo Offer
Process
Recruiter reached out via LinkedIn.
Scheduled a meeting and talked with the hiring manager.
Asked about work experiences, the particular role, and cultural fit.
Ghosted with zero follow-up.
Questions
Why do you want to work at GitHub?
What is one thing you would absolutely not work with?
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the GitHub Staff Software Engineer role in United States.
Success Rate
0%
Pass Rate
GitHub's interview process for their Staff Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Positive0%
Neutral0%
Negative100%
Candidates reported having very negative feelings for GitHub's Staff Software Engineer interview process in United States.
GitHub Work Experiences
4.0
Decent comp for remote
Staff Software Engineer • Former Employee
San Francisco, California, United States
April 15, 2025
Pros: Remote work is the norm,
having a big impact on millions of developers.
Cons: The average GitHub developer is decent, but not as consistently good as at other tech companies I've worked for. There are some pockets of extremely competent engineers, though.
Currently trying to figure out their AI strategy, and both product and management seem to change directions weekly.
5.0
Great place to work
Staff Software Engineer • Current Employee
Seattle, Washington, United States
January 7, 2022
Pros: - Trust by default
- Helpful colleagues
- Supportive leadership
Cons: - Not very aggressive in shipping
1.0
Bad Upper Management
Senior Software Engineer • Current Employee
Toronto, Ontario, Canada
October 24, 2025
Pros: - Salary and benefits are good
- Remote
Cons: - Upper management reports directly into Microsoft in the absence of a CEO.
- This leads to a lot of thrash, long hours, and often burnout in team members.
- 4.0Decent comp for remoteStaff Software Engineer • Former EmployeeSan Francisco, California, United StatesApril 15, 2025Pros: Remote work is the norm, having a big impact on millions of developers.Cons: The average GitHub developer is decent, but not as consistently good as at other tech companies I've worked for. There are some pockets of extremely competent engineers, though. Currently trying to figure out their AI strategy, and both product and management seem to change directions weekly.
- 5.0Great place to workStaff Software Engineer • Current EmployeeSeattle, Washington, United StatesJanuary 7, 2022Pros: - Trust by default - Helpful colleagues - Supportive leadershipCons: - Not very aggressive in shipping
- 1.0Bad Upper ManagementSenior Software Engineer • Current EmployeeToronto, Ontario, CanadaOctober 24, 2025Pros: - Salary and benefits are good - RemoteCons: - Upper management reports directly into Microsoft in the absence of a CEO. - This leads to a lot of thrash, long hours, and often burnout in team members.
GitHub Interview Questions
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
