GitHub·Software Engineer

GitHub Software Engineer interview experience

No offer

Medium

Negative

SydneyPosted Oct 2023 · Candidate report, summarized by Dataford

I went through an early-stage GitHub process that looked straightforward on paper but felt difficult because of missteps, rigid criteria, or poor coordination, and I didn’t move forward.

Recruiter screen — I discussed experience and fit, but the recruiter stage raised concerns for me (e.g., overly aggressive salary negotiation, or questions that felt misaligned with HR).
Take-home assessment — I was given an assignment that either seemed incorrect for the process or created wasted time.
Technical interview attempt — After the assignment, I still hit barriers such as criteria not matching (like required years of experience), or lack of follow-up after completing steps.
No/limited feedback — In the end, I received rejection/closure without meaningful

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