<rant> Was more trying to prove a point that such titles are pretty much useless, and that someone's skill, like Mini said, should be checked by the actual quality stuff they deliver and not bind it to titles which are (often) given depending on age. Though be noted that where I work I work with a certain country and their culture (to at least respect that, I'll leave out the name) that's basically the biggest form of "fake it till you make it". I've worked with hundreds of people from that country and culture. They're all senior (seriously, hundreds, hundreds, and I've never seen any that wasn't a senior. It's like they roll out of school being a senior), and all of them have like 20 years of experience in <insert required job position here>. An example, someone specifically stated on his resume that he had years of experience in Springboot, yet he couldn't setup a Spring project by myself. Other people with similar resumes took down firewalls, causing massive (seriously, *massive*) security problems, others seems to like the idea of visualizing and storing passwords in a back office plain text because it's "more user friendly". Meanwhile there's me, the junior developer who has to tell those seniors how to do their job. Would prefer it if everyone (in the same position) just had the "software engineer" title. Like Mini said, there are people who just stop caring and don't have any passion anymore. In this certain culture I work with, that is massively the case. You get the job done, it has to work, no matter what and how, and that's a job well done. Nobody cares how it's implemented, how many employees had to fix it, how much of a hassle it is to maintain, how much it costed, etc. All that matters is that it's there and "it works". The customer is king without limitation. You have a company that just hosts some wordpress sites and does a bit of custom development? Yeah if SpaceX came to them asking for a new sub orbital launch calculation system, they'd take the job. It also doesn't help that certain culture's are massively support their anarchy of these ranks. Remember that password thing I mentioned earlier? I had a serious discussion for two whole weeks, almost fights, with this certain colleague on why he has to follow the (internally required!) security standards and just protect the password like a normal person. Problem is he was he was the senior and I was the junior (sane team lead was on vacation), and in a highly anarchial culture, you listen to what the person above you says (in this case I was below, since I'm a junior). Just try to imagine how insanely frustrating it is to work like that. That's why I'm not a fan of those titles. Just treat everyone equally. We're all in the same position, doing the same jobs. Why different titles? It has no benefits. Also, they wouldn't give me a medior title last year because I was too young. Yet, I'm praised by the entire company half of the time. It's unfair and it's ridiculous. So, again, I see no benefits to those titles. By all means this isn't the case for everyone and every company, just an extreme example of my case where it actually gives the exact opposite effect of what it's intended to do. Considering we have on a platform with plenty of young, starting, inexperienced developers, I fear the same here. </rant> Quite off topic but the same applies to what OP is suggesting. I see no added value, only lost.