Telephonic round: The interview started with no introductions... open coderpad, copied a problem... "read the problem and solve it". I tried explaining the problem and how i would solve it, but the interviewer did not have the patience to listen. Anyway I started coding and there was a STL warning for which I thought I would ask a question. I got the response "I do not know C++". In all, my code compiled but the O/P was not correct... I ran out of time. As expected I got a reject. But the experience was one of the worst I had gone through in my 12 years of industry experience. The person on the other side of the phone was super rude and I completely missed the point of such an interview (they can very well give me a timed coding challenge and that way I would have done the same without the weirdness of talking over phone with a rude person). I would recommend folks to rather put your brains towards a better company (with humble people).

They offer you either phone interview or online test. would recommend online test and cheat as the level of questions is freaking hard. If you go for phone interview, the phone interview is gonna be harder as the level of questions is too high

A phone interview which asked to solve a coding problem (coding, compile, come up with your own test, and run) within 40 minutes. The coding was not hard. But the testing phase was not clear. The interviewer didn't mention anything about how to process the input. The interview was mainly to find out if you can code quickly and cleanly (no bug). They didn't care about your industry experience and other stuffs on the resume. As long as you can code, you'll be fine. And they seemed to put a junior person on the interview who sometime gave wrong comment about the code. It could be part of the interview process - to see how you approach to vague/wrong description of the problem.