When the supply of scientists far exceeds the demand, there must be a way to decide who gets jobs and funding. Some people favor objective measurements, because they are less prone to corruption and nepotism than subjective ones. But when you have objective measurements, people will try to game them, and some will use dishonest means.
- You need to be available for contracting work, but many people prefer to go from one full-time job to another. Or they might not want to leave their current job, unless they get a much better offer.
- You need to be in the right location. Relocating without a job offer is risky.
- Especially strong candidates are likely to get many offers when they go looking, which is a good position to be in for salary negotiations. But work-as-interview arrangements make it hard to interview with more than one company at a time.
- Anything resembling visa support is probably off the table.
This plus a very easy coding question (think fizzbuzz) works really well at a small enough company that you can ensure that all interviewers:
1. Are far enough above the hiring bar that they can comfortably tell when other people are (people near the bar have a harder time distinguishing whether someone is a bit above or below the bar)
2. Are invested enough in the company to want to do a good job interviewing
3. Are thoughtful enough to gauge the competencies the company needs for the role. Those needs are not universal, I know developers who thrive in super technical no-nonsense roles who flounder in product-y work.
If a company is very large or growing rapidly it is nearly impossible to guarantee these things. My experience is that companies that don't adopt something like the industry norms lose control of their hiring bar. In some cases this is fine (sometimes you need quantity, not quality) but if the business relied on that high technical bar there's generally a cascading effect of initiatives failing, good engineers leaving, and more initiatives failing because of it. I've seen this tank a few startups in the 50-100 engineer rage.
Absolute fav :)
Best guesses I've got for how to combat the situation: - Have a diversity of metrics that are somewhat independent, somewhat anti-correlated (if I'm using the right words) - Have non-measurable goals that you refer back to
Anyone else got ideas for hedging against the failure mode of Goodhart's Law? :)
I have seen this in a company where they would change employee objectives every year, and also promote and demote people into unexpected new roles. This seemed to result in everyone understanding that next year things can be very different, and does not give people enough time to corrupt a metric. So everyone needs to build good working relations with superiors and subordinates, and not only try to meet objectives but also do well for the company in general, because next year roles can be reversed.
This system is tiring for everyone though...