In Part 1 of “The Untapped Power of Veteran Engineers,” we explored the immense value that seasoned software engineers, with over 25 years of experience, bring to the table. These Veteran Software Engineers offer unmatched technical expertise, strategic insight, and mentorship that can drive innovation, minimize technical debt, and ensure long-term success. Their ability to solve complex problems efficiently, prevent technical debt, and future-proof software systems makes them indispensable, particularly in high-pressure environments. Despite these advantages, many companies fail to fully recognize their contributions, often due to outdated perceptions about age. This article highlights why veteran engineers should be celebrated as key assets to any team, advocating for their crucial role in building robust, scalable, and maintainable systems.

This article explores the challenges of age bias in the workplace, debunks common stereotypes, examines the tech industry’s youth-obsessed culture, highlights the underutilization of senior talent, and offers actionable strategies companies can adopt to reverse these trends.

Why do companies not understand the benefit? There are many reasons why companies tend to favor youth over experience. I am currently struggling with most of these issues, especially the first one. I hope this will help you in your journey as a veteran software engineer and also help companies realize they are missing out on very valuable assets.

Age Bias in Tech: The Elephant in the Server Room

Ageism remains one of the most pervasive challenges in securing or retaining a position across many industries. However, in the tech industry, it is particularly glaring. Having been in this field for decades, I knew this issue existed, but I never anticipated just how entrenched it would be as I advanced in my career. In tech, there is a tendency to favor youth over the invaluable asset of experience and the deep knowledge built over years of hard work. This bias is not just an inconvenience; it is a real barrier that dismisses the value of seasoned professionals who have seen and shaped the evolution of this industry.

For those of you unfamiliar with this term:

Ageism in the workplace refers to discrimination or prejudice against employees or job applicants based on age. It often involves stereotypes or biases that assume older or younger individuals are less capable, adaptable, or qualified, leading to unfair treatment in hiring, promotions, or day-to-day job responsibilities.

Age discrimination is not only a deeply troubling issue but also an illegal one in the United States under federal law. The Age Discrimination in Employment Act of 1967 (ADEA) explicitly prohibits employment discrimination against individuals aged 40 or older. Under this law, employers are forbidden from requesting your age on job applications—though, unfortunately, some still do. I have even encountered instances where companies ask applicants to submit a photo of an ID that includes their birthdate. In situations like this, I do not hesitate to abandon the application. It is worth noting that this protection extends beyond the U.S., with around 50 countries, including the UK, Canada, Australia, and Japan, enacting similar laws to protect older workers from discrimination.

I have heard from many engineers experiencing this issue. Most say that the company likes their resume and what they learned about the candidate, but as soon as they go in or do a virtual interview, the process abruptly stops. I know of one person whose interviewer let slip that he was “too old.” This person brought a case against the company and won, but I am sure this is rare since candidates need proof that they violated the ADEA.

Sadly, even today in the tech sector, ageism persists. Let us discuss these issues in detail.

Stereotypes

There can be many stereotypes when discussing veteran software engineers. Let us first discuss how they might be out of touch with new technologies.

They Are Out of Touch with New Technologies

In my experience, staying current with technology often comes down to the individual’s approach to learning and growth, especially when they first entered the tech industry. Throughout my career, I have encountered software engineers of all ages who struggle to keep up. In fact, if an engineer is not actively engaging with new developments, maybe they should reconsider their place in such a fast-moving field. It is why I always ask, “How do you keep up with technology?” at the end of every interview. If a candidate does not have a quick and thoughtful response, I tend not to recommend them for the next stage in the process.

That said, I partly agree with the stereotype that some older engineers resist learning new things. However, I have also seen younger engineers fall into this same trap. This is where employers need to dig deeper in interviews and ask the right questions to better assess a candidate’s commitment to staying up-to-date.

For me, staying on top of new technologies has always been a priority. The tech world evolves every single day, and to remain a relevant professional software engineer, you must continuously learn. Teaching at a university, running a user group, traveling the world sharing knowledge, writing books, maintaining dotNetTips.com, and hosting a podcast — all these activities have kept me engaged and learning. If you are not actively pursuing opportunities to stay on top of trends, I would encourage you to start now.

With all that said, my experience has also taught me the value of patience. Over the years, I have learned that not every trend is worth chasing. Some technologies come and go quickly, but the ones that last are those that are thoughtfully developed and widely adopted. This is where experience comes in. Early in my career, I was quick to jump into new trends, but now, I tend to wait and watch how things evolve before diving in.

As a Microsoft MVP, I have often seen firsthand how important it is to take a cautious approach. When Microsoft releases a new framework, I do not start writing or teaching it until I have had the chance to ask the teams at Microsoft whether they are “dogfooding” it—using it internally. If they are, then I know the framework will be supported and refined, giving it longevity. Experienced engineers know the risks of using version 1 of any technology. Patience pays off, and with time, trends will show their true value.

Recommendation for Employers:

When hiring software engineers, prioritize candidates who demonstrate a genuine commitment to lifelong learning. Ask thoughtful questions about how they stay updated with emerging technologies. Look for those who balance keeping up with trends and exercising patience—those who know when to embrace new tools and when to wait for them to mature. This balance is essential to building a sustainable, innovative development team.

They Resist Change or Aren’t “Hungry” Enough

This issue is closely related to the previous stereotype. It all comes down to how individuals keep up with technology, but it is also reflective of broader organizational behavior. Employers need to ask the right questions during interviews to understand whether candidates are truly motivated to evolve with the industry. However, this problem is not just limited to individuals; it can be a hallmark of companies as well.

I have witnessed too many organizations outright resist change—often due to fear or simply a lack of understanding. It is not uncommon to find businesses running systems that have not changed in decades. When companies take this approach, it can be nearly impossible to implement meaningful changes.

For example, in part 1 of this article, I mentioned a company that claimed they were transitioning to the cloud, but all they were doing was moving their old services into virtual machines (VMs) and calling it “cloud.” This is not the cloud! They were still operating services that were over 20 years old, with little to no updates during that time. In fact, their approach to change was to only make updates if customers specifically paid for them. As a result, their systems are in poor shape, with some services taking minutes to return results—no exaggeration. The only reason they moved to the cloud was to appease some of their customers. This approach is a surefire way to set a SaaS company up for failure.

As for individuals, if someone resists change or is not “hungry” enough to grow, I would argue that this mindset is likely ingrained and not necessarily tied to age. It is a sign of an unwillingness to adapt, learn, and improve—characteristics that are essential for success in the fast-evolving tech world. People who are not actively seeking new challenges or who are content with the status quo can become stagnant, regardless of how long they have been in the industry.

Recommendation for Employers:

In hiring and management, seek out individuals and teams that embrace change and continuously strive for improvement. Ask questions that gauge their willingness to learn, adapt, and innovate. Similarly, companies should foster a culture that values flexibility and continual growth, encouraging employees to evolve with the technology landscape. Organizations that resist change may find themselves left behind, while those that remain “hungry” for progress will thrive in an ever-evolving market.

Fear They Will Expect Too Much Pay

It is a reality that comes with experience—higher pay often accompanies greater expertise. This is not just true in tech; it is a universal principle across all industries. Why would anyone with 25+ years of experience work for entry-level wages? It is simple: experience commands value. Unfortunately, I have recently come across job postings for lead engineers, managers, and architects offering less pay than someone working in a grocery store. This trend is concerning, especially since salaries are currently trending in the wrong direction, reminiscent of what happened after the Internet Bubble burst.

What many companies seem to fear is the cost of high-quality work. There is this common misconception that “butts in seats” means faster work at the same level of quality. This idea—that more people lead to better results—is fundamentally flawed.

The concept of the “mythical man month,” introduced by Fred Brooks in 1975, emphasizes that adding more people to a project does not necessarily accelerate progress. In fact, software development does not scale linearly due to factors like:

• Communication Overhead: More developers mean more time spent coordinating efforts, which leaves less time for actual coding.
• Ramp-Up Time: New team members require time to get familiar with the project and its intricacies, slowing overall progress.
• Task Division Limits: Not all tasks can be split among multiple people, and some require a single, focused effort.

Brooks famously illustrated this by saying, “Nine women can’t make a baby in one month,” highlighting the absurdity of expecting that simply increasing the number of people on a project will result in faster or better outcomes. Many times, I have witnessed companies make the mistake of laying off their senior engineers, leaving only less experienced staff. In doing so, they lose the “brain trust,” leadership and mentorship that keep teams focused, on track, and productive. This has resulted in some companies shutting down altogether.

The reality is that experience matters. Companies need to pay for experience, and they must maintain a balance between seasoned engineers and emerging talent. The last group that should be laid off during tough times are the experienced engineers—the ones who provide stability, leadership, and mentorship to help the company navigate through challenges.

Interestingly, experienced software engineers might actually cost less than many companies assume. Often, seasoned professionals do not carry the same financial burdens as younger engineers—such as supporting children or maintaining high living expenses. In fact, many experienced engineers, like myself, may have already made adjustments in their personal lives. I recently moved to a more affordable location, which allows me to accept a lower salary compared to what I would have expected in high-cost areas like California. Companies may find that experienced engineers are more willing to adapt to market conditions, making their compensation needs more flexible than expected.

Recommendation for Employers:

When it comes to compensation, do not shortchange experience. Paying for seasoned engineers is an investment in quality, leadership, and mentorship. The experienced members of your team are invaluable assets who guide the rest of the workforce, ensuring that projects run smoothly and efficiently. As tempting as it might be to cut costs by eliminating experienced roles, remember: losing these key people can set a company back significantly, both in terms of morale and productivity. Keep the right balance of experience and emerging talent to ensure long-term success.

In summary, the stereotypes about older software engineers—such as being out of touch with technology, resistant to change, or expecting high pay—are often unfounded. Staying current is about individual commitment to learning, not age. Resistance to change is a mindset, not an age issue. While experienced engineers may command higher pay, it is an investment in quality, leadership, and mentorship. Many seasoned professionals are also more adaptable than assumed, adjusting their compensation based on personal circumstances. Employers should value experience, foster continuous learning, and balance new talent with seasoned professionals for stronger, more resilient teams.

Youth-Obsessed Culture & the Startup Myth

The tech industry often celebrates youth, hoodie culture, and the fast-paced “move fast and break things” mindset. While innovation and energy are essential, true success—especially at scale—relies heavily on experience.

Veteran engineers bring much more than just code. They’ve:

• Weathered multiple tech booms and busts.
• Scaled teams, led projects, and debugged critical systems at 3 a.m.
• Witnessed the rise and fall of every trend since Visual Basic.
• Built the foundation that many modern platforms still rely on today.

With experience comes stability, long-term thinking, and sound decision-making—qualities that are often undervalued in startup culture. Unfortunately, job descriptions using phrases like “fast-paced startup mentality,” “high energy,” or “nights and weekends required” can unintentionally alienate seasoned engineers who could be game-changers for your organization.

The reality? Companies that overlook experience often face higher turnover. Many younger engineers eventually recognize the unsustainable demands and leave for environments that value balance and growth. I have seen this pattern play out again and again—companies ignoring advice to retain talent through culture and compensation, only to later struggle with churn and missed deadlines.

Recommendation for Employers:

Employers can make a significant impact by rethinking how they approach hiring and team dynamics. Start by avoiding exclusionary language in job postings that glorifies burnout rather than promoting balance. Create specific roles for mentors—veteran engineers who can guide teams, prevent costly missteps, and accelerate the growth of junior developers. Prioritizing retention through flexibility, respect, and recognition helps keep both new and experienced talent engaged. Finally, fostering multigenerational teams brings together fresh ideas and seasoned insight, fueling long-term innovation.

Bringing experience to the table is not about being stuck in the past—it is about building a future that works.

Failure to Leverage Senior Talent Properly

Now that I am a veteran software engineer, I have noticed a recurring theme during interviews: companies often focus on whether I can crank out code as fast as someone fresh out of school. The short answer? I absolutely can—and often with higher quality, fewer bugs, and better performance. In fact, I have had younger engineers at past jobs ask me to slow down because they felt I was making them look bad.

But that is not the point.

The true value of a veteran engineer is not measured by the number of lines of code written each day. Much like a seasoned musician knows which notes not to play, experienced engineers understand which code does not need to be written. Their strength lies in architecting scalable, maintainable systems from the very beginning, identifying performance bottlenecks before they become expensive problems, and mentoring junior developers to elevate the capabilities of the entire team.

I often push back when companies try to treat me like a “code monkey.” That has never been who I am—and it is not how experienced engineers should be seen. Our most valuable contributions come through:

• Designing robust architecture.
• Performing deep, constructive code reviews.
• Leading projects and aligning teams.
• Driving long-term strategy and decision-making.
• Being the steady hand in high-pressure situations.

Yet many companies make the same costly mistakes:

• Treating senior engineers as interchangeable coders.
• Excluding them from leadership or architectural discussions.
• Failing to tap into their mentoring potential.

When this happens, it is not just the engineer who loses out—projects suffer, technical debt grows, and teams lack the direction they need.

Recommendation for Employers:

Employers should redefine what success looks like by moving beyond metrics like coding speed and instead evaluating impact, mentorship, architectural thinking, and long-term vision. Involving senior engineers early in the planning and decision-making process ensures that their insight shapes key project directions from the outset. When empowered to lead—whether by guiding projects or mentoring junior developers—experienced engineers act as force multipliers who elevate the entire team. It is also critical to value wisdom alongside youthful energy; while fast code might impress, it is smart, sustainable code that drives lasting success.

If you want your team to ship better products, faster, and with fewer fires to fight—start by properly utilizing the talent you already have.

What Companies Should Do Differently

Throughout these articles, I have outlined the importance of leveraging experience to drive long-term success. To gain a true competitive edge, companies must take deliberate steps to engage and empower veteran engineers. Here are some forward-thinking strategies:

Proactively recruit experienced engineers – Do not wait for them to apply. Instead of fearing higher salaries, consider the long-term return on investment their expertise brings. Veteran engineers often deliver higher-quality work, faster ramp-up times, and critical leadership that elevate entire teams.

Establish mentorship programs to harness institutional knowledge – I have worked at several companies where I led regular “brown bag” sessions or shared insights from my conference presentations. These informal learning opportunities not only uplift teams but also help prepare them for future tech shifts, such as cloud or AI adoption.

Encourage age-diverse teams – Just like any other form of diversity, having a wide range of ages on a team brings broader perspectives, better decision-making, and more resilient solutions.

Train hiring managers to value experience, not fear it – Many hiring managers lack formal training in effective, unbiased hiring practices. Investing in their development ensures your company makes smarter, more inclusive hiring decisions.

Rethink job descriptions and resume filters – Automated systems often unintentionally exclude highly qualified senior candidates. Take time to review your hiring tools and ensure they align with your values and business needs.

Offer part-time roles for veteran engineers – Not every expert wants a full-time role, yet they are eager to contribute. Flexible work arrangements allow companies to tap into decades of experience on-demand—an often overlooked win-win scenario.

Engage with Your Local Tech Community – One of the most effective ways to build connections and discover top talent is by actively participating in your local tech community. Consider hosting a user group at your workplace or sponsoring grassroots tech conferences in your area. If opportunities like these don’t yet exist where you live—create them. Launching a meetup or organizing a local event positions you as a leader while fostering an ecosystem of innovation and collaboration. You’ll not only meet passionate engineers but also gain the advantage of working with individuals who are committed to staying current and continually advancing their skills.

By embracing these strategies, companies can unlock a powerful, often underutilized resource—seasoned engineers who bring deep technical knowledge, mentorship capabilities, and a long-term view that helps avoid costly mistakes. When businesses stop viewing experience as a liability and start seeing it as a competitive advantage, they not only build stronger teams but also future-proof their products, culture, and success.

Final Thoughts

The stereotypes about veteran software engineers—that they are out of touch, resistant to change, or too expensive—collapse under scrutiny. Staying current is a mindset, not a birthdate. Hunger for growth is a personal trait, not something that fades with age. And compensation? It is often more flexible than companies assume, especially for engineers who have built a lifestyle around balance and long-term value rather than chasing the next highest salary.

You do not need to reinvent the wheel when you can hire someone who has already built it, shipped it, debugged it, and taught teams how to make it better. Hiring a 25-year veteran is not a luxury—it’s one of the smartest, most efficient investments a company can make. Veteran engineers shorten ramp-up time, improve team cohesion, and proactively prevent the kinds of architectural and technical disasters that can quietly kill a project.

As I emphasized in Part 1, veteran engineers do not just bring technical mastery—they future-proof your systems. I shared the story of when I joined a tech company bogged down in a three-year “lift-and-shift” cloud migration. Despite the time and cost, they had completely missed the benefits of modern cloud architecture. The root of that failure? Poor company culture and architectural decisions made decades earlier—choices that could have been avoided had the company involved experienced engineers with a mindset for continuous learning and long-term vision from the start.

I also detailed how veteran engineers naturally detect and prevent technical debt before it silently metastasizes into project-killing chaos. Debugging? We have done it so often that it becomes instinctive. I personally developed a custom logging framework at one company that my boss later called a “lifesaver” because of how fast it helped us fix critical production issues.

And beyond code, veteran engineers lead. I have mentored engineers, saved companies millions of dollars through strategic decisions, and written extensible systems that others could easily evolve years later. I have run user groups, taught at universities, lost over 140 pounds (63.5 kilograms) to maintain focus and energy, and built a life that allows me to give full energy to the teams I work with—without distraction, ego, or drama.

Veteran engineers bring calm in chaos, maturity in conflict, and mentorship in the trenches. We are not trying to dominate—we are trying to elevate everyone around us. If companies stopped seeing experience as a threat and started seeing it as a multiplier, they would discover that many of the outcomes they are striving for—innovation, efficiency, sustainability—are sitting right in front of them, waiting to be invited in.

So, if you want fewer fires to fight, faster delivery, better performance, stronger teams, and deeper insight—stop overlooking the people who paved the road on which you are walking. Invite them back to the table. Let them lead, teach, and build your future.

They are not “too old.” They are just not done yet.

The Untapped Power of Veteran Engineers: Why Companies Are Overlooking Their Most Valuable Assets – Part 3

Pick up any books by David McCarter by going to Amazon.com: http://bit.ly/RockYourCodeBooks

If you liked this article, please buy David a cup of Coffee by going here: https://www.buymeacoffee.com/dotnetdave

© The information in this article is copywritten and cannot be preproduced in any way without express permission from David McCarter.