|
|
|
|
|
by lliamander
2255 days ago
|
|
> I used to think hard work leads to promotion. This is because I didn't understand why different positions exist outside of a title change. Now I see things a bit differently. If an individual on my team is working hard, I'm going to keep them where they are because they're getting the job done. Rather, I'm looking to elevate my 10x engineer - not the one that's the doing their job well but the one thats mentoring those around them to do their job well too. An excellent point. This misconception that hard work leads to promotion is widespread, and management doesn't often do enough to dispel it (if they are even aware of it themselves). I think an important step here is to identify the concrete behaviors and competencies needed to advance. In the words of Randall Koutnik: "What does it take to succeed at [your] company beyond 'hard work'?"[0]. [0]https://rkoutnik.com/articles/Questions-to-ask-your-intervie... |
|
You might be a Senior Software Engineer at one place but called a Staff engineer at another place, but they're broadly comparable, and the seniority criteria show a very clear progression: the more senior you get the more influence you are showing across the organisation, whether that means managing larger projects, mentoring other staff, consulting with other teams on best known practices, or influencing other parts of the company inter-discplinary projects.
Almost every large organisation will have a neat table telling you exactly what attributes you need to show. They all show that progression - more influence on the organisation as a whole.
And yet every single review cycle there's always a portion of engineers who think they deserve a promotion because their personal work was high quality. It's like they haven't read the job spec of the job they're applying for. It's amazing.