← Blog
May 3, 2026 · Post · Kent Langley

The Bottleneck Moved, and History Already Told You Where

A long-form post written for X: why the engineering cuts are a snapshot, not the trend, and where the bottleneck goes next.

Every technology in human memory has created more jobs than it consumed.

The loom. The tractor. The spreadsheet. The internet.

Some jobs go away. Many more follow. We do not know what we do not know, much less what we already know.

This is the pattern. It has never broken. And it is happening again right now, while everyone watches the wrong number.

The contradiction that isn't

Companies are cutting engineers and hiring engineers in the same week. People call that a contradiction. It is not. It is a bottleneck shift in real time.

AI coding tools turned a 25,000 line a month team into a 250,000 line a month team.

Writing code stopped being scarce. Reviewing it became scarce. Security. Compliance. Quality assurance. The unglamorous work that keeps software from blowing up in production.

And here is where it goes wrong.

Cut junior coders because AI writes code now? Fine. The math works. For now. In the short term.

But the cuts do not stop at junior. They are landing on senior reviewers, security engineers, quality architects. The exact people who just became the scarcest resource in the building.

The logic looks rational from the inside. AI writes the code, so the team needs fewer humans to write code. True. But the same AI just multiplied the volume of code that has to be reviewed, secured, and shipped without breaking production. That part gets ignored.

The companies celebrating 10x output are cutting the people they need to handle what 10x output creates. That is not strategy. That is reading the wrong dashboard.

The system property

Goldratt named it in Theory of Constraints. Meadows mapped it in Thinking in Systems.

When you speed up one part of a system, you do not make the system faster. You make the next chokepoint louder.

The bottleneck never disappears. It moves.

What comes next

Engineer headcount drops this quarter. Engineer headcount returns next year, with different titles. Reviewers. Validators. Security architects. AI operators. Quality systems engineers.

The work changes. The need does not.

The companies that win from here are not the ones celebrating the cuts. They are the ones building review capacity, security infrastructure, and quality systems before the next chokepoint breaks something expensive.

The constant

People are still the bottleneck. They always were. They always will be.

What shows up on the org chart in 2028 that nobody is hiring for today?

Skate to the puck.

.K

Subscribe

Notes like this one also go out through factually, my newsletter. Subscribe at news.kentlangley.com, or point your reader at the RSS feed.

Founder OS · Published 2026-05-03 · Instance: factual · Project: content-engine/x-post-bottleneck-jobs
Skills applied: designing-fos, writing-copy, navigating-skills, writing-x-article
fos.kentlangley.com