The Disappearing Gray Hair of Silicon Valley
Visit a Silicon Valley semiconductor company in the 1990s, and there was nothing unusual about meeting engineers in their 50s. They were the ones spreading thick circuit diagrams across conference tables, debating designs with younger colleagues. When trouble erupted on the production line, they would study the problem for a while before saying, “I’ve seen something like this before,” and working their way toward a solution. Their gray hair was a mark of experience.

Silicon Valley’s Strange Way of Counting Age
Walk into an AI startup or software company today, however, and a question sometimes comes to mind: Where have all those engineers in their 50s gone?
Silicon Valley seems to have its own peculiar way of counting age.
Across the American workforce, people in their 50s are hardly a rarity. According to the U.S. Bureau of Labor Statistics, the U.S. labor force in 2025 included approximately 32.3 million people ages 45 to 54 and another 26.6 million ages 55 to 64.
But step inside the technology industry, and the atmosphere changes.
An unspoken equation has long shaped the Valley: youth suggests new technology; age suggests old technology. A developer in their 20s talking about a new programming language is seen as innovative. A 55-year-old engineer discussing three decades of experience may find that someone attaches a different word to the conversation: “legacy.”
But should people really be treated like software—retired simply because their version is getting old?
Losing Your Job at 50 Is Different From Losing It at 30
Layoffs are a familiar feature of the technology industry. The trouble is that the same layoff can have very different consequences depending on a worker’s age.
One set of 2025 figures put the average duration of unemployment at 22.7 weeks for people ages 25 to 34, compared with 27 weeks for those ages 45 to 54 and 26.7 weeks for those ages 55 to 64. For workers 65 and older, it stretched to 31.4 weeks.
For engineers in their 50s, though, finding another job is only part of the challenge. The harder question is whether they can return at anything close to their previous title and salary.
An engineer with 20 or 30 years of experience will often command substantial compensation. Add health insurance, equity awards, and other benefits, and the total becomes a significant expense.
Somewhere in a restructuring spreadsheet, “30 years of experience” begins to appear as “high labor costs.”
Then there are the less comfortable considerations. A company may hesitate to place an engineer in their 50s under a manager in their 30s. Someone asks whether the candidate will adapt to the company’s culture. Rarely does anyone say, “You’re too old.” Instead, the language sounds like this:
“Not a culture fit.”
“Overqualified.”
“Too senior.”
These phrases can become Silicon Valley’s coded language for age.

The Controversy at IBM
Few companies have illustrated this issue as starkly as IBM.
In its investigation of the company’s sweeping workforce reductions, ProPublica estimated that IBM had eliminated the jobs of more than 20,000 U.S. employees ages 40 and older over five years. In some of the layoff records examined, 70 percent of workers whose ages could be established were 50 or older.
IBM denied engaging in age discrimination.
Google, too, has faced questions about age. Applicants ages 40 and older brought a class-action lawsuit alleging discrimination in hiring. While denying the allegations, Google agreed to an $11 million settlement in 2019.
The point is larger than whether one particular company behaved badly.
Why does age remain such a persistent issue in an industry that considers itself the most forward-looking in the world?
They Have Moved Beyond Our View
So where did these engineers go?
Here is where the story takes an interesting turn. Engineers in their 50s have not disappeared. Many have simply moved beyond the places where we tend to look.
Some replace “Senior Engineer” on their business cards with “Independent Consultant.” Others become chief technology officers or technical advisers at smaller startups. Some move into industries where years of practical experience carry considerable weight: semiconductor equipment, automotive technology, medical devices, aerospace and defense, factory automation, and data centers.
Others move from engineering into product management, technical sales, or business development.
Those with enough financial security may retire early.
And some start companies of their own.
This brings us to one of Silicon Valley’s most revealing paradoxes.
When we picture a startup founder, we often imagine a brilliant twenty-something in a hoodie. Yet research using U.S. Census Bureau data found that the average age at founding among the fastest-growing 0.1 percent of new businesses was 45.
Successful entrepreneurship was never the exclusive territory of the young.
An engineer in their 50s who has spent decades watching products succeed and fail—and learning what customers actually want—may be particularly well prepared to build a company.
Then Came AI
Now the question has become more complicated.
As generative AI writes code, runs tests, and produces documentation, companies are asking once again: How many engineers will we need?
For engineers in their 50s, AI could bring both a threat and an opportunity.
If the ability to type out new code quickly becomes less valuable, other abilities may become more important: deciding what should be built, understanding an entire system, and recognizing where failure is likely to occur.
You can ask AI to write code.
Whether it can readily replace the judgment of an engineer who has spent 25 years building products—and knows where a particular approach may cause trouble six months down the road—is still an open question.
Experience Is a Technical Skill, Too
Silicon Valley has always loved the new: new technologies, new companies, new ideas, and new people. That appetite helped make it the world’s leading center of innovation.
But the ability to create something new is not the same thing as being young.
Engineers in their 20s can bring speed and fresh instincts. Those in their 30s develop the ability to turn ideas into execution. By their 40s, many have learned to see technology and organizations together.
And engineers in their 50s often carry something that is difficult to find through a search engine: the memory of failure.
They remember why a technology failed, why customers rejected a product, and how a single decision produced consequences years later. These are lessons learned firsthand, sometimes at considerable cost.
That, too, is technical