[000ooo000]

These days I tend to think that anyone hung up on being a "senior" doesn't qualify as a senior, because they haven't been around long enough to know it usually means SFA. Work a few places with a variety of folk, some "senior", watch who gets promoted to "senior" and when, and you'll notice it's pretty arbitrary and often just a lever in role negotiation/retention; you want your resume to show progress, and if you aren't savvy, it can cost them nothing to throw you that bone.

As for the guy in the article: think about any junior you've ever worked with and the kind of work they're assigned. It's usually not high-impact, deep/broad, technical stuff. Hell, even non-juniors need a good few months to come up to speed in a codebase, not to mention some domains require a good bit of seat time to hit your stride as a dev. So, under 12 months of that basic junior-style work and then you're a "senior"? Not convinced