Nothing as of such coming to my mind.
One needs to brush up on their basics before taking the interview. The interview level is average. They focus more on the current project one is involved in. One should be thoroughly expert in their field.
It was good. I was asked OOP in depth. I had two rounds of technical interviews before rejection. As I was working on a Java-based project, I was asked Java in depth.
The first round consisted of coding and technical MCQs. If you are lucky, you might get a simple programming question. There were two technical rounds and one HR round. My friends were asked to write only simple code, like insertion in a linked lis
One needs to brush up on their basics before taking the interview. The interview level is average. They focus more on the current project one is involved in. One should be thoroughly expert in their field.
It was good. I was asked OOP in depth. I had two rounds of technical interviews before rejection. As I was working on a Java-based project, I was asked Java in depth.
The first round consisted of coding and technical MCQs. If you are lucky, you might get a simple programming question. There were two technical rounds and one HR round. My friends were asked to write only simple code, like insertion in a linked lis