Will AI Take My Job? A Practical Way to Think About It
People ask it as a yes or no. It isn't one. Not because nobody knows the answer, but because "job" is the wrong unit to ask about. Almost nobody does one thing at work. You do a bundle of tasks, and AI hits each one differently. Some are already mostly automatable. Some are decades out. A few will actually get easier in a way that makes you more valuable, not less. Average all of that into a…
When people inquire if AI will take their job, the question is not binary. The reason is not a lack of knowledge, but because the unit of consideration is incorrect. Most individuals perform a variety of tasks at work, and AI's impact varies across these tasks. Some tasks are already highly automatable, while others are still far away.
A few tasks may become easier, potentially increasing an individual's value rather than diminishing it. Evaluating one's job exposure based on these tasks, rather than their job title, provides a more practical perspective. The article outlines a method to assess one's exposure task by task, explaining what safeguards a role, and suggesting actionable steps.
The core idea is that it's the tasks, not the jobs, that matter. Economists have been employing a task-based approach to automation for years, finding it more useful than predictions about entire occupations. The article uses the example of a marketing manager, whose week might involve writing copy, analyzing campaign performance, attending client calls, deciding on budget allocations, briefings designers, resolving team conflicts, and creating reports.
Each of these tasks is scored based on four factors: whether the input is mostly text or data, if there's a clearly correct output, if mistakes are cheap, and if the task requires accountability. Tasks scoring high on these factors are more exposed to automation. The article also discusses what safeguards a role, highlighting four key factors: accountability, physical presence and dexterity, relationships and trust, and judgement under ambiguity.
These factors are mostly not technical skills, and the common advice to learn coding as a safeguard is counterproductive as coding is highly automatable. The article then explores the near-term impact of AI, noting that most discussions focus on one aspect while ignoring the other. While AI isn't replacing whole roles at scale yet, the composition of roles is shifting quickly, affecting those whose work is mostly in the exposed column.
The most immediate risk for most people isn't being fired but being outpaced by someone doing the same role with the mechanical parts removed. This change often appears as "we're not replacing that person who left" rather than "redundancy." The article concludes by contrasting past automation waves with the current situation, emphasizing that while ATMs didn't eliminate bank tellers, the current AI wave is reshaping roles and creating a competitive risk for those whose work is highly automatable.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
