[san_at_weblegit]

1. As an engineer I would definitely not work with a team that comes up with the first reason for rejection (Provided that I have not mentioned that stack on my resume to begin with).

2. The second reason is more of a choice of the given company. There are companies on the other hand which give out an offer all based on cultural fit. More than often good interviewers never make a decision on the result of the puzzles but on how the candidate approaches it. Downside is that not all people are up for it in the interview hour even if they are really smart otherwise.

3. Third is bad luck (cause of disorganized recruiting). The delay in response has something to do with the candidate too, how much vulnerable they are for the job. Personally I discuss the expectations for the interview process beforehand which is super helpful since I almost always get the feedback the next day irrespective of whether its an offer or rejection.

On the flip side there should be another discussion on how engineers get the jobs. I am sure those stories would be interesting too. It is not about the technical competency for majority of the times. Interviewing is an art and the candidates who are able to make the interviewers feel good about themselves have much more chances of offers.