
GitHub Engineering Manager Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GitHub.
Engineering Manager
Applied in January, made it all the way to the final stage interviews in March. Even though I did very well and the interviews went smoothly, I just got an email saying I was close but they decided not to move forward. I asked for feedback but didn't get any. I'd really like to work for GitHub, so I just wanted to ask if they could try to give some feedback to those who are not selected.
- Can you share your experience with People Management?
- Can you share your experience with Product Management?
- Could you present an architecture for a complex system you designed?
Senior Engineering Manager
I had a screening call with the hiring manager, followed by another call with the talent partner before the official interview process began. The interview process itself had three rounds, with two interviewers in each round. The talent partner ended my call early due to an errand, instead of rescheduling. The interview process felt rigid, with interviewers sticking to a script and repeating questions even if they'd been covered. Overall, the people didn't seem friendly or interested in my responses, more focused on passing/failing me based on their questions. It was a really strange interview experience.
- General questions were asked, with each interviewer reading from a list.
Engineering Manager
I went through the interview process for two Engineering Manager roles at GitHub. I spoke with two recruiters who were upfront about compensation and benefits, which was helpful. I had to sign an NDA to continue. For the first position, the recruiter moved me directly to the second round. The interviewers seemed disengaged, reading questions and typing my answers, likely due to interviewing many candidates. Although I had significant product experience, they felt I wasn't senior enough. For the second position, after an initial good conversation with a senior engineering manager, someone else was offered the role. The recruiter called me to share the news and circulated my resume internally. Unfortunately, no other suitable roles were available at that time, it felt like bad timing. I'd reapply if circumstances were different.
No confirmed questions were included in this interview report.
GitHub Engineering Manager Interview Questions
Quoted word for word from GitHub interview reports.
“Can you describe the distinction between a good manager and a great manager?”
Read reports →“And how do you manage conflict when it's between you and someone else?”
Read reports →“Can you describe how you would go about improving a team that isn't performing well?”
Read reports →“How do you handle conflicts that arise between team members?”
Read reports →“Could you present an architecture for a complex system you designed?”
Read report →“Could you describe how you foster growth within your team members?”
Read report →“Can you share a story about a difficult situation you faced?”
Read report →“What's your approach to managing competing priorities?”
Read report →“Could you present a complex or large solution that you have designed?”
Read report →Formats, difficulty and experience
Across all 14 GitHub interview reports.