GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Medium

Negative

United StatesPosted Feb 2022 · Candidate report, summarized by Dataford

I had an average difficulty process driven by a take-home coding task in a repo, but the experience was marred by delayed review and scheduling friction, ending without an offer.

Take-home assignment (CRUD-like app) — I received an emailed assignment to implement functionality in a small CRUD-style application with a hard limit (tied to repo access).
Limited interaction + delayed feedback — I got little communication; my code wasn’t reviewed until I reached out after weeks.
Scheduling attempt that didn’t happen — I was eventually asked to schedule an onsite, but I couldn’t make room because I already had other offers.
Later live rounds that felt operationally rough — In parallel, I also experienced a stage that depended on live setup details

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