GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Medium

Negative

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

I interviewed for a Software Engineer role at GitHub with an offline/async-heavy technical format, but the communication and feedback loops felt inconsistent.

Recruiter outreach over LinkedIn / initial chat — I was contacted by a recruiter, and the process was set in motion after an initial conversation.
Async technical questions — I received written technical prompts to answer (via email/gist-style formats) before any live interview.
Offline coding exercises — I was given additional take-home tasks delivered through GitHub resources and environment instructions.
Follow-up delays / limited responsiveness — At key points I experienced long waits and limited personal follow-up, with communication sometimes going

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