I have seen a lot of interesting characters in both interviewers and interviewees. However, few weeks back I came across a conversation which forced me to write this. All this started with a very a simple/routine question
1. What is MVC?
Interviewee explained his understanding ( From my personal opinion, he was right and that’s what you can expect from average 4-5 yrs experienced guy in an ITES Industry). I’m not going to discuss this answer here because that’s not the intention of this post.
2. Interviewer took note of what he said and asked why do we need to all this, can’t I write everything in JSP itself and leave that?
Now, Interviewee explained JSP’s intent was not to write java code and it should just have HTML and other data should come from business classes, so writing all in JSP is not the rightway.
3. Interviewer doesn’t worry about the answer, he still went on what if I don’t bother about rightway’s, can’t I right them in JSP and work?
Interviewee thought for few minutes and asked this question back, If you start having all your BL’s in JSP’s, Don’t you think you repeat your code all around and also you are putting too much effort on client side which is not good.
4. I don’t know what made interviewer angry now, he said in a harsh tone that I will write an include.jsp and put all my code in that. What’s your answer for that?
Now, interviewee got angry and said that I won’t do that because that’s not a good practice from my as well as others point but if you want you can do that stupidity.
Then interview went for few more questions and candidate was rejected by interviewer as we all know.
I just tried to understand what was in Interviewers mind when he asked that question
1. He doesn’t want to select the candidate – Which is very remote given the time and effort taken by us to do the interview
2. He doesn’t know what is MVC or got lost in translation – Yes, there is a 50 – 50 chance for this but not always and from the way he asked the other questions, I think he is not lost at all.
3. He was thinking of a point for that question and expecting interviewee to say that as he knows – I would say this has a 90 – 10 probability. From my experience, this is what happens a when a half cooked guy takes interview.
Here, the problem is the Interviewer might know a valid point but he is not good in asking a direct question to get that answer. He took a longer router and finally annoyed the interviewee because from the outset almost all the answers given by interviewee is correct.
As the saying goes, all good programmers or not good Leaders, same will apply to interviewers as well.