GitHub Manager Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GitHub.
GitHub
Senior Manager
Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Technical
The interview process was pretty standard for a Senior Manager role, but dealing with the recruiter made it a really bad experience. They asked for my availability for the initial recruiter call but then scheduled it outside of the times I could make. They rescheduled calls multiple times at the last minute, and those reschedules were also outside my availability. It felt like they had zero respect for my time. The actual interviews went okay, I think. I spoke with three different people for an hour each. The conversations were fine and the interviewers were nice. They asked a lot of the usual types of questions. When the recruiter called to let me know I didn't get the job, she first asked me how I thought the interviews went. Considering she was about to tell me I was rejected, that felt really rude and like another waste of my time.
Confirmed questions1 question
- Can you share a significant career achievement, detailing the situation and the obstacles you faced?
GitHub
Management
Mid Difficult Positive experience No offer 13 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Behavioral Technical
I had 8-10 video chats with team members and other managers. Then I had an on-site where I met 5 more people. The whole thing took about 6-7 weeks and was draining, but everyone was really nice and open.
Confirmed questions1 question
- What's your reason for looking at GitHub?
GitHub
Manager
Manager Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical
I got referred by some people I used to work with. It took over a month for anyone from recruiting to reach out after I was submitted. The first screen went fine, and the first round with the hiring manager also seemed to go well. The interview was scheduled for 30 minutes but went for nearly an hour because we had a good discussion about the team's operations and what I could achieve. I was supposed to hear back after the weekend, but after not hearing anything for a week, I followed up. When I followed up, I let them know I had two other offers on the table. Github didn't respond for 10 days. I didn't wait for them at all and accepted an offer two days later with no response. But when they finally got back to me, they had the nerve to assume I was still waiting and told me they weren't moving forward. Good luck to them, they'll need it because if they think the best candidates will wait around for a slow and unresponsive recruiting process, they're wrong.
Confirmed questions1 question
- Can you describe your experience in relation to this role?
GitHub Manager Interview Questions
Quoted word for word from GitHub interview reports.
“What's your reason for looking at GitHub?”
Read reports →“How do you decide what to prioritize?”
Read reports →“What challenges do you foresee with remote work?”
Read reports →“Can you share a significant career achievement, detailing the situation and the obstacles you faced?”
Read reports →“Tell me about your previous work experience and how it relates to this position.”
Read report →“Can you describe your experience in relation to this role?”
Read report →Formats, difficulty and experience
Across all 8 GitHub interview reports.