This is not necessarily true in practical terms when it comes to hiring or promoting. Often a senior dev becomes a senior because of having an advanced skillset, despite years on the job. Similarily, often developers who have been on the job for many years aren’t ready for senior because of their lack or soft and hard skills.
Maybe you could enlighten the rest of us then. According to your favorite definition, what does senior mean, what does seniority mean, and what's a term for someone who knows what they're doing?
Time is required to be a senior engineer, but time does not _make_ you a senior engineer.
You need time to accumulate experience. You need experience, time in the proverbial trenches, to be a senior engineer.
You need to be doing different things too, not just implementing the same cookie cutter code repeatedly. If you are doing that, and havent automated it, you are not a senior engineer.
There's what "senior"-level developers say about themselves, and there's what's actually generally true about them. The two notions are, of course, not the same.
But as of now, it's senior engineers who really know what they 're doing who can spot the errors in AI code.