125,000 Layoffs Later: DevOps Skills That Can Save Careers and Why

Over 125,000 tech jobs vanished last year. But DevOps roles? They're still hiring. Just not for everyone.

Watch short video version of this letter on YouTube.

Watch 1.5x saves your time ☺️

---

The pattern is violently clear.

Ten skills dominate right now. Everything else is, kind of noise. So let’s start with 10

Skill #10: Ansible (36% of Job Postings)

One in three DevOps jobs still needs configuration management.

Ansible survived where Puppet and Chef died because it’s agentless. SSH-based. Actually readable.

But here’s the split:

Don’t Keep 500 playbooks

Integrate Ansible as GitOps component.

Same tool. Different context. 40% salary gap.

Don’t specialize in Ansible alone. It’s a supporting actor, not the lead.

Skill #9: GCP (38% of Job Postings)

Google Cloud is the underdog with great developer experience.

38% mention rate means it’s real but not dominant. Usually appears as:

• Multi-cloud secondary

• Kubernetes-heavy primary

• Data/ML workload specialist

The advantage:

Less competition. Newer architecture. Better tooling.

Engineers who picked GCP early are now rare and expensive.

Skill #8: Bash (44% of Job Postings)

Nearly half of DevOps jobs explicitly require shell scripting.

Not “can run commands.” Actual scripting.

Error handling. Exit codes. Parsing output. Idempotent operations. Proper quoting.

Reality check:

Python is sexier. Bash is required. Learn both.

Skill #7: Docker (44% of Job Postings)

If you can’t containerize an application, you’re not a DevOps engineer.

You’re a system administrator with an outdated resume.

Basic Docker is assumed. What separates employed from searching:

• Multi-stage builds

• Layer caching mastery

• Security scanning

• Resource constraints

• Production debugging

Hard truth:

“I know Docker” is like “I know Microsoft Word.”

It’s not a skill. It’s basic literacy.

Skill #6: Jenkins (44% of Job Postings)

Wait. Jenkins? Isn’t it dead?

Wrong. Jenkins is zombie infrastructure.

Nobody wants it. Everybody has it. Somebody needs to maintain it.

44% of postings mention Jenkins because legacy pipelines exist.

But here’s the twist:

If Can migrate from Jenkins to modern CI/CD you are wanted.

Strategy:

Learn it well enough to maintain or migrate.

Skill #5: Azure (48% of Job Postings)

Almost half of DevOps roles mention Azure.

Less competition than AWS.

Enterprise-heavy markets pay premium rates for Azure depth.

Skill #4: Kubernetes (62% of Job Postings)

2/3 DevOps jobs require Kubernetes.

But “I deployed a pod once” doesn’t count.

Companies need engineers who use Kubernetes

• The survivors of debug CNI issues.

• Design resource limits properly.

• Handle persistent storage calmly.

• Troubleshoot CrashLoopBackOff in prod.

The secret weapon:

Understanding what happens UNDER the hood.

That knowledge gap is where salaries double. Yes, 2X.

Brutal truth:

Most companies have K8s clusters they don’t understand.

Becoming the person who does is career accelerator.

Skill #3: Terraform (66% of Job Postings)

2/3 of DevOps jobs require infrastructure-as-code.

Not optional. Foundational.

Terraform users who thrive:

1. Architected modular, reusable code

2. Moved 3,000-line chaos into clean modules.

3. Deploy time: 40 minutes to 7 minutes.

That engineer became untouchable.

Hot take:

Knowing Terraform syntax is premium skill.

Understanding state lifecycle is career insurance.

Skill #2: AWS (66% of Job Postings)

2/3 of DevOps roles demand AWS experience.

Tied with Terraform at 66%. Not a coincidence.

But not “I clicked around the console once.”

Real experience: (Something like)

• ECS, EKS management

What changed last year: Generic “cloud knowledge” died.

Companies want AWS-specific depth.

They’re tired of engineers who:

• Can't explain security groups vs NACLs

Reality check: Multi-cloud sounds impressive.

Single-cloud expertise pays bills.

Skill #1: Python (74% of Job Postings)

3/4 DevOps jobs require Python.

Not “nice to have.” Required.

This is the summit.

The skill that dominates the market.

• The ones making premium pays,

• they’re not just writing scripts,

• they’re building platforms.

What matters: You don’t need Python expertise.

You need competence.

Ship working automation without setting things on fire.

The brutal reality: If you can’t code, you can’t compete.

Last Thing

125,000 people lost their jobs last year.

• Most were competent.

• Many were talented.

• Some were brilliant.

They just weren’t aligned.

These 10 skills represent what companies pay for now.

Data source: prepare.sh

---

If you liked this essay, share with a friend or community that might find it useful, or DM me. If my writing is new to you, here’s the next one you might love reading: You know Kubernetes.