I'm not saying the kind of ageism thats being discussed here doesn't exist - the "brogrammer", "culture fit" kind of discrimination. But I think its probably blown out of proportion. Especially for non-bay area companies, it seems like whenever somebody talks about "tech companies" they are referring to a very specific kind of tech company that is really only a relatively small portion of the industry.
They don't understand that after 3-5 years the diminishing returns flatten
This sounds about correct for a single role. A good senior person will have at least a few different roles under their belt too, each one of those takes another 3-5 years to flatten out, and usually at least a couple tech stacks they've been deeply in.Having multiple repeats of the same year's experience never helps anyone, whether it's 2 years or 20. But 10-15 years of good experience puts you far ahead of 5.
The old joke about this had to do with learning to differentiate between 10 years experience, and the same year of experience, 10 times.
I don’t think you really start becoming an engineer until you’ve already got coding down, and then you start having to go onto other things...
If someone has got 30 years of experience, employers/recruiters think it requires at least senior or manager position, while entry/mid level position appears "unsuitable".
They don't understand that after 3-5 years the diminishing returns flatten the output almost completely and the only thing that years of experience can tell is the arithmetic difference between current year and the year of graduation.
The matters are surely made worse by the current FAANG tendency to ignore whether the experience is relevant. If someone has never wrote a line of Java before, a junior position with quick promotion is the most fair and logical choice. But if their resume shows 7+ years of any coding experience at all it wouldn't even pop up in recruiter's search because of how they set up their filters for junior positions.