Why Do Job Postings Demand 8 to 10 Programming Languages When We'd Never Accept It in Other Fields?

The Enumeration Syndrome

Open LinkedIn. Search for a developer position. Here’s what you’ll see:

“We are looking for a Senior Backend Developer with solid experience in PHP, Python, JavaScript, Go, Rust, SQL, Git, Docker, Kubernetes, AWS, GCP, MongoDB, PostgreSQL, Redis, RabbitMQ, Elasticsearch, and a good understanding of microservices patterns.”

That’s it. One position. Ten to fifteen technologies. Sometimes more.

Now, do a simple exercise: imagine these requirements in other fields.

In Medicine

Search for a surgical job posting:

“We are seeking a general surgeon with a minimum of 10 years of experience in cardiac surgery, neurosurgery, pediatric surgery, orthopedics, gastroenterology, urology, ophthalmology, ENT, dental surgery, and surgical dermatology.”

What would you do? You’d laugh. Or call an employment lawyer. It’s absurd.

A cardiac surgeon is a cardiac surgeon. We don’t ask them to do neurosurgery on the side. And if we do, we pay them like two people. Period.

Yet in tech, we ask exactly that: be an expert in three fields simultaneously, at the same salary.

In Linguistics

Imagine a job posting for a translator:

“We are seeking a professional translator fluent in English, Spanish, French, German, Mandarin, Japanese, and Arabic. Minimum 5 years in each language.”

That’s delusional. A specialized translator is already a career. English-French? Five years. English-Mandarin? Another five years. Add seven more languages to that, and it’s… impossible.

Yet that’s exactly what we ask developers to do.

In Law

Look at job postings for lawyers:

“Law firm seeks attorney specializing in commercial law, labor law, administrative law, criminal law, family law, intellectual property, and international contracts.”

Seriously? Firms have departments. The IP expert doesn’t handle divorces. The labor lawyer didn’t study criminal law in depth. You hire specialists. Precise. Focused.

Why Did This Become Normal in Tech?

Three reasons.

1. The Recruiter Doesn’t Understand the Job

The worst part is, it’s often true. A generalist recruiter sees a job description from the CTO. It lists “Python, C++, Go, Rust.” The recruiter doesn’t know that C++ is for embedded systems, Go is for backend services, and Rust is a current obsession. They just… see stuff listed. They pile it on. They imagine more = better.

Result: One posting for three different jobs, written as if it was one.

2. Technical Leaders Panic

The other explanation: the CTO is scared. He saw a startup next door lose a developer who was the only one who knew Kubernetes. So he says: “We need someone who can do everything.”

What that really means: “We manage technical risk poorly.”

The real solution: Document. Train. Share knowledge. Don’t ask one person to be a living encyclopedia.

3. Downward Wage Competition

Tech salaries are stagnating in many countries. So how do you attract people? By demanding more qualifications. It filters out weak candidates… and strong ones too, because they know these lists are bluffing.

Result: Nobody matches. The CTO complains “there are no good developers anymore.” False. He’s just asking for the impossible.

The Final Hypocrisy: The Candidate’s Resume That Lists Everything

Here’s what perfectly sums up the absurdity.

A developer reads this monstrous job posting. He thinks: “OK, they want all of that. I’ll show that I master Python, Go, Rust, Kubernetes, AWS, GCP, MongoDB, PostgreSQL, Redis, and RabbitMQ. I’ll put it in my resume.”

What happens next?

The company questions him. In the interview:

“So… you say you master Rust, but I only see one small hobby project on GitHub. And you claim to know both AWS AND GCP? That’s weird. Typically, people who have real expertise specialize. We’re skeptical.”

They’re right to be skeptical.

Because it’s impossible to truly master 8 to 10 languages at the same level. You can’t be equally proficient in Python and Rust. Not really. Not with equivalent depth. Or you spend 80 hours a week learning, which isn’t sustainable.

The Paradox

The job posting says: “We want someone who masters 10 technologies.”

The candidate’s resume says: “I master 10 technologies.”

The company replies: “Yeah… we don’t believe that. You’re too much of a generalist. We want depth.”

It’s a trap.

The job posting is written in a way that repels honest candidates. The ones who say:

“I’m really good at Python. I have 8 years in Python. I also know JavaScript and a bit of Go. But that’s it, my stack.”

Those candidates don’t apply. They know they’ll get filtered out before the interview.

Who will apply? Three categories:

1. Naive juniors: They think they can really learn all of that. Spoiler: they’ll burn out in 6 months.
2. Bullshitters: They inflated their resume, they pretend to master stuff they barely touched. They fake it.
3. Other recruiters reading the job and thinking: “There are 5 positions bundled into one here.”

So you end up with:

• Burned-out juniors writing bad code
• Liars on your team
• Nobody to actually do good work

It’s a filter that selects for dishonesty, not competence.

The Comparison With Other Fields (Again)

Imagine the same game in medicine.

The job posting says: “We want a cardiologist with 10 years in cardiology, 10 years in neurosurgery, and 10 years in pediatrics.”

A real cardiologist thinks: “No thanks, that’s a bluff. I’m not applying.”

Who applies? The charlatans who say “yeah I have the basics in everything” and will kill your patient.

In law, it’s the same. The delusional posting repels real specialists and attracts generalists who’ll do bad work.

In tech, we just… accepted it.

In Conclusion

No, tech job postings aren’t comparable to medicine, linguistics, or law because “tech evolves faster.” That’s an excuse. Medicine evolves too. New techniques arrive in surgery, new drugs in pharmacology. But you don’t ask the surgeon to be an expert in everything simultaneously.

What has become normal in tech would be abusive anywhere else.

It might be time to ask a simple question: is this a good practice… or just a norm nobody questioned because “we’ve always done it this way”?

Welcome to tech in 2026.