GitHub logo

GitHub Product Manager Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 11 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
63.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GitHub.

Showing 3 of 11
GitHub logo
GitHub

Senior Product Manager

Product · a year ago

Senior Difficult Positive experience Decline offer 5 rounds
Interview process
Recruiter call Phone screen Take home Presentation Onsite
Interview formats
Behavioral Presentation

Started with a recruiter call to go over my background and see if I was interested. Then I had a call with a manager to check if my experience matched what they were looking for. After that, there was a take-home test that took about 3-4 hours. I then presented the take-home test to three people back-to-back. Finally, I had an executive call focused on culture and values.

Confirmed questions1 question
  • Can you tell me about your experience with remote work and how you'd manage working with remote teams?
GitHub logo
GitHub

Product Manager II

Product

Mid Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical

So the process here at GitHub for PM II involved a few steps. First, there was an HR screen, lasted about 30-45 mins with a recruiter. They just wanted to get a feel for my background, career path, why I wanted to join GitHub, and if the PM II role seemed like a good fit, you know, expectations and seniority. Also checked on availability, location, and if my salary expectations were in the ballpark. It was a pretty standard, non-technical chat, nothing too deep on product stuff. Then I had an interview with the Hiring Manager, who's a Product person, for about an hour. We talked a lot about my past product work and what I owned, like going from the start of a project to getting it out the door and what happened after. Also covered how I work with engineers, designers, and leaders. They wanted to know about my decision-making, how I prioritize, and deal with trade-offs. It was mostly behavioral and experience-based, no case studies or live exercises. Finally, there were the panel interviews, which took about 3 hours total, three back-to-back 1:1s. I met with the Engineering Manager, Director of Design, and Director of Product. The focus was pretty similar for all of them: how I collaborate with cross-functional teams, my working style with engineers and designers, my product thinking, how I manage stakeholders, influence people, and deal with uncertainty and trade-offs. The questions were pretty much the same across the interviewers, no one really dug into super deep functional areas. And again, no practical stuff like whiteboarding or take-homes, it was all high-level and experience-focused.

Confirmed questions8 questions
  • Tell me about what motivates you to join GitHub.
  • Can you elaborate on how your past experiences and career path align with the expectations of this role?
  • Describe your previous experiences in product management and the scope of your ownership.
GitHub logo
GitHub

Product Manager Intern

Product

Intern Difficult Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Case

The interview process was lengthy and quite beneficial. The questions posed really encouraged deep thinking and a consideration of the step-by-step process, along with comparing potential best options.

Confirmed questions1 question
  • What organizational tool do you use most often?

GitHub Product Manager Interview Questions

Quoted word for word from GitHub interview reports.

What product influencers have you been following recently?

Read reports

If GitHub were thinking about removing a specific product or feature, what steps would you take to determine if it should be deprecated and how would you proceed?

Read reports

Could you complete a case study on whether GitHub should mandate legal names on all internet profiles?

Read reports

How do you effectively manage stakeholders and exert influence?

Read report

Tell me about a digital product you like, and what you would change about it.

Read report

Formats, difficulty and experience

Across all 11 GitHub interview reports.

Interview formats

Behavioral 44%
Technical 24%
Presentation 20%
Case 8%
Other 4%

Interview difficulty

Easy 9.1%
Average 54.5%
Difficult 36.4%

Candidate experience

Positive 63.6%
Negative 9.1%
Neutral 27.3%