GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Medium

Positive

United StatesPosted Jan 2022 · Candidate report, summarized by Dataford

I went through a straightforward, average-difficulty flow that combined a coding test with follow-up interviews, with a heavy emphasis on behavioral preparation, and I didn’t advance.

Coding test via GitHub — I completed a coding test using Ruby.
Phone interview to review my code — I discussed my solution and walked through decisions.
Behavioral/policy-focused phone interview — I had a general call covering policies and how well I’d connect with the team.
Outcome: I didn’t move forward; the takeaway was to be ready with clear behavioral stories and concise resolution examples.

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

GitHub Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All GitHub interview guidesEvery role we cover at this company