3 ms·
> In a large organisation like Microsoft's the skill of the engineers and the ratings should follow a normal distribution. My understanding is that stack ranki
by vwinsyee 13y ago
> In a large organisation like Microsoft's the skill of the engineers and the ratings should follow a normal distribution.
My understanding is that stack ranking is effective when first implemented. Subsequent implementations are progressively less effective and eventually become toxic if done too frequently. This is because at the beginning, the distribution of skill in the company's population of engineers does mirror the distribution in the overall, global population of engineers. So the initial stack rank eliminates the bottom, say 10%, performing engineers. The problem is when this happens again the following year, which seems to be what Microsoft has been doing. Barring a horrible incoming recruiting class, the company's distribution has already been shifting to the right. So each yearly cut is cutting out increasingly better engineers.
- marcosdumay 13y agoWell, by that rationale, the worst your hiring process, the more you gain by stack ranking once. But, even if you hiring people by tossing coins, if you don't have huge teams the results won't be fair. Yet, just defining a minimum performance and firing the people that don't reach it outperforms that first application of stack ranking. And you can apply that filter as many times you want, with no loss of quality.
- craigyk 13y agoThat's ignoring the actual "accuracy" of most employee "ranking" algorithms. And continual, though diminishing improvements is only true if your method of ranking employees is significantly more accurate on existing employees than for job candidates.