3 ms·

Maybe, maybe not. I mean, titles don't really mean anything to developers. It's not like in the army where everyone knows the difference between a colonel and

• jabradoodle 3y ago
  You could, but you would implicitly give them titles and have different expectations. No one is expecting a junior to define the technical roadmap for the next 6 months and coordinate it's implementation across 5 teams* and be the final judge on disagreements. Edit: typo
• viraptor 3y ago
  > I mean, titles don't really mean anything to developers. To the developers themselves? Yeah, it does to many. To the company in general - there's a reason level descriptions exist. They define expectations for a given person. Let's say you create a new team for project X: you want someone who can plan the project out. Are you going to give that to any "developer" who all exist at the same level? If no, then you have different levels, you're just pretending they don't exist. It also makes things more clear for the pay. Let's say you get some good mid level dev who gets bumped many times for being really good. If they're just doing well at that level but not advancing, are you going to pay them more than senior devs with more responsibility at some point? Is that a wise decision?