Python Automation: The Jobs It Is Eliminating and the New Roles It Is Creating

Every few years, a new wave of automation anxiety sweeps through the professional world. In the 1980s, it was personal computers. In the 2000s, it was offshoring. In the 2010s, it was machine learning. Today, it is Python automation and AI coding tools.

The anxiety is understandable — and partially justified. Automation does eliminate jobs. It also creates new ones. The net effect, historically, has been positive for employment in aggregate but deeply disruptive for specific workers in specific roles. Understanding which jobs are at risk, which are growing, and what determines which side of that divide you fall on is one of the most practically important questions in professional development.

What the Data Shows About Automation and Employment

The most comprehensive research on automation and employment comes from the McKinsey Global Institute, the Oxford Martin School, and the World Economic Forum. Their findings are consistent in direction but differ in magnitude.

The Oxford Martin School's 2013 study by Frey and Osborne estimated that 47% of US jobs were at high risk of automation within 20 years. This figure was widely cited and widely misunderstood — it represented the proportion of jobs with high automation potential, not the proportion that would actually be automated in that timeframe. Subsequent research by the OECD, which looked at tasks rather than whole jobs, found that only about 9% of jobs were highly automatable, because most jobs contain a mix of automatable and non-automatable tasks.

The McKinsey Global Institute's research found that while automation would displace significant numbers of workers, it would also create new jobs — and that the net effect on employment would depend heavily on the pace of economic growth and the effectiveness of reskilling programmes.

What is consistent across all the research is the pattern of which tasks are most automatable: routine cognitive tasks (data entry, basic analysis, standard reporting) and routine physical tasks (assembly, sorting, basic inspection). The tasks least automatable are those requiring complex problem-solving, creative thinking, social interaction, and the application of judgment to novel situations.

The Jobs Python Automation Is Eliminating

The jobs most directly affected by Python automation are those built around routine data processing. Data entry roles, basic reporting roles, and administrative roles that involve moving data between systems are being automated at scale. A Python script that takes two hours to write can replace a task that previously took a human worker several hours per week — indefinitely.

The McKinsey analysis estimated that data processing and collection activities, which account for a significant proportion of working time in many office roles, have an automation potential of 64% and 69% respectively. These are not fringe activities — they are the core of many administrative, analytical, and operational roles.

The roles most at risk are not the lowest-skilled roles. They are the roles built around routine cognitive work — the kind of work that is predictable, rule-based, and does not require complex judgment. A data entry clerk is at risk. So is a junior analyst whose primary function is to produce standard reports from structured data.

The Jobs Python Automation Is Creating

The same forces that are eliminating routine data processing roles are creating new roles — and the new roles are, on average, more cognitively demanding and better compensated than the roles they replace.

The most direct new roles are in automation itself: the Python developers, data engineers, and automation specialists who build the scripts and pipelines that replace manual work. These roles are growing rapidly. The Bureau of Labor Statistics projects software developer employment to grow significantly faster than average across the coming decade.

But the more important category of new roles is less obvious: the roles that require human judgment to direct, evaluate, and improve automated systems. A Python script that automates a reporting process still requires a human to define what should be reported, evaluate whether the output is correct, and decide what to do with the findings. These judgment roles are growing as automation handles more of the routine work — and they require the analytical thinking and framework skills that automation cannot replicate.

What This Means for Your Career

The practical implication is straightforward: the workers who will benefit most from automation are those who can direct it, evaluate its outputs, and apply judgment to the decisions it informs. The workers who will be most displaced are those whose primary value is in executing the routine tasks that automation is absorbing.

This is not a prediction about the distant future. It is a description of what is already happening. The Python skills that are most valuable are not the ability to write automation scripts — though that is valuable. They are the ability to identify which processes should be automated, design the automation correctly, evaluate whether it is working, and apply the time freed up by automation to the higher-judgment work that creates more value.

That is a framework thinking skill. It requires understanding not just how to write Python, but how to think about processes, value, and the appropriate division of labour between human judgment and automated execution.

@misc{ffa-2026,
  author = {Framework First Academy},
  title = {Python Automation: The Jobs It Is Eliminating and the New Roles It Is Creating},
  year = {2026},
  howpublished = {\url{https://www.frameworkfirst.site/blog/python-automation-jobs-that-disappeared-and-new-ones-created}},
  note = {Accessed: 2026-09-09}
}