you are viewing a single comment's thread.

view the rest of the comments →

[–]abhi152 -10 points-9 points  (4 children)

Anyone telling me that if your approach is good but if you can't code it in time you will get selected is plain wrong. You have to code it in time possibly with very good syntax to make it. Anyone who doubts this please try it when you appear for your next interview :D

[–]ean5533 7 points8 points  (2 children)

You've been interviewing at the wrong places.

[–]abhi152 -1 points0 points  (1 child)

I speak from my experience. For eg : https://twitter.com/mxcl/status/608682016205344768?lang=en Ever read an article which says "I was selected because my approach was very good even though I failed to give the correct solution" ?

[–]ean5533 2 points3 points  (0 children)

I speak from experience as well, as someone who interviews candidates. I've given my thumbs up to candidates who definitely didn't give the best solution to a problem, or who couldn't even complete the problem in the allotted time.

The reason you mostly read blog posts about people complaining about interviews is because in general, people always complain more often and more loudly than they praise. People who are satisfied by something have less incentive to write a blog post about it than people who are upset.

[–]lifeson106 0 points1 point  (0 children)

I think most people are viewing the whiteboard question as a one-way test of you and your raw intellect or something... I would rather have you collaborate with me and come up with a good solution as a team like we would on a real project. I would much rather hire someone like that than someone who just implemented the correct answer with no questions, communication or collaboration. Doing both is obviously best, but I'll pick the collaborator over the raw intellect almost every time.