GitHub logo

GitHub Program Manager Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GitHub.

Showing 3 of 6
GitHub logo
GitHub

Program Manager

Operations · nearly a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

The whole hiring process took over two months, and the communication was the main problem. There were really long gaps between interview stages with hardly any updates. I constantly had to chase them to find out if anything was happening, and they never gave me any timelines, feedback, or a clear idea of what was coming next. This lack of basic organization made what could have been a great opportunity feel like a frustrating and demotivating experience. I even had to contact the scheduler because the recruiter wasn't getting back to me. Even though the people I spoke with were smart and really nice, the overall recruiting process felt messy and like it wasn't a priority, which left a bad impression. Because of this, I wouldn't consider applying or interviewing with them again unless they seriously improve their process and how they communicate.

Confirmed questions4 questions
  • Can you share an example of a basic situation you encountered and how you dealt with it?
  • Describe a situation using the STAR method.
  • Could you give an example of a time you managed different groups of people?
GitHub logo
GitHub

Senior Program Manager

Operations · more than a year ago

Senior Average Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

First, there's an HR screening for about an hour. If that goes well, there are about two or three more interviews, each lasting an hour, with the Hiring Manager, another program manager, and other folks in the company.

Confirmed questions1 question
  • Can you explain the Project management life cycle?
GitHub logo
GitHub

Program Manager

Operations

Mid Average Positive experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Recruiter set up an interview for a week out. I signed the NDA and they confirmed the date. When the interview date arrived, the recruiter didn't show up. I emailed them to see if we should reschedule. They called me 30 minutes later, apologizing and saying they were out sick, and asked me to reschedule. I told them to feel better and we'd talk the following week. I sent my availability again... radio silence. A week passed, I followed up again. Still nothing. I found out a week later that they closed the position via an automated message. Wasted my time.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

GitHub Program Manager Interview Questions

Quoted word for word from GitHub interview reports.

What is your perspective on GTM strategy to increase adoption?

Read reports

Describe how you would manage a team that isn't performing well.

Read reports

What was your part in a program that was successfully launched?

Read report

Could you give an example of a time you managed different groups of people?

Read report

Formats, difficulty and experience

Across all 6 GitHub interview reports.

Interview formats

Behavioral 54.5%
Technical 36.4%
Presentation 9.1%

Interview difficulty

Easy 16.7%
Average 83.3%
Difficult 0%

Candidate experience

Positive 66.7%
Negative 33.3%