Technology & The Future

The Job Isn't Gone. It Just Got Quietly Hollowed Out.

AI isn't showing up as mass layoffs — it's showing up as a slow removal of the tasks that gave work its texture, and most workers don't have language for what they've lost.

Julian CrossJune 15, 20269 min read
The Job Isn't Gone. It Just Got Quietly Hollowed Out.

The job still exists. The title is the same, the salary roughly the same, the org chart unchanged. But something has shifted in the past eighteen months that workers are struggling to name. The interesting parts keep disappearing. The judgment calls, the creative detours, the problems that required you to actually think — those are being absorbed, one by one, into an AI workflow. What remains is coordination, review, and a light supervisory function over outputs you didn't produce. You are still employed. You are also, in some hard-to-articulate way, less present in your own work.

This is not the automation story most people have been watching for. The dominant narrative over the past decade was about deletion: which jobs would survive, which would be eliminated, which categories of worker would be stranded on the wrong side of a technological rupture. That story had a clean shape — job in, automation out — and it generated an enormous amount of research, punditry, and policy anxiety. What it missed was a subtler and more pervasive transformation happening inside jobs that never went away. Not elimination. Excavation.

A working paper circulating through labor economics and organizational behavior research on arXiv, alongside data from the Society for Human Resource Management's 2025 Automation Survey[3], is beginning to give shape to what many workers have only felt. The finding is not that AI is replacing workers at scale. It is that AI is systematically absorbing the tasks within jobs that carry the most cognitive weight, creative friction, and decision-making latitude — while leaving intact the administrative shell that surrounds them. Job titles persist. Headcount stays flat or declines slowly. But the actual substance of work is being redistributed upward into software, leaving workers to manage the interface between the tool and the output.

Researchers describe this as task-level automation rather than job-level automation[2], and the distinction matters more than it might sound. When a job is eliminated, the disruption is visible — it shows up in unemployment filings, in severance packages, in press releases about restructuring. When tasks are automated out of a job that still exists, the disruption is invisible in the aggregate data and deeply felt in the daily experience of work. The job survives the measurement. The worker absorbs the loss.

What Task-Level Extraction Actually Looks Like

To understand what is being removed, it helps to think about what makes a job feel like skilled work. It is almost never the formal job description. It is the texture of the problems that arise — the ambiguity that requires judgment, the edge cases that require context, the decisions that have to be made without a clean precedent. These are the moments that build expertise over time, that create the sense of professional identity, and that tend to be where workers feel most engaged. They are also, structurally, exactly what large language models and AI decision-support tools are now best positioned to absorb.

A paralegal who spent years developing instincts about which contract clauses tend to become problems, a financial analyst who built a feel for which anomalies in the data were signals and which were noise, a marketing strategist who learned through iteration which creative directions tended to land with a particular audience — all of these workers developed cognitive assets through accumulated practice. What AI tools do is compress that development cycle dramatically, not by replicating the insight, but by handling enough of the routine application of it that the worker no longer gets the repetitions that built the expertise in the first place. The craft is not stolen. It just stops being practiced.

“The craft is not stolen. It just stops being practiced.”

The SHRM data[3] illustrates how unevenly this lands across job categories. Knowledge workers in legal, finance, marketing, HR, and mid-level management are seeing the highest rate of task-level AI integration, not because their jobs are most vulnerable to replacement, but because their work is most legible to current AI tools. Tasks that involve processing language, summarizing documents, generating initial drafts, flagging patterns in structured data, and producing the first-pass version of almost anything — these are being absorbed rapidly and often without formal announcement. A tool gets added to the workflow. A step gets skipped. A deliverable arrives faster because the AI did the heavy lifting. Over months, the shape of the job changes without the job changing on paper.

The Hollowing Doesn't Show Up in the Data That Gets Reported

One reason this transformation is so hard to track is that most labor market measurement was built to detect job creation and job destruction, not job degradation. Unemployment figures, payroll reports, sector-level employment data — none of these instruments were designed to capture a shift in the cognitive content of work that leaves headcount unchanged. A worker who has lost half the interesting work in their role is still employed in every sense that shows up in aggregate statistics. The job is fine. The work is not.

Organizational researchers describe what is being lost in terms of discretion — the degree to which a worker can make meaningful choices about how to approach their tasks. High-discretion work is associated with engagement, skill development, professional satisfaction, and the kind of organizational knowledge that is genuinely hard to replicate. When AI tools absorb the high-discretion tasks and leave workers with the low-discretion residue — the checking, the approving, the formatting, the routing — they are doing something that looks like efficiency at the system level and feels like deskilling at the human level.

“Efficiency at the system level tends to feel like deskilling at the human level.”

There is also a feedback loop that research in organizational behavior has been tracking for years under different conditions but which applies here with particular force: when workers are removed from the practice of complex tasks, they lose the ability to evaluate the quality of the outputs that replace their practice. A paralegal who no longer drafts contracts stops being able to reliably catch what an AI-generated draft gets subtly wrong. A financial analyst who no longer builds models from scratch stops being able to recognize when an automated output is making assumptions that don't fit the situation. The human oversight that companies cite as the safeguard against AI error is being quietly undermined by the very automation it is supposed to check.

Why Workers Are Only Now Finding Words for This

Part of the reason this shift has been so hard to name is that each individual change feels reasonable. Adding an AI writing assistant to the workflow seems like a time-saver. Using a tool to auto-summarize meeting notes seems like an obvious efficiency. Having an AI generate the first draft of a client report seems like a sensible allocation of effort. None of these changes, considered in isolation, looks like a diminishment. Considered together, over time, they can restructure the actual nature of a job to the point where the worker who occupied it is doing something qualitatively different from what they were hired to do — often without any formal acknowledgment that a change has occurred.

The framing that employers tend to use — that AI is freeing workers from tedious tasks so they can focus on higher-value work — has a plausible logic and, in some cases, describes something real. But it also papers over a more complicated dynamic. The tasks being automated are not always the ones workers find tedious. Research on work motivation has long shown that the tasks people find most meaningful are often the ones that involve difficulty, uncertainty, and the satisfaction of getting something right without a guaranteed path to the answer. These are precisely the tasks that current AI tools are most eager to absorb. What gets left behind, frequently, is coordination overhead, quality review of AI outputs, and the administrative connective tissue of the job — the least engaging, least skill-building, least career-advancing work in the portfolio.

Workers have been searching for language that captures this. The phrase 'AI anxiety' gets used in workplace surveys, but it tends to suggest fear of job loss, which is often not quite what people are feeling. What they are feeling is closer to professional estrangement — still present in the job, still productive by measurable standards, but increasingly peripheral to the decisions and outputs that constitute the work. Some describe it as watching their own expertise become less relevant not because they've been replaced but because the problems that would exercise it are being handled before they arrive.

The Long-Term Cost of Managing Outputs You Didn't Make

There is a hiring and talent development dimension to this that organizations are only beginning to reckon with. If mid-level knowledge workers spend the next several years primarily reviewing and approving AI-generated work rather than producing and iterating on their own, the pipeline of judgment and expertise that feeds senior roles gets thinner. The senior analyst who can walk into an ambiguous situation and make a good call without a model to consult developed that capacity through years of doing the messy, uncertain, lower-level work themselves. That developmental path[1] is being shortened, bypassed, or quietly eliminated in organizations that are integrating AI tools fastest.

The SHRM survey data points to a tension that HR professionals are starting to flag internally but rarely raise publicly: companies are capturing real efficiency gains from AI task absorption, which creates pressure to continue and expand deployment, while simultaneously seeing early signals of reduced employee engagement, slower skill development, and a sense among workers that professional growth is stalling. These two facts are not easy to reconcile when the quarterly productivity numbers look good and the engagement costs are slow to materialize and hard to attribute.

What Remains, and Who Owns It

The economic framing most often applied to AI and labor focuses on whether workers will be displaced or augmented — a binary that was always too clean and is now visibly inadequate. The more accurate frame may be about the distribution of meaningful work. As AI tools absorb more cognitive tasks, meaningful work does not disappear from organizations. It concentrates. The decisions about what to prompt the AI to produce, how to evaluate the output, how to set the constraints and the direction and the standards — these remain human functions, at least for now. But they are moving upward and inward, toward a smaller number of people with the organizational authority to define what the tools are trying to do.

“Meaningful work doesn't disappear from organizations. It concentrates.”

For workers below that threshold, the job becomes increasingly about execution within a system they did not design and cannot significantly alter. This is not new as a structural description of employment — plenty of jobs have always involved executing within tight constraints. What is new is that it is happening to job categories that were previously defined by their relative autonomy, and to workers who built careers on the assumption that their judgment and skill were the primary inputs. The renegotiation of that assumption is underway, but it is happening through workflow changes and software rollouts rather than through any conversation that would give workers the standing to push back.

There is no clean villain in this story and no simple remedy. The efficiency gains are real. The tools are, in many cases, genuinely useful. The problem is not that AI is being used but that the transition is being managed as a productivity project rather than a labor conditions project — with all the measurement focused on what gets faster and almost none of it focused on what gets lost. Workers are discovering this through experience, in real time, without vocabulary or institutional support for naming what is happening to them. The job is still there. The task is to figure out what, exactly, is now being done inside it.

References

  1. Automation, AI, and the Intergenerational Transmission of Knowledge (arxiv.org)
    Examines how AI-driven automation disrupts early-career learning and the intergenerational transmission of tacit knowledge through workplace practice.
  2. Pascual Restrepo on AI, automation, and the future of work (economics.yale.edu)
    Establishes the distinction between task-level automation and job-level automation that frames the article's core argument.
  3. Automation, Generative AI, and Job Displacement Risk in U.S. Employment (shrm.org)
    Provides 2025 data showing knowledge workers in legal, finance, marketing, HR, and management experience highest rates of task-level AI integration.

About Julian Cross

Julian Cross writes about AI, automation, surveillance, digital identity, labor, human relationships with each other and automation, complex systems and attention — less about what new tools, studies and observations can do in theory than what they're already doing to how we work, spend, relate, and get measured. His work follows leads to the point where it stops being a product and starts being a condition.

More like this

The AI Agent Doesn't Work For You. It Works Around You.

The AI Agent Doesn't Work for You. It Works Around You.

Julian Cross 9 min
AI Isn't Killing Entry-Level Jobs. It's Closing the Door Before You Get In.

AI Isn't Killing Entry-Level Jobs. It's Closing the Door Before You Get In.

Julian Cross 10 min
Your Employer Is Training Its Replacement on Your Keystrokes

Your Employer Is Training Its Replacement on Your Keystrokes

Julian Cross 10 min