It's a 2-step process. Firstly, you get a phone screen.

The engineer I talked to was very nice. He showed great interest in knowing about my past projects and experiences. We talked for about 30 minutes.

Then I was given a coding challenge over an online code editor. The problem was easy, and I think that he wanted to see if I could come up with the simplest solution or not. After I solved the problem, we again talked for 10 minutes, and this was my turn to ask questions. He made sure to answer all my questions (I had a lot).

Within a day or two, I was told that they would be flying me in for the final round. I had two interviews on-site.

In the first interview, I was asked about my work experience during the summer. After that, I was given a coding question on state automata. The interviewer was again very helpful and did a great job explaining the problem to me.

The second interview was on algorithms. The interviewer straight away jumped to questions without wasting any time. He explained the concept of parallel programming and, while explaining it, asked me questions on complexities at various stages of the concept. This was again a great experience for me. His explanation was so solid that I immediately registered for a parallel programming course when I came back to university.

After these 2 interviews, I had lunch with another engineer. After that, they told me that they wouldn't be proceeding with my interview.

Lastly, the recruiter was fantastic in following up. She made sure to reply back within a day or two. Not only that, she was also quick in arranging interviews and made the process really fast.

I have interviewed with companies like MS, Twitter, and IBM Watson, and this was a far better experience than others.

Conceptual algorithmic questions