18 and Ignored. 45 and Invisible. Same Tech Industry. Same Hiring Broken.

Too young to be trusted. Too old to be affordable. The hiring math in tech never adds up.

Last month a prospect said: "We need someone mid-thirties or younger to match the vibe." My Terraform state file never once asked for my birth year. And Kubernetes doesn't check your LinkedIn before accepting YAML. Let's bust some myths. Innovators are under 25? The 50-year-old who wrote rsync says hi. Seniors resist new tech? I learned Helm before version three. Juniors can't own production? I ran a datacenter solo at 24.

Two engineers I know personally. One is 18 - writes Terraform modules cleaner than most seniors, understands networking, ships consistently. He's filtered out before anyone reads his code because the "3 years of experience" requirement is physically impossible for him to meet. The other architected systems running billions of transactions. He gets a "culture fit" pass because someone decided curiosity expires with age. Both assumptions are lazy. Both cost companies engineers who would have been great.

Age is a metric. Impact is a KPI. They are not the same thing. The next time you're writing a job requirement or sitting on a hiring panel, ask whether you're filtering for skill or filtering for familiarity.

0:00 "We need someone under 35 to match the vibe"
0:12 Terraform never asked for your birth year
0:35 Myth-busting: innovators, seniors, and juniors
1:30 What actually matters: curiosity, feedback, culture
2:20 Age is a metric. Impact is a KPI.

Too young. Too old. Never just right. Subscribe if the hiring system frustrates you too.
devopsdive.com

#DevOps #Ageism #TechHiring #CareerAdvice #DevOpsDive

Видео 18 and Ignored. 45 and Invisible. Same Tech Industry. Same Hiring Broken. канала DevOpsDive