GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Medium

Negative

Stoke-on-Trent, EnglandPosted Apr 2023 · Candidate report, summarized by Dataford

I had a more streamlined GitHub interview journey that started with an assignment and moved into a single day (or close to it), and I ultimately didn’t get an offer.

Recruiter screen / initial check-in — I talked briefly with a recruiter and sometimes completed a short written or lightweight evaluation.
Take-home / assignment — I worked on a time-bounded technical task (language of choice in one case), then submitted it.
Onsite: multiple interviews in sequence — I did a compact set of interviews including behavioral, plus a technical coding interview.
Code/engineering review style technical talk — One stage included reviewing code (less leetcode-like and more practical), plus a mix of behavioral conversations.
**Final

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