CareerCup

It happened at many places. Its not mistake of company. Some interviers are assholes...

Most of the people are like that :) It could be as simple as this - we might come to a solution that is not efficient or we might even be doing some simple mistakes coding our correct solution. It gives them a feeling that we are wrong all along.

+1

man the same thing happened to me in microsoft!! dumb people all over!!

ya most interviwers are ass hole and fools. they dont know anything just asking the famous question and expecting same answer

its pretty common in these days.. this happened with me at microsoft and amazon.....4 large problems of trees and in 1 hr time.. and then he said you have done pretty bad.. i challenge that fellow to write code considering he has never seen the answers.. .
infact in one interview at 24/7 ilab, in one round the person asked me to sort an array of only 0's and 1's .. while i was taking time, he said its pretty basic stuff and i will tell u atleast i know of two solutions and i have given you the simplest problem...that was humilating.. because solving in interview under pressure is always difficult as far as I have seen... somehow in few minutes i solved it.. coincidentally i had done with different method and that hopeless interviewer took 15min to understand that i had written a right piece of code...and he says nice solution...bastard.... strangely when i came back and googled the question, i saw only 2 methods on GeeksforGeeks.. !!!!! shit......in same company for the second round, the interviewer asked me to convert a binary tree to double linked list. frankly i did not knew, because i come from embedded side wherein I do not write binary tree every hour and then need to convert it into a double linked list... it was shocking to see that as a piece of code I had written a function that was taking a pointer to pointer (**) to the struct DoubleList and inside function I was doing a malloc for structure.. He said if you are passing double pointer in that case, when calculating size of struct node, you need to do sizeof(struct node *) instead of sizeof(struct node)... fuck.. that hopeless fellow was not clear on basics of C .. forget Binary trees , Lists.. and was asking a mugged up piece of code.... and moreover by the virtue of fact that there was a glass on his side of seat, he had opened up the careercup page of this program and was literally "Reading" the hint to solve it and was seeing in laptop screen and was telling me.... frankly it was so embarassing to see this.. when i returned back, i searched his profile on LinkedIn and to my shock I noticed that he had Java profile of 5 yrs and had never coded in C.... shit ... how can u mug up answers and come....

frankly career cup was designed to solve some real good problems.. unfortunately every tom, dick interviewer in any xyz company opens the page, and asks any question irrespective of the complexity and time.. he himself may not be able to right that in 15min of alloted time.. bullshit.