GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Medium

Negative

San Francisco, CAPosted Aug 2017 · Candidate report, summarized by Dataford

I interviewed for a Software Engineer role at GitHub and had a frustrating experience driven by inconsistent recruiter communication and an altered coding assignment.

LinkedIn recruiter outreach — I started with a recruiter screen that went well and led to a different recruiter.
Hiring manager phone chat — The call was positive and I progressed to a coding challenge.
Coding challenge (battleship) — I completed the initial challenge and then expected next steps.
Recruiter follow-up issues — I had to send repeated email follow-ups, and it took over two weeks to get a reply.
Challenge changed midstream — After the delay, the recruiter said they changed their mind and wanted a different coding challenge. Outcome: I didn’t move

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

GitHub Software Engineer interview experience (2017) | Dataford