One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
My view is simple: Job titles are mostly meaningless.
What is important for you?
That someone has the title of writer, or that she write cool books?
Therefore the question is not what a senior developer is, it is what a senior developer does.
Once you know that, you can do those things long before you give yourself the title. If you feel like it obviously, no pressure. You can lead before you are officially the lead of your team. You can organize retrospective, compare alternatives, think about architecture, train your colleagues, ... long before you have the title of senior developer.
I agree with you Jean, but I commented in the article, the problem is that this causes frustration in people, imagine a Junior earning to do the work of a senior and not having the opportunity to evolve within the company, I've seen this happen, and the person left the company when he saw that there was no result.
I also believe that they are just titles, but deep down, people recognize others by titles and not by what they truly do. Thanks for the sugestion.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
The junior can start today doing the activities behind the titles, like volunteer to do a retrospective.
If the company doesn't value her, she can move to a better company later.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My view is simple: Job titles are mostly meaningless.
What is important for you?
That someone has the title of writer, or that she write cool books?
Therefore the question is not what a senior developer is, it is what a senior developer does.
Once you know that, you can do those things long before you give yourself the title. If you feel like it obviously, no pressure. You can lead before you are officially the lead of your team. You can organize retrospective, compare alternatives, think about architecture, train your colleagues, ... long before you have the title of senior developer.
Related:
What is a Senior Developer *Really*?
Marc Backes γ» Oct 15 '20 γ» 3 min read
I agree with you Jean, but I commented in the article, the problem is that this causes frustration in people, imagine a Junior earning to do the work of a senior and not having the opportunity to evolve within the company, I've seen this happen, and the person left the company when he saw that there was no result.
I also believe that they are just titles, but deep down, people recognize others by titles and not by what they truly do. Thanks for the sugestion.
The junior can start today doing the activities behind the titles, like volunteer to do a retrospective.
If the company doesn't value her, she can move to a better company later.