|
|
|
|
|
by htormey
1907 days ago
|
|
Making promotion the only way to get a bump in salary can cause all sorts of problem when the responsibilities and requirements of the role change at the next level. As an example, at big companies staff level engineer is more oriented around writing/reviewing and building consensus about technologies. This is a very different role to the level below and someone who is great at that role may not be great as a staff level engineer. They do however deliver a lot of value to the company. Having a way to reward someone who’s doing an amazing job at their current level helps avoid this situation. I.e inventing projects to justify promotion to staff level engineer. In most companies, the level below staff is a terminal position. I.e their isn’t necessarily an expectation that you need to get promoted to the next level. I think Facebook got the formula right with its performance based bonus that allows employees who go above and beyond to be rewarded. This is a similar situation to when companies had career tracks that forced really good engineers to get promoted into management in order to get more comp. Just because you are an amazing engineer doesn’t mean you would be a good people manager. |
|
At least half of my coworkers could move over to a similar position at a FAANG with no difficulty and make over double what they are now, but I have no doubt in my mind that if any of them did that, it would not be for compensation.