DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The AI Co-Pilot: How to Lead When Your Team's Best Player Is a Machine
  • Why Your GPU Fleet Is Both Full and Idle: Building a Capacity Orchestration Layer
  • The New Senior Developer Job Description: Half Engineer, Half AI Systems Architect
  • You Learned AI. So Why Are You Still Not Getting Hired?

Trending

  • Spring AI on Local LLMs
  • Part 1: Building Governed MCP Tool Services With Quarkus LangChain4j and Goose
  • When RabbitMQ Accepts a Message but Does Not Route It to a Queue
  • Fix the Target, Precompute Once: A Backend-Free Word-Ladder Solver With a BFS Distance Field

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. AI/ML
  4. Every Generation Fears the Machine. Here Is How the AI Job Panic Usually Ends

Every Generation Fears the Machine. Here Is How the AI Job Panic Usually Ends

Machines take tasks, and people invent new work. The research backs that pattern, with one catch for young workers that deserves a straight answer.

By 
Faisal Feroz
·
Nov. 03, 26 · Analysis
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
2.1K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

"A new disease of which some readers may not yet have heard the name."

— John Maynard Keynes (Economic Possibilities for our Grandchildren, 1930)

In 1930, John Maynard Keynes told the world it was being afflicted by something new.

The disease was technological unemployment: machines saving labor faster than we find new uses for it. Keynes said readers would hear a great deal about it. He was right. Ninety-six years later, you're hearing it again, this time about AI.

I've spent more than 20 years as a Chief Technical Architect and Fractional CTO, helping companies modernize the platforms they run on. I started my career in 2003 optimizing a physics engine for games. Today I design AI-first, event-driven platforms that write product content and translate it into 29 languages. Apache Kafka, the event streaming system behind those platforms, didn't exist when I graduated. Neither did anything like ChatGPT. So I have a personal stake in one question: does AI end careers like mine, or change them?

Here's my answer, built from history and current research. Machines take tasks, and people invent new work. That pattern has held for well over a century. But this time has one real catch, and it lands first on people just starting out.

The Stable Hand Could Not Have Predicted the Mechanic

Around 1880, New York and Brooklyn together had between 150,000 and 175,000 horses. Researcher Eric Morris estimates their manure added up to three to four million pounds a day, as he explains in From Horse Power to Horsepower. Whole careers circled those animals: stable hands, blacksmiths, carriage makers, and feed suppliers.

Then cars arrived, and many of those jobs shrank for good. That's the half of the story people remember. The other half is mechanics, gas station attendants, road crews, motel owners, and traffic engineers. In 1900, nobody could post a job ad for a mechanic, because there were no cars to fix.

The same script ran again with electricity, the personal computer, the internet, and the smartphone. Each wave erased some work, like typing pools and travel agencies, and created work no one had a name for yet. Economists have now measured how much. In a landmark study of US census data, MIT economist David Autor and his coauthors found that:

"The majority of current employment is in new job specialties introduced since 1940."

— Autor et al., (New Frontiers: The Origins and Content of New Work, 1940-2018, Quarterly Journal of Economics, 2024)

In plain terms, roughly six in ten jobs Americans do today did not exist in 1940.

The Bank Teller Plot Twist

ATMs are the textbook case. They arrived in the 1970s and took over the tasks everyone linked to tellers: handing out cash and taking deposits. The forecast seemed clear. Tellers were finished.

Economist James Bessen checked what happened. ATMs did cut the tellers needed at an average urban branch from 20 to 13 between 1988 and 2004. But cheaper branches meant banks opened more of them, and urban branches grew 43 percent. Teller jobs did not fall as ATMs spread. The work itself changed too, as Bessen explained in the IMF's Finance & Development magazine:

"Cash handling became less important and human interaction more important"

— James Bessen (Toil and Technology, March 2015)

Counting cash faded. Relationship building grew.

The story has a sequel, and it matters. Mobile banking removed the need for the branch itself. The Bureau of Labor Statistics now projects teller jobs to fall 13 percent between 2024 and 2034. So the lesson isn't that jobs are immortal. It's that outcomes depend on whether demand grows and what work remains after the machine takes its share.

Why Cheaper Work Often Means More Work

In 1865, economist William Stanley Jevons studied coal. Steam engines were getting more efficient, so people expected coal use to fall. It rose instead. In his book The Coal Question, Jevons wrote:

"It is the very economy of its use which leads to its extensive consumption."

— William Stanley Jevons (The Coal Question, 1865)

Economists now call this the Jevons paradox. When something gets cheaper to use, people use much more of it. Weaving shows the same effect. Bessen notes that power looms automated 98 percent of the labor needed to weave a yard of cloth, yet weaving jobs grew through the 19th century because cheaper cloth sparked far more demand.

Now apply the idea to software. If AI makes software faster and cheaper to build, businesses will want more of it: the internal tool nobody could justify, the custom app for a ten-person team. The effect isn't guaranteed, because demand has to grow when prices fall. But it explains why "less labor per unit" so often turns into "more units."

A Job Is a Bundle, and Bundles Get Repackaged

Here's the mental model that clears up most of the panic. A job isn't one task. It's a bundle of tasks. Automation pulls some tasks out of the bundle, and the rest get repackaged. Autor explains why the leftovers gain value:

"Tasks that cannot be substituted by automation are generally complemented by it,"

— David Autor (Why Are There Still So Many Jobs?, Journal of Economic Perspectives, 2015)

Take the teller again. Less cash counting made the human conversation more valuable.

I see the same repackaging in AI work. When generative AI drafts a product description or a translation, the scarce skill is no longer typing it. It's defining what "correct" means, building test sets, and measuring precision and recall until quality is a number the business can trust. Precision asks how often the system is right. Recall asks how much it misses. That work wasn't on any job board when I started.

The same research team found something every system designer should hear. New work tends to grow from technology that complements what people do, while innovations that only automate tasks or shrink demand for an occupation slow new work down. That's a design brief. Build AI that augments people, not just AI that removes steps.

Where the Pattern Gets Uncomfortable

So what do the numbers say about AI today? Generative AI went mainstream in November 2022. The Yale Budget Lab tracks the US labor market and updates its findings regularly. Its September 2026 update, which includes August data, says its analysis "does not provide clear evidence of labor market disruption associated with AI."

The broad job market looks ordinary so far. The lab itself warns that this may change as new data arrives.

But averages hide pockets. A Stanford Digital Economy Lab team of Erik Brynjolfsson, Bharat Chandar, and Ruyu Chen studied payroll data and looked at workers aged 22 to 25 in the most AI-exposed jobs, such as software development and customer service. They found a 16 percent relative decline in employment.

More experienced workers in the same jobs stayed stable. The authors call this early evidence consistent with AI hitting entry-level workers hardest, so treat it as a warning light, not a verdict.

That's the catch. One plausible reason is that entry-level tasks lean on textbook knowledge, which AI copies well, while experience builds judgment that is harder to copy. Autor says, "the real concern is for whom the new work has been created."

That's the right question for 2026. Not "will work exist?" but "who gets the first foothold in it?"

Three Moves for Ground That Keeps Shifting

First, learn the tools until they feel ordinary. Every wave rewarded the people who got comfortable early, whether it was spreadsheets, the internet, or an AI assistant. Use the tools on real work, not demos.

Second, own what the machine hands back. Judgment, quality, and accountability tend to survive automation. Someone must decide what good looks like, catch what the model gets wrong, and answer for the result. If you're early in your career, start now. Check AI output, write down what you changed and why, and build a record of good calls.

Third, practice inventing. Roughly six in ten of today's jobs did not exist in 1940, and someone invented every one of them. Build a small tool. Automate a boring process at your workplace. Publish what you learn. Job titles follow evidence.

Is this time different? Maybe in speed. Maybe in scope. The data so far says the old pattern is holding, and the uncomfortable parts are real and specific. Both things can be true. Curious people who keep learning, measuring, and building have historically been the ones who found the next job on the far side of the shift. There's little reason to expect that to change.


Faisal Feroz is a Chief Technical Architect and Fractional CTO with more than 20 years of experience in enterprise platform modernization, AI-first architecture, and event-driven systems. Readers who want to plan an AI strategy or a career move with a practical eye can connect with Faisal on LinkedIn, explore more of his writing on his blog, or reach out about fractional and advisory engagements. If this article helped you think more clearly about AI and the future of work, pass it to someone who's worried about their next step.

AI Machine career

Opinions expressed by DZone contributors are their own.

Related

  • The AI Co-Pilot: How to Lead When Your Team's Best Player Is a Machine
  • Why Your GPU Fleet Is Both Full and Idle: Building a Capacity Orchestration Layer
  • The New Senior Developer Job Description: Half Engineer, Half AI Systems Architect
  • You Learned AI. So Why Are You Still Not Getting Hired?

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook