I was watching a YouTube video about Job Titles in Software Engineering and there was a comment:
“labels like senior, medior or junior are illusions companies make to pay you less… we can’t put labels on people – everyone is different. This approach also supports imposter syndrome”
The comment got the following response:
“This is certainly a valid opinion, but it doesn’t change the fact that putting these labels on developers is a standard practice in the industry. And if getting a different label means having more opportunities, more money, and arguably more fun, shouldn’t we discuss how to get there?”
This response is definitely correct. If it is standard practice, then it’s beneficial to follow. If you are advertising a job and just write “Developer”, Seniors and above may overlook this advert because they may interpret it as below them.
As for the original comment, I would have thought the opposite is true. If you have the same title, it is harder to justify higher pay. If you have a different title, it is much easier to justify higher pay and you will also obtain higher rises as you jump from one role band to the next.
As for imposter syndrome, having the same title as someone you perceive to be much better can easily dent your confidence. If they have a higher title, then it’s easier to aspire to be the same rank as them; and you will feel confident with your own title.
I definitely think a hierarchy makes sense.