In my opinion, the number of years experience in a programming language or technology isn't what makes someone a senior level developer. It's entirely possible for a developer to have 1 year of experience 10 times over, so years of experience is a garbage metric. I actually consider the title of senior to be absolutely dependent on junior level employees being present. If a senior developer isn't mentoring and growing a junior developer's skills then they aren't a senior level developer.
Michael MacTaggert is a software developer looking for work, host of a law review podcast called Amicus Lectio, and a moderator of Programming Discussions (invite.progdisc.club). Follow me on Twitter!
I see this all the time. I can’t tell you how many interviews I have done with a senior person with 10 plus years does not have the competence and experience to do a junior level develops task on my teams.
It comes down to experience.
This is the same reason I have junior developers do code reviews, knowledge shares, and in short treat them like any other developer. As their experience grows, so does there responsibilities.
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.
In my opinion, the number of years experience in a programming language or technology isn't what makes someone a senior level developer. It's entirely possible for a developer to have 1 year of experience 10 times over, so years of experience is a garbage metric. I actually consider the title of senior to be absolutely dependent on junior level employees being present. If a senior developer isn't mentoring and growing a junior developer's skills then they aren't a senior level developer.
Absolutely agree with this.
Couldn't agree more.
+1 Absolutely.
I see this all the time. I can’t tell you how many interviews I have done with a senior person with 10 plus years does not have the competence and experience to do a junior level develops task on my teams.
It comes down to experience.
This is the same reason I have junior developers do code reviews, knowledge shares, and in short treat them like any other developer. As their experience grows, so does there responsibilities.