If you want to improve your professional standing, by all means, make a skills inventory and try to achieve those skills. Many of these skills might be in common with other "senior" people you know. Take some from your organization's leveling doc. But remain aware that there is nothing that "separates" juniors from seniors, that there is no threshold you cross, and that a good team is made up of a diversity of skills that complement each other, not just a bunch of people with maxed out 10X stats
The negative outcomes of a static senior/junior distinction mindset include:
- complacency once you've achieved an arbitrary title
- failure to identify specific skills needed to complete specific projects
- treating other engineers as homogenous and fungible based on level
- not listening to people lower-level than you are because you're now Senior-er than them
- failing to provided needed pushback on people higher-level than you are even when you have specific knowledge that they don't
If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/glyph/statuses/116240345723477662 on your instance and quote it. (Note that quoting is not supported in Mastodon.)