I applied online. The process took 3 weeks. I interviewed at GitHub in Oct 2017
Interview
I applied in late September/early October. I was sent three questions to write out answers to. After I submitted those, someone reached out to me in a timely manner to set up a time for a phone screening/process overview. During that call, the entire interview process was explained to me, I was asked general behavioral questions, and I was able to ask any questions I had about the process. The next part of the interview was a video call behavioral/skills interview. I was asked a few behavioral questions and then a few applied technical questions (real-life scenarios to test data structure/algorithmic understanding). After that, there was a short period of no communication, but I reached out to my recruiter and got a response almost immediately. The final round was a live coding challenge with two engineers on the team I applied for. They were kind and very helpful throughout the hour-long coding challenge. The entire process was organized, responses were timely, and it was all very personal, which was such a nice break from the classic coding challenges most software engineering positions require.
Interview questions [1]
Question 1
Best data structure for a university trying to represent classes and their associated departments
Really nice people the entire time through the interview process and really made me feel comfortable during the entire process. Everything was done over video call making it really convenient for me
I applied online. The process took 2 weeks. I interviewed at GitHub in Oct 2015
Interview
Initial interview was an hour with two engineers, discussion and coding exercise. Second round interview was two hours of coding exercises with two engineers, along with another hour with others of interview. All over videoconference/screen sharing.
I messed up the coding interview by being too nervous. There wasn't anything in the exercises that particularly intimidated me -- they were well-crafted exercises, not requiring too much contextual knowledge, the right kind of tasks for this kind of interview. However, I hadn't done interview code exercises like this before, nor do I have much experience pair programming, programming in front of an audience was a new experience for me, and made me pretty nervous especially when I knew I was being evaluated. I was nervous and jumpy, and it showed, and in the feedback given by the recruiter, this was the reason I was turned down, I seemed hurried and not confident.
I guess my advice is do your best to stay calm and collected and one step at a time in code exercises in interviews!
All around, but for that, the interview process was good, relatively speedy, with the interviewers showing care and consideration for the candidate.