|
|
|
|
|
by tfp137
1512 days ago
|
|
The dual-ladder system exists to fix something that is broken but ends up breaking it more. In essence, there's the E9/O1 problem. An elite engineer with 25 years of experience simply knows more than an entry-level manager. Organizations try to solve this by dual-laddering and saying that there are "Director-equivalent" engineers (e.g. Staff or Principal) and so on, to rectify the obvious injustice of a scenario where a fresh MBA is seen to outrank the best engineers because he manages a team and they don't. The problem is that this dual-laddering makes it worse, because it's so much harder to move up the engineering ladder. If you're a Software Manager I at Google, you have to shit five or six different beds not to make Director within ~6 years and VP within ~12. On the other hand, making Principal+ Engineer is quite difficult, especially if you're not in MTV. So it perpetuates a false equivalency in which the managerial and product folk are gods (because of their swift, easy promotions) while most of the engineers are leftovers. |
|
The parity between the two ladders is something of a myth. At most companies, you can see that clearly if you count heads.
A director might oversee 150 to 250 people. There will likely be five second level managers reporting to the director, and maybe twenty first level managers reporting to those second level managers. So 30 manager level people.
And there will be maybe four or five Staff and one Principal engineer in the same organization. Sometimes even fewer.
So the parity really isn't there.