GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Easy

Negative

United StatesPosted Feb 2021 · Candidate report, summarized by Dataford

I experienced a recruiter-first flow that asked for substantial work up front and then ended with rejection or a canned excuse, without meaningful clarification.

Recruiter outreach via email — I was asked to answer multiple long, multi-part behavioral questions asynchronously.
Wait + rejection — I received an autogenerated rejection after a long silence.
Timed assignment (other attempt) — In another run, I was given a 4-hour timed assignment and could not get clarification because questions weren’t really possible; it felt like they wanted a very specific approach.
Canned rejection — I was rejected with a generic “many other candidates” message and no elaboration. Outcome: No offer; the main takeaway was that the

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