After filling out the form online, I received an invitation to a meeting a few days later (less than a week).
Then, more or less every week, I had another interview or technical exercise.
After the first interview, I completed a 30-minute live coding exercise. It was very easy, so easy that I thought I was doing something wrong.
Next, I received a description for a home coding exercise. There was no due date, but I submitted it the very next day. The exercise was not very complex, but it wasn't trivial either.
After that, I was given access to a repository with a pull request, and I had to review the code. I wrote about 120 lines of text in my code review.
Following this, I had a meeting with two engineers who reviewed my code review and asked me many questions.
At this point, there are no more technical exercises, but there are four interviews in the next round. Fortunately, they scheduled them into two groups, so you have two interviews in a row one day and two in a row another day.
These interviews are about culture, values, diversity, and the team.
If you pass them, there's a final, wrap-up meeting.
I thought I was going to get an offer then, but no.
After this meeting, you have to wait for a committee that meets twice a week to give you the thumbs up.
Then, if you get the thumbs up, another department usually takes one day to write the offer. They schedule a meeting for that day if you are available, and you receive the offer.
How do you explain what a database is to a child?
The following metrics were computed from 1 interview experience for the GitHub Senior Ecosystem Engineer role in Spain.
GitHub's interview process for their Senior Ecosystem Engineer roles in Spain is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for GitHub's Senior Ecosystem Engineer interview process in Spain.