Earlier quoted context omitted.
> whereas everyone else would call that person [with 5 years experience] a junior engineer I’ve met people with 3 years experience who I’d consider more senior than myself (8 years). Some folks just learn really fast and/or don’t do much else other than work. Not sure time is relevant to your skills or title after about 2-3 years.
It's such an old-fashioned way to look at skills and experience. Tbh there should be real ways to measure all this but there aren't. If you can code by your own without handholding, are you a junior at that point anyways?
Having worked in multiple fields throughout my life, I deeply miss the presence of truly experienced coworkers.
For example one of the lessons of experience is that skill in the immediate task at hand is only a part of the overall engineering skillset. Experienced professionals (in any field) can often solve problems better with a tool they are unfamiliar with than less experienced professionals can in their area of expertise.
One trait of experienced devs I've seen, that I've not seen in even the sharpest but less experienced ones, is the ability to see problems that will arise down the road from miles away.
Likewise I also rarely see less experienced devs, no matter how smart and talented, see solutions outside of the main path massively reduce the complexity of the original problem. I fondly recall working in research orgs when I was much more junior, and asking a 30+ year industry vet how to solve a tricky problem only for them to, time and time again, that the best solution was to avoid the problem.