Taro Logo

Software Engineer - Ecosystem Interview Experience

February 5, 2019
Neutral ExperienceNo Offer

Process

After applying, the process kicked off with a 45-minute video call with a Talent Partner, who explained the GitHub hiring process.

Following this, I had to schedule a time to complete a technical exercise, orchestrated by an automated system.

The technical exercise lasted up to 4 hours and involved implementing a simple API in either Ruby (Rack) or Go. It was a really great technical assessment, honestly.

My only gripe is their communication afterward.

When the exercise was completed, I didn't receive a reply. When I followed up two weeks later, I was told it would be reviewed by engineering managers.

Eventually, a month after the exercise, with almost no communication from them, they informed me that they were closing the position while management planned their 2019 headcount.

Questions

What are you looking for in your next role?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the GitHub Software Engineer - Ecosystem role in United States.

Success Rate

0%
Pass Rate

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

Experience Rating

Positive0%
Neutral100%
Negative0%

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

GitHub Work Experiences