Things I Learned from a Job Hunt for a Senior Engineering Role

Re:Things I Learned from a Job Hunt for a Senior Engineering... by tedsanders on Tuesday April 24, 2018 @03:27PM (#16915761)

I love this idea. Testing how well someone can learn new skills can be just as important as the skills they've already learned. However, the problem is that as soon as it becomes known that Google is giving tests in Fortran 1988, applicants will study Fotran 1988 and thereby reduce the efficacy of the test. It will also have the sad side effect of incentivizing people to waste time studying Fortran 1988 rather than building skills useful to their job. It seems to be a good interview needs to satisfy the following properties:

* Predictive of job performance

* Either (1) difficult to optimize against or (2) easy to optimize against but in a way that doesn't reduce predictive value

* Low cost to give

* Low cost to take

[ Parent | on HN ]

Re:Things I Learned from a Job Hunt for a Senior Engineering... by khedoros1 on Tuesday April 24, 2018 @04:44PM (#16916391)

> However, the problem is that as soon as it becomes known that Google is giving tests in Fortran 1988, applicants will study Fotran 1988 and thereby reduce the efficacy of the test.

How about "Google is giving tests in these 25 languages"? They could even choose languages that are purposefully dissimilar from any language that you've claimed familiarity with.

[ Parent | on HN ]

Re:Things I Learned from a Job Hunt for a Senior Engineering... by ljw1001 on Tuesday April 24, 2018 @06:06PM (#16917080)

Umm. Not if they only stay 2 years at your company. I think that's about average outside of ones with golden handcuffs.

[ Parent | on HN ]