News for hackers. Stuff that matters.

A comment on Cracking the Coding Interview Tutorial. Parent comment

Re:Cracking the Coding Interview Tutorial by vonmoltke on Tuesday September 27, 2016 @04:07PM (#12592668)
> This relies on being able to accurately identify poor performing engineers, which is very tough at a big company.

"Very tough"? The only big company I ever worked at was a more traditional engineering company, but identifying the poor performers was easy. The problem was the politically-savvy poor performers who used their savvy to shield themselves.

[ Parent | on HN ]
Re:Cracking the Coding Interview Tutorial by ng12 on Tuesday September 27, 2016 @04:08PM (#12592677)
Fair enough -- but the bullshitters are generally pretty politically savvy :)
[ Parent | on HN ]
Re:Cracking the Coding Interview Tutorial by wolfgke on Tuesday September 27, 2016 @04:43PM (#12593005)
Thus put them into a position where political savviness will be of no use. :-)
[ Parent | on HN ]
Re:Cracking the Coding Interview Tutorial by azraomega on Tuesday September 27, 2016 @05:33PM (#12593423)
If the person who has the power to do that knows it, might as well fire them... why even bother? The person is politically-savvy generally savvy enough to smell it ahead and get promoted else where...
[ Parent | on HN ]
Re:Cracking the Coding Interview Tutorial by wolfgke on Tuesday September 27, 2016 @05:49PM (#12593529)
Because at the moment we are talking about, we yet don't know whether the new hire is a good programmer or not (he just passed the interview). Thus my point is to put new hires into positions where political savviness will be of no use until you are sure that he is indeed a good programmer, so that they don't have any option to fake anything by political means.
[ Parent | on HN ]
Re:Cracking the Coding Interview Tutorial by mattnewton on Tuesday September 27, 2016 @06:15PM (#12593680)
I do - The not to be hired pile of resumes.
[ Parent | on HN ]