No one likes rejection. I've been rejected a lot of times in campus interviews. And, it was not a good feeling.
"I have been rejected, but why?"
This question occurs to a lot of us. Even I did not know the answer to it until I was on the other side of the table. If the reasons are technical qualification, you will yourself know by end of the interview. But most of the times candidates are clueless on which parameters s/he was rejected.
After taking more than a couple of hundred interviews in last 2 years, here are a few parameters apart from technical expertise, I and some of the people I know consider while marking the final stamp on candidates
Can s/he learn?
This is the most important of all the parameters, where an interviewer judges candidate based on his/her learning capabilities. A person who can quickly learn from previous mistakes and doesn't do same mistake again is a what everyone is looking for.
How s/he approaches the problem
It is never important to completely solve an interview problem, but how you approach a problem is what interviewer is looking for. Do not use brute force mechanism to solve the problem otherwise it won't be a problem after all, Take your time and apply whatever you have learned so far, look for focus keywords in the problem and don't just jump to solution, if in doubt ask question.
One dirty fish can spoil the pond
Don't be a dirty fish, your attitude is most important trait you carry. If you are applying in a startup or some of the MNC's there is a high possibility that you are being interviewed by a less experience guy like me, so you should never try to prove the interviewer wrong or argue over a question.
Though only one question shouldn't decide his fate that he qualified for an interview but what came out of this single question was his attitude towards defeat.
Will bringing him in, raise the bar
You must have heard a lot about this round the bar raiser round, I heard it in Amazon's interview process, but it's being followed everywhere in tech industries. In some companies this round is taken after the screening and sometimes it's the last round, if you are lucky enough this may be skipped. Let's see first what exactly is this round:
The team you are being interviewed for has certain critical point the "bar" which decides the standard of a team, for example in a team there are 10 people of which some people are high performer, some average and few below average, now from this a magical number is calculated for team based on performance of these 10 people, Suppose the number is 55(bar).
In this particular round the interviewer judges you on the basis, that bringing you in will raise this number or decrease it. If you raise the bar you are qualified for the round and if you decrease it you are rejected, so in this round you are being compared to average performer of the team and your job in this round is to perform better than average which is as easy as it sounds ;)
Can he guide people
Don't know about other interviewers but I am more inclined to candidates who can teach and guide other colleagues, so I am always looking forward to candidates who explain there solutions in depth. It shows how well you have studied and how seriously you have prepared for the interview. A person who likes sharing is knowledge and keeping everyone updated about latest technology makes a good leader. An introvert person who just does his work cannot be a team player.
Will i go out with him/her for drinks 🍺
I read about this one in Cracking the Coding Interview After taking the interview I do ask this question to myself will I go out with him/her for a beer or drinks(in case s/he doesn't drink). Keeping everything aside, let's jump to ground reality, if you are hired you will be closely working with interviewer and you will be friends with him, so leaving such an impression is also part of the interview. Don't be an obsequious candidate!
If you have any rejection criteria, do share with us in comments till then Read through this strip from commitstrip