Real, anonymous reports from people who interviewed for Software Engineer at GitHub, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role with a medium-difficulty process over about a month, moving from HR contact into several leadership interviews.
I went through a longer, more confusing GitHub hiring journey where the interviews were standard, but the communication and follow-through became the main pain point over many weeks.
The interview process typically begins with a recruiter screen that assesses background and fit, often followed by a coding assessment through platforms like Codility or HackerRank. Candidates noted that communication during this stage can vary significantly in clarity and helpfulness.
Candidates can expect multiple technical coding interviews, which may include live coding, data structures, algorithms, and system design discussions. The difficulty of these rounds can range from medium to challenging, with an emphasis on practical problem-solving skills.
Behavioral interviews are a key component of the process, focusing on cultural fit and alignment with company values. Candidates reported varying experiences, with some interviews feeling more adversarial or interrogational than conversational.
The overall interview structure is generally multi-step, often spanning several weeks, with some candidates experiencing delays and poor communication throughout the process. Timelines can be inconsistent, affecting candidate expectations.
Final rounds often involve discussions with senior leadership or hiring managers, focusing on both technical and behavioral aspects. Candidates noted that these conversations can be constructive, even if they ultimately do not receive an offer.
Candidates reported mixed experiences, with some finding the process straightforward and others feeling it was challenging due to communication issues or unclear expectations. Many emphasized the importance of clear feedback and closure after interviews.