Ageism Haunts Some Tech Workers in the Race to Get Hired

Age discrimination in tech hiring is widely seen as an “open secret,” with many engineers reporting that opportunities dry up sharply in their 40s and 50s despite decades of experience. Commenters describe structural factors such as “up-or-out” promotion tracks, preference for cheaper or younger hires, and interview processes that favor trendy stacks or recent grads while sidelining generalist skills and long-term track records. Some see consulting, enterprise software, or strong professional networks as partial workarounds, but many argue that both older and younger workers face age-based barriers that waste talent and undermine teams.

Prevalence and Forms of Ageism

  • Many describe ageism as an “open secret”: harder for 40–50+ developers to get hired or even get callbacks.
  • Reported signals: recruiters hanging up after inferring age, being told to “ask for less” due to age, being deemed “overexperienced,” or told teams wouldn’t be “comfortable” with someone so senior.
  • Some see structural ageism via “up-or-out” policies and limited promotion slots; older ICs get pushed out when they plateau at mid/senior levels.
  • Others note that some orgs (e.g., certain big companies, “boring” enterprise/defense, academia) still value greybeards and retain them long term.

Career Strategies for Older Engineers

  • Strong support for moving into consulting/contracting or “lifestyle” businesses as age increases; perceived less discrimination, more control.
  • Getting first contracts is viewed as hard: typically requires prior connections, client-facing roles (sales engineer, professional services), and some luck.
  • Some recommend shifting into stable enterprise software, aerospace/embedded, or maintaining legacy/low-churn stacks (C/C++/embedded).

Skills, Stereotypes, and Interview Dynamics

  • One camp argues many older candidates are rejected because they’ve let skills atrophy, don’t keep an eye on new paradigms/fields, or come across as defensive/jerkish.
  • Others counter that fundamentals transfer, fads are often superficial, and expectations to chase every trend are unreasonable and ageist.
  • Frustration that interviews overemphasize narrow, current stacks, modern CS trivia, transcripts, and “culture fit,” undervaluing broad shipping experience and adaptability.

Younger and Junior Engineers’ Perspective

  • Juniors report the opposite problem: roles demanding 5+ years experience, few true entry-level positions, and market saturation/layoffs.
  • Some younger posters also feel ageism against the young (dismissed as inexperienced or unserious), though others push back that software has historically favored youth.

AI and Career Structure

  • One view: AI will let juniors level up faster and reduce demand for seniors and/or juniors.
  • Skeptical view: AI hallucinates, requires domain expertise to use safely, and may mostly diminish the value of juniors while making seniors more productive.

Networking and Resilience

  • Several emphasize that long careers should build networks that bypass biased recruiters; referrals from ex-colleagues and managers often trump age filters.
  • Personal fit, attitude, and willingness to handle “boring,” business-critical work are repeatedly cited as protective factors at any age.