Earlier quoted context omitted.
I'm a software engineer in my 40's. I also worry about ageism. I don't want to victim blame. There is probably discrimination. But I think the older developers have some responsibility in defeating ageism. I know a few SWEs who are older than me. They are already feeling the burnout of learning the new languages, frameworks, technologies every 3-4 years. Some of them are set in their ways thinking, "why would you nee…
If an engineer with 20 years of experience is intimidated by a new grad then that’s not ageism, and not what this thread is about. If a new grad performs better then there is literally no point in hiring that engineer. They don’t bring anything to the table and there is no room for growth. If you’re in your 50’s then ideally you’d be at least a principal engineer at a big tech company by then.
But there's an engineer in his 50's, who worked in his company for many years. He had intimate knowledge of its systems and domain. But his company got bought out, and the new owners decided they don't need that group anymore and lays off the entire group. Suddenly, his domain expertise is near-useless unless he can find another, similar position.
He interviews for other positions, but he is hit with questions he's not familiar with. He drones on about his old systems/architect like an old fogey who not up to date with the new, shiny stuff. He tries to study the new stuff, but he's tired, overwhelmed, burnt out, etc. His interviewers realizes he has a lot of experience and probably highly skilled, but his skills and experience aren't relevant enough to what their company is doing. They offer to hire him at a junior rate, or not hire him at all. Is this ageism, or is he not good enough?