Agreed. I dislike the terms "sr" and "jr" developer, but I think we too often call someone a senior because they know a lot of technology or they've been around for a while.
I've been thinking a lot about these terms and have been defining these roles internally as:
junior: can build relatively simple solutions, still gaining experience.
mid-level: can build complex systems, but the solution is going to be complicated.
senior: builds simple solutions to solve complicated problems.
I mentor internal devs to help shift their focus from learning more complicated technologies toward learning how to produce much cleaner and simpler solutions. This is the career path that I think helps them the most and also helps our company scale.
I've been thinking a lot about these terms and have been defining these roles internally as:
junior: can build relatively simple solutions, still gaining experience.
mid-level: can build complex systems, but the solution is going to be complicated.
senior: builds simple solutions to solve complicated problems.
I mentor internal devs to help shift their focus from learning more complicated technologies toward learning how to produce much cleaner and simpler solutions. This is the career path that I think helps them the most and also helps our company scale.