GitHub Engineer 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
Candidate interview experiences
First-hand accounts from people who interviewed at GitHub.
GitHub
Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding
It was a pretty good and smooth interview process. It had most of the typical questions for any technical interview, so you don't need to prepare anything extra specific. One important thing though: be ready to showcase some of your previous projects or open source contributions.
Confirmed questions2 questions
- Could you tell me how many years of experience you have?
- Can you showcase some of your previous projects or open source contributions?
GitHub
Data Center Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical
I was screened by a woman, but the hiring manager was male. I have over twenty years of experience in data centers. The hiring manager asked a lot of STAR-based questions. I talked about the various saves I did over the years, like catching mistakes such as installing circuits in the wrong location. A lot of work in data centers is routine, and even upgrades and patches are not difficult. I was rejected a few days later because I wasn't considered technical enough, which I found insulting given my background. I have a master's degree and twenty years of experience working my way up from the bottom, installing servers, loading software, troubleshooting, and doing turn-ups. I complained to HR about the perceived chauvinism. The hiring manager told me I didn't have enough technical experience, which I found surprising given my extensive background. I was very disappointed with Github.
Confirmed questions1 question
- Tell me about a time you experienced failure.
GitHub
Engineer
Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Behavioral
It was a pretty long interview process, lasting about two weeks with many rounds. Each interview got progressively harder. But it was all worth it in the end, because I got the offer!
Confirmed questions3 questions
- Can you describe the hardest engineering project you worked on in the last year?
- What software packages do you know?
- What's the coolest thing you can do with one of those software packages?
GitHub Engineer Interview Questions
Quoted word for word from GitHub interview reports.
“What's the coolest thing you can do with one of those software packages?”
Read reports →“Did you sign an NDA?”
Read reports →“Did you sign a non-disclosure agreement?”
Read reports →“What software packages do you know?”
Read reports →“Tell me about a time you experienced failure.”
Read report →“Could you tell me how many years of experience you have?”
Read report →“Can you describe the hardest engineering project you worked on in the last year?”
Read report →“Can you showcase some of your previous projects or open source contributions?”
Read report →“Can you describe how you collaborate with past managers?”
Read report →Formats, difficulty and experience
Across all 6 GitHub interview reports.