Earlier quoted context omitted.
I've yet to see anything better than years-of-experience (or years-in-company). I've worked in both FAANG and startups plenty, and personally I've seen worse outcomes from "impact-driven" OKRs, nepotism, team-surfing, than from coasting. Coasting can be fixed by firing or layoffs (which I consider a healthy lifecycle for any company). "Coasters" at least know that what they do today they might have to support for N y…
Recently I have been musing about a SlateStarCodex-ish "compensation systems very different from ours." One is Oxide [0], which has uniform compensation across the board, explicitly with reference to this problem about how performance processes influence work and culture. Another might be to take LeetCode-style interviews more seriously. We have already concluded that the most important criteria for whether we want t…
The leetcode stuff doesn't necessarily correlate to actual productive capacity. Good teams tend to be a mix of complementary talents, and if you put a group of algo hackers together you'll get a lot of algo hacking. You won't necessarily get a lot of maintenance or debugging.
All of which highlights that the industry has no clue how to quantify talent either during hiring or after. And even less clue how to quantify the business value of talent. It has even less clue how to quantify needed talent - in the sense of creating teams with a productive mix of interlocking skills.
Abstract discussions about comp are meaningless from a business POV without that information.
This applies particularly to management. Some managers are clearly better than others, but in spite of all of the books, lectures, and general opportunism around management theory, many corps struggle with creating a sane productive culture.