I'm that old, and I have an undergrad CS degree. CS degrees were already common in the early 1980s.
> 1973 Two-hundred B.S. degrees awarded
[1] https://www.cs.purdue.edu/history/table1.html
PS - Purdue is the oldest CS department in the US, though perhaps another university started an undergrad program earlier?
It was reorganized into the Department of Computer Science in 1964.
In 1965 the College of LAS undergrad degree was established.
In 1972 the undergrad degree in College of Engineering was established.
I assume within 4 school years of both they issued undergrad degrees.
The first graduate degrees were awarded in 1967.
At Nova they had the big iron too even though there were only 11 students.
There's more to the story on that one.
Nobody small could afford a mainframe.
"I have not, do you have those problems with 10k users too?"
Ironically, in the early 2000's it was the opposite. Something did change though because I've seen the problem you're talking about.
One thing could be companies, recruiters, or manager looking for CS or CE degree specifically. Someone who is 60 outdates CS and CE. I'd caveat by saying most fresh grads don't actually know how to negotiate algorithms correctly. They leetcode like everyone else before the interviewing process. As I've gotten older I've developed more holistic understandings of some data structures and algorithms, but definitely not all of them. The skill I think I became more adept at was working through the logic of them more efficiently. That's the gift repetition gives though, I suspect. All that to say, if entities are overvaluing those degrees, it's an irrelevant requirement.
Another thing could be that most jobs are phrased, "CS, CE, or equivalent experience". As someone without a degree "equivalent experience" at times boiled down to, "Have you worked at a FAANG or on FAANG level problems?" It's a circular dependency unless you spend some time in growth companies or start ups that don't have these hard requirements. Again, it's another useless requirement because you either have the math chops to solve the problems in front of you or you don't. I don't need provenance to tell me that.
All that to say, I don't even imagine how old someone is when I'm looking at a resume. Most of my judgement relies on the interviewing process and whether you can negotiate a simple algorithm and some systems design. That's as data driven as I can get it right now, although highly inefficient, but inefficiency is worth the time for quality, imo.