Taro Logo

Software Engineer Interview Experience

February 1, 2022
Positive ExperienceGot Offer

Process

  • Take-home coding exercise
  • Virtual onsite

All done very quickly. The recruiter was not very talkative but was very efficient.

Took the opportunity to meet with the hiring manager. Turned down the offer because it wasn't competitive.

Questions

Take-home exercise:

  • 5-hour time limit.
  • Provided with a GitHub repo to clone.
  • README with instructions on how to run, test, and requirements.
  • Submission via a Pull Request (PR).
  • The exercise involved making requests to an API.

Virtual onsite:

  • Two behavioral interviews (interviewers were well-liked managers, though not for the target position).
  • Another coding exercise, similar to the take-home.
  • A Pull Request (PR) review to assess handling of ambiguity when joining a new project and reviewing unfamiliar code (hint: ask questions about why and what).

Was this helpful?

Interview Statistics

The following metrics were computed from 44 interview experiences for the GitHub Software Engineer role in United States.

Success Rate

14%
Pass Rate

GitHub's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive45%
Neutral14%
Negative41%

Candidates reported having mixed feelings for GitHub's Software Engineer interview process in United States.

GitHub Work Experiences