Contrary to my assumptions, i found the interview pattern simple. Each interview lasted for 1 hour and it consisted 3 questions precisely. a. Quick Question about OOPS. b. Question related to functional - preparing a exhaustive test case list for a typical Web service architecture. c. Coding Question - A typical challenge was thrown associated with arrays, matrix and they expect to arrive with design and coding with in the stimulated time. Trust me, they expect the fine tuned code with in the first attempt itself. No excuses. Interviewers might give some focus points if they think if you are missing something or lacking - try to seek that point and explain about that area. You can't skip that point. Preparation around coding challenges around arrays, strings, matrix and linked lists would be helpful.
Sigiloso
Though i was able to answer the questions correctly - i got to know that they rejected me stating that the solution i provided them wasn't an optimized approach. And another reason was that they mentioned that i did not covered the test case generation well for the area the interviewer mentioned during the discussion.