There was a broad HN discussion about this here on HN late last year [1].
And the top comment [2] is worth repeating here
Here's some of my learnings about getting promoted for those that really want to play that game:
- Only the perception of your work matters
- Attend the social events and get in good with the bosses
- The countability of your major achievements is important. Make the list long, too long to hold in the mind
- At the same time the gravitas of your best achievement is also important since that will be the soundbite that is shared about you behind your back
- Get allies who can proselytize about you behind your back
- Be the best. The difference between one and two is bigger than that between two and three, as far as promotions go
- Take credit for your work (use pronouns I and Me when talking about your work, not We) and do not allow others to take credit for your work
- If it's a teamwork situation with other people on your level, don't do most of the work, because the credit will end up being split 50/50 in the eyes of the bosses even if you did most of it
- Make a very good first impression
- Shape the narrative around the role you played in the success of the mission/team/company
- Get the bosses to make a soft public commitment regarding your competence
- Even if you have a really good boss, all of the above is still important, because they are fallible humans and aren't omniscient
- Actually do good work, it'll make the above easier
You can progress to a pretty decent level and pay as "the best programmer" up until a high senior role, which most talented folks hit after about 8 yrs of experience. After that, promotions start to depend on the extent to which you influence the direction of your group or even company, which is all about teaching and leading others.
I think of it as three stages:
* Learning: you may be good at completing well-defined work, but you generally need a mentor to guide and help you. in other words, the company at this point is investing in your growth.
* Building: you are now self-directed and able to work independently, capable of being assigned a possibly ambiguous product requirement and being able to solve it yourself.
* Leading: you are now at the point where you can be given a large, complex project with possibly ambiguous requirements and trusted to deliver. you can work with management to form a team, and can design the technical / architectural approach and break it down into smaller pieces which you can delegate to the rest of the team.
And once you hit "leading", it will grow in scope.
So that excludes about 95% of them.
If you're working at a functional organization that rewards growth, never sharing knowledge will ensure you put quite a low ceiling on your advancement.
I've written countless promotion justifications. Been on countless promotion review boards at several very successful tech companies. Being the best programmer, or what ever, is only going to get you so far. Advancement comes from teaching and leading others. You do that by sharing knowledge.