Re:How to conduct a good programming interview
by nolemurs on Sunday September 10, 2017 @10:12PM
(#15215430)
> The desire for a 'good candidate' and the paranoia about making a mistake is sounding increasingly utopian.
I don't know where you're getting your 'perfect hire narrative' idea from; this is simple cost/benefit analysis. If making a bad hire is a lot more expensive than failing to make a good hire (and I'm pretty sure it is by a factor of at least several times - failing to make a good hire is really cheap), then you choose to make the cheap mistake of not hiring instead of the expensive mistake.
This is about as far from utopianism or looking for the 'perfect hire' as you can get. It's all about finding enough 'good enough' hires, while avoiding expensive mistakes.
Re:How to conduct a good programming interview
by Apocryphon on Monday September 11, 2017 @01:57AM
(#15216290)
What makes a bad hire? Couldn't a 60-70% hire be trained up, rather than expecting all of the candidates to be 90%?
A bad hire is not the end of the world, and is easily corrected and one can't help feeling there is some magnification going on somewhere about hiring mistakes. There is near constant evaluation and feedback loops in most organizations. A 'bad hire' simply won't survive this.
No ones hires a person not suited to the job in terms of technical requirements, that's a given, but there are other things at play to make the final decision, that are less easily obvious in the interview process so mistakes will be made. Better to make them and move on rather than manufacture this increasing hysterical narrative about the 'perfect hire'.