GitHub logo

GitHub Application Support Engineer Interview Questions
& Process

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

Based on 16 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
37.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GitHub.

Showing 3 of 16
GitHub logo
GitHub

Customer Support Engineer

Engineering · nearly a year ago

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

This was a total waste of time and energy. They asked me generic questions about management in a technical role, and the people interviewing me had no technical knowledge at all. Seriously, just a waste of my time.

Confirmed questions1 question
  • Management questions were asked.
GitHub logo
GitHub

Support Engineer

Engineering · more than a year ago

Entry Difficult Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Technical

So I had this really strange interview experience. The recruiter was a bit late to the call, which is fine. But then they admitted they hadn't even looked at my resume (uh oh) and just started firing off random questions. No intro about who they are, the company, or the job. What was weird was that most of the questions were based on assumptions that were either already in my resume or I could have covered in a 'Tell me about yourself' answer. It was hard not to roll my eyes, but I knew this wasn't going anywhere and I wouldn't be moving on.

Confirmed questions4 questions
  • Can you tell me about yourself?
  • How many years of professional experience do you have with Linux systems?
  • Why do you think you're a good fit for this role?
GitHub logo
GitHub

Enterprise Support Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 7 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design Presentation

I got referred for a job at GitHub's Asia-Pacific support team back in October 2016. A few days later, I got an invite for the first interview, and had to sign an NDA. The whole thing took about 7 weeks. All interviews were remote over Zoom, mostly with video. They suggested joining a bit early to make sure your setup works. I fiddled with my camera and mic for about 5 minutes, then it was fine. My first chat was with the APAC hiring manager, supposed to be 45 minutes but went a bit longer. It was pretty chill and mostly non-technical, focusing on getting to know each other, my background, and why I wanted the job. It went well. Four days later, I got asked for a second round, a technical interview with another Enterprise Support Engineer from my region. About a week after that, we did this session over Zoom with a shared SSH connection, working through different scenarios. I think I did okay overall, but got stuck on one scenario. The interviewer was cool though, helpful without giving away the answers too easily. It was still fun even with them seeing my mistakes. I wasn't sure how that one went, so I was happy to get an email a few days later to move on to the final round, which was spread over two days. The first day had four interviews, mostly around 45 minutes, except the last one which was 90 minutes and focused on troubleshooting customer tickets. These felt like casual chats, like talking to a colleague. It was tiring by the end of the day, but I felt really motivated and excited about GitHub and the people I'd met. The second day was the following week. I had an hour with the Director of Enterprise Support in the morning, and then a quick voice call with someone from Talent Acquisition in the evening. Then came the long wait to hear back, made longer by the Thanksgiving holiday. GitHub kept me updated on their timeline though. The week after Thanksgiving, they scheduled a 'follow up' call where they offered me the job, which I accepted right away.

Confirmed questions5 questions
  • Can you explain how you would assist someone who doesn't have a technical background?
  • How would you handle supporting a customer who is experiencing issues with their tickets?
  • Could you share a bit about yourself and what motivates you?

GitHub Application Support Engineer Interview Questions

Quoted word for word from GitHub interview reports.

How many years of professional experience do you have with Linux systems?

Read reports

What steps would you take to assist a customer experiencing performance issues?

Read report

How would you handle supporting a customer who is experiencing issues with their tickets?

Read report

What steps would you take to enhance diversity within the technology sector?

Read report

What is your method for troubleshooting a technical issue?

Read report

Formats, difficulty and experience

Across all 16 GitHub interview reports.

Interview formats

Behavioral 40%
Technical 34.3%
Presentation 8.6%
Other 5.7%
Coding 5.7%

Interview difficulty

Easy 18.8%
Average 75%
Difficult 6.2%

Candidate experience

Negative 62.5%
Positive 37.5%