TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

What makes you hire or no hire a candidate for a software engineering position?

1 pointsby wbsunabout 7 years ago
Just out of curiosity, or maybe a valid question that a lot of people might be interested? So what makes you decide to hire or no hire for a engineering position?<p>I will just tell my personal experience both as a interviewee and a interviewer:<p>* As a interviewee: Since you probably would never get real feedback from interviewers (due to some policies or whatever), my feel of the interviews that I was rejected: 1. interviewers caught some of your coding bug, even though you fixed it; 2. you think you will discuss&#x2F;communicate with the solution that interviewer wanted, but maybe the interviewer is expecting to see without too much discussion (hints), you came up something s&#x2F;he wants or better surprise him&#x2F;her. If not, you will be probably rejected. 3. Maybe the interviewer just does not like you (chemical not right, etc). No matter how well you did, someone can always pick up something to say you&#x27;re not &quot;good&quot; enough for the position. This can be subtle, and you as interviewee, just can never know.<p>* As a interviewer: From what I recalled, I will hire the candidate if s&#x2F;he 1. Does some amount of workable coding 2. Even with some hints, the optimal solution is brought up and implemented.<p>The reasons I rejected candidates: 1. too much unnecessary talking, no real code. or cannot write any sensible code. 2. with <i>a lot</i> hints, he&#x2F;she can not write up standard algorithm routines 3. border line candidate, in the sense that there is some team member just does not like the candidate and vote for no hire and I did not champion for him&#x2F;her.<p>What are your possible reasons of hire&#x2F;no hire? or &quot;feel&quot; of being accepted&#x2F;rejected?

1 comment

daniellee85about 7 years ago
This is a very hard question actually. Interviews are pretty subjective process. It will be very hard to summarize what are the possible reasons to hire&#x2F;reject candidates.<p>Aside from answering the author&#x27;s question, I would propose the onsite in-person interview should be video recorded, conducted by one interviewer. Then later replaying in the hiring committee or what so ever, and vote for hire&#x2F;no hire. That could eliminate any discrimination&#x2F;bias&#x2F;subjective&#x2F;personal feedback from interviewer and stop interviewee from being accusing any accidents during the process.