Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think its potentially bad the common thinking I've seen where an interviewer ( and I've fallen into this trap ) thinks "whoa! X years of development and they can't do that! shakes head slowly". It's more a failure of the interviewer to find out what the X years of experience entailed. They could be insanely good at something really useful and just haven't coded many things like your random coding problem.


At a technical but non programming job someone once told me "Man he doesn't know what X is!"

My response, "The only reason I know that is because of that bug of ours that keeps coming up..."

Some things just happen more some places and other things don't.


It can also just be nerves. It sucks, but it happens, and your brain just freezes up and kicks itself later in the evening for looking so stupid.

Besides general strategies of trying to lower the adversarial atmosphere I think the only full solution to this problem is to be open for them re-applying after some number of months. That at least codifies a second (or more) chance for candidates who really want to work for your company specifically.


Agreed! Its super important to make sure the job, job description, candidates, and interview questions are aligned.


it really depends on the that although I get the intention that you are trying to convey.

It's also worth bearing in mind the old refrain about X*Y years of experience vs X years of experience repeated Y times.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: