Cracking the Coding Interview Tutorial

Re:Cracking the Coding Interview Tutorial by dragonwriter on Tuesday September 27, 2016 @04:39PM (#12592969)

> Dismissing a company because one engineer there is bad at interviewing seems potentially short-sighted.

I keep hearing about a shortage of quality talent in the industry. Given that, I would expect employers to pay particular attention to putting their best foot forward in interviews -- since interviews work in both directions.

One that fails to do so -- or whose best foot is off-putting -- is revealing that their attitude toward potential hires and/or their ability to offer a good working environment is poor.

People talk about how a bad hire is a significant cost for employers, but taking a bad job can be a much bigger cost for the employee than a single bad hire is for an employer, and quite worth avoiding.

[ Parent | on HN ]

Re:Cracking the Coding Interview Tutorial by wolfgke on Tuesday September 27, 2016 @04:49PM (#12593061)

> Given that, I would expect employers to pay particular attention to putting their best foot forward in interviews

"Best" (in doing interviews) is not a criterion that lies on an ordinal scale, but is a multicriterial property.

[ Parent | on HN ]

Re:Cracking the Coding Interview Tutorial by wtracy on Tuesday September 27, 2016 @05:25PM (#12593368)

If the interviewer is just another rank-and-file engineer rather than a manager, he/she may not be motivated to see someone get hired.

[ Parent | on HN ]