Recruiter contacted me, reasonably quickly [within a week] after applying online and was generally very helpful. But the first interviewer started phone interview around 10 minutes late [in the end ending up kicked out of conf. room] and asked two very simple questions. One of the questions was given 2 arrays of size n and 2n containing n elements only, both sorted in ascending order, How will you merge, first array with second [which has size 2n] into second array in ascending order. I just used merge sort merge step and wrote java like psuedo code in collabedit. I tried out my code later and it worked fine with no changes [except that I used .length() instead of .length for array length]. But he didn't provide any feedback on what he was looking for. It was correct and complexity was the best possible. One thing I can think of later was I didn't add any method level comments [although I had comments in body] as it was pseudo code. Maybe he was looking for it [pure guess - as I don't know what he wanted]. I left with impression of having done the interview very well [I have worked in the best of companies and got interviewed and interview for those companies] and most of the time you know when you blew it. But I was surprised to get the rejection, 2 days later! Particularly given that question was too easy! Now I am left pondering over what was it? I consider interviews where the perception of interviewer and interviewee differs wildly in terms of performance as bad interviews with negative experience associated with it, as the interviewer didn't communicate his intention with the interviewee properly. If he was not looking for correctness and perf. [objectively defined as mentioned above], What was it?