Start with the written guide
How AI is changing jobs and roles — the same entries, grouped in the order most people need them, with what to do first.
Read the roles changing with AI guide53 free resources on this topic. Everything here is free and hand-picked. You can also search within this topic.
The article discusses AI skills appearing in job postings and draws on analyses of postings from 2025 and 2026. It breaks demand down by role type and discusses implications for career skill-building.
The author proposes approaches to hiring junior software engineers as AI changes development work. The piece follows earlier writing and a talk about changes to software engineering.
The page addresses future-of-work trends in the context of AI and global employment. G-P presents its global hiring and workforce management services alongside the resource.
The author traces how related software operations work has been labeled over time, including DevOps, SRE, and platform engineering. The article discusses the evolution and overlap of software job titles.
The article shares the winning entry in an essay challenge about changes in software development. The page introduces the piece as part of The Pragmatic Engineer newsletter. The site offers paid options alongside free content.
Fair Play Talks article on a survey of employees' views of CEO transparency about AI's effect on careers.
Amazon engineering leadership's guideline on the software engineer role as AI changes the work.
A Brookings report outlining a four-part policy framework (brakes, steers, buffers, and shifts) for supporting workers as AI changes jobs.
UC Today article by Kristian McCann on whether companies will use AI productivity gains to cut headcount or reinvest them in capacity, citing research suggesting the technology's impact on jobs remains uneven.
Reports research on the spread of AI mentions in U.S. job postings and compares the pace with earlier technology waves. Discusses how employers may need to change tasks and workflows rather than simply add AI tools to existing routines.
Gartner analysts Brook Selassie and Helen Poitevin argue that current workforce data supports an uneven transition rather than imminent mass unemployment. They discuss adoption constraints, early-career risks, role redesign and reskilling, while acknowledging uncertainty about future employment.
Brookings on workforce policy and AI.
In plain terms: Brookings sets out workforce policy options for helping workers adjust to AI.
In plain terms: A World Economic Forum piece on how AI is changing jobs and skills demand, part of its Jobs and the Future of Work series.
A report on the share of data analyst jobs requiring AI skills.
An analysis of different AI engineering roles and what they build in 2026.
A blog post arguing that organizations which do not give employees time to practice with AI coding tools risk falling behind competitors that do, with examples of workflow shifts in software engineering teams.
Bipartisan Policy Center issue brief using network analysis to examine which job moves actually change a worker's options in the AI economy, and where workers have limited paths to better roles.
A worker survey on whether AI is already causing job losses finds a more complicated picture than the headlines suggest, looking at how AI is actually affecting employment and day-to-day work.
Fast Company report on entry-level tech hiring in New York City falling sharply as AI takes over junior-level tasks. (Described from the headline and related reporting — the page itself could not be read.)
Labor economist Gad Levanon argues on his Labor Matters newsletter (Oct 1, 2026) that most of the public debate underestimates how much AI has already changed the US economy and labor market. He estimates underlying GDP growth at about 3 percent, driven largely by AI-related business investment, and says his reading of the evidence is not definitive proof.
Mia de Búrca argues that AI has removed the friction junior engineers once relied on to build critical thinking, and that leaders should make critical thinking an explicit expectation in reviews and postmortems.
CNBC's August 18, 2026 coverage of LinkedIn's AI Talent Divide study, with comments from LinkedIn economist Kory Kantenga. It reports Gen Z makes up more than two-thirds of hires for forward deployed engineer and AI engineer roles (median pay $199,000 and $166,000), millennials 60% of head-of-AI hires, and women 26% of new AI hires, and closes with his advice on computer science degrees, data experience and side projects.
NPower's research page on how AI is changing early-career tech work, from the nonprofit that runs free tech training programs for veterans and young adults.
Investopedia article on hiring rebounds in roles hit by AI and what that means for the value of related degrees. Investopedia blocked the automated check, so this description is based on the title.
Ratio Institute Working Paper No. 388 (Lodefalk, Löthman, Koch, Engberg) on how generative AI relates to hiring across age groups. Free PDF.
Stanford Digital Economy Lab paper using payroll data to track employment changes for early-career workers in jobs most exposed to AI.
California Policy Lab report (June 2026, Hyman, von Wachter and co-authors) using unemployment insurance claims to measure job losses linked to AI. Free PDF.
Report on a September 2026 analysis by IT support provider Hamilton Group of 60 occupations with AI automation risk below 45%, compared against AI augmentation data from the Anthropic Economic Index and current employment and median wage figures. Emergency medical technicians, paramedics and several healthcare and social service roles rank among the lowest-risk.
Yale Insights on research by Yale SOM's Menaka Hampole and co-authors: when AI automates a task it fades from job descriptions, but workers often shift to other work and firms become more productive.
Why I recommend it: A readable summary of one study, written by the business school that produced it. Useful balance to "AI will take every job" headlines, but it is one data set, not the final word.
CNBC's August 2026 survey report on the split between workers and managers over whether junior staff should use AI tools on the job — and what that means for entry-level careers.
Why I recommend it: Free to read. It's one survey of CNBC's own audience panel, so treat it as a snapshot of opinion, not a measurement of the whole workforce.
Reporting on New York City's growing AI and tech industry, what the Mamdani administration's plans could mean, and how CUNY students are positioning for the jobs.
Why I recommend it: Local reporting with a policy angle — useful for New Yorkers, less so elsewhere. The page blocked automated checks but opened in a browser.
CNBC report (Sept. 23, 2026) on AI taking over junior-level tasks and how employers are changing graduate and entry-level hiring.
Why I recommend it: Free to read. Examples come mostly from large firms; smaller employers may look different.
Sponsored piece (Feb. 2026) arguing CS jobs aren't collapsing but getting harder to enter; cites 6.1% unemployment for new CS grads vs 4.8% overall.
Why I recommend it: Paid content written by Rize Education, which sells courses to colleges. Free to read.
Dewey Data review of mixed research on AI and jobs; job-posting data suggests firms are changing what they hire for more than how much.
Why I recommend it: Written by a data vendor that sells datasets used in this research. Check the original studies.
US Census Bureau working paper (CES 26-56, September 2026) by Cody Orr, Lee C. Tucker and Lawrence Warren, using administrative records covering about 29% of US bachelor's degrees conferred 2016-2024. Graduates in the most AI-exposed tenth of majors saw their chance of being employed in the quarter after graduation fall five percentage points, and first full-quarter earnings fall thirteen percent, starting immediately after ChatGPT's release in late 2022. The earnings hit is comparable to graduating into a large recession. About half came from lower pay inside the same industries, the rest from graduates shifting into lower-paying sectors such as restaurants and retail. The effect shrinks to about five percent two years out but does not disappear for the most exposed majors.
Why I recommend it: This is the strongest evidence yet that AI has already moved entry-level pay, because it uses actual wage records rather than employer statements or surveys. Two things to hold onto: the paper says plainly it has not been through Census Bureau review and is not an official position, and exposure is measured by what a major typically leads to, not by whether any particular employer used AI. So it tells you which fields got harder to enter — not that a machine took a named job.
Pew Research Center short read, 18 August 2026, on a survey of US adults conducted 22-28 June 2026. 52% now say they are more concerned than excited about AI in daily life, up from 37% in 2021. Among adults aged 18-29, 55% are more concerned than excited and 11% more excited than concerned, and 73% think AI will mean fewer US jobs over the next 20 years, up from 61% in 2024.
Why I recommend it: Useful when a client says the worry is just in their head — it is not, and the numbers are free to download as a spreadsheet. Read it as what people expect, not as what has happened to employment: it measures opinion, not job counts.
Stanford Digital Economy Lab working paper by Bharat Chandar and Bouke Klein Teeselink, separating what happens to jobs after a firm adopts generative AI into a company-wide productivity effect and changes in what specific kinds of workers are asked to do.
Why I recommend it: Free, with the full PDF on the page. It is a working paper dated 21 September 2026, meaning it has not been through peer review yet, so read it as early evidence. Useful because it does not answer 'will AI take jobs' — it asks which workers get asked to do more and which get asked to do less.
Allwork.Space's write-up of a four-day Reuters/Ipsos poll that closed on Sunday 20 September 2026: 73% of Americans worry AI companies have not gone far enough to prevent serious harm, 55% favour slowing AI development, 39% say AI is having a negative effect on society (up from 36% the month before, the highest since Reuters/Ipsos began asking in March), and only 11% call it positive. Most respondents said federal officials, not the companies, should set safety standards. Free to read, no paywall.
Why I recommend it: Useful when you need a number for how the public actually feels about AI at work rather than how vendors say it feels. Two honest limits: this is Allwork.Space reporting a Reuters/Ipsos poll, so read the original poll before quoting a figure in writing, and a poll measures opinion, not job losses — it tells you nothing about how many roles AI has actually replaced.
A free tracker documenting AI-driven layoffs, closures and job displacement by country, industry and company, with each entry sourced back to reporting.
From the site: AIimpacted documents AI-driven layoffs, closures, and job displacement across every country, industry, and company - reported, sourced, and discussed.
Why I recommend it: Useful for seeing which roles and industries are actually being cut rather than which ones headlines say are at risk. Treat it as a directory of reported cases, not a forecast.
IEEE Spectrum article on how AI is shifting entry-level engineering work toward higher-order thinking, review and collaboration skills, and what recent graduates can do about it.
From the site: How can recent grads navigate a job market transformed by AI? Learn how to make AI work for you, not against you.
Why I recommend it: Free to read on IEEE Spectrum. Practical if you are early-career: it describes what junior work is turning into rather than predicting job counts.
An internal-talk write-up in which AWS's chief AI and technology officer lays out how he expects AI and cloud work to change, including what he thinks engineers should get good at. Free to read, no sign-up.
From the site: At the AWS Global Meeting, Matt Wood drew a parallel between AI today and cloud's early days—and brought a live demo to prove the future is already here.
Why I recommend it: Worth reading as an industry leader's view of where the work is heading — it is also Amazon talking about Amazon, so treat the optimism as a company position, not a neutral forecast.
A breakdown of ten new AI job titles — from agent orchestration to evaluations specialists — with what each role actually does and what hiring managers screen for.
From the site: Discover the 10 fastest-growing AI roles in 2026. Learn who to hire for ethics, UX, prompt engineering, and more. Stay ahead with AI talent.
Why I recommend it: Written to help companies hire, which makes it a clear read on the titles and skills being asked for right now if you are aiming at AI work.
A free article on why breaking in or changing careers feels harder right now, with what job seekers can control in an AI-heavy hiring market.
Why I recommend it: Reassuring and practical if the search is knocking your confidence.
Free workplace data showing that as AI use rises, more time is going into troubleshooting AI output than into productivity gains.
Why I recommend it: Good counterweight to AI hype in job interviews and internal pitches.
A Liberty Street Economics post from the New York Fed arguing that, so far, AI adoption is being used to change how work is done rather than to reduce headcount, based on regional business survey data.
Why I recommend it: A useful counterweight to AI job-loss headlines; helpful for understanding how employers are actually deploying the technology right now.
Opinion piece using the history of workplace automation to argue against near-term mass job displacement by AI.
Why I recommend it: Useful counterweight if the headlines have you panicking. Read it alongside the more pessimistic forecasts.
An essay weighing the argument that AI adoption could push unemployment into double digits, against the labor data we actually have so far.
Why I recommend it: I collect both the alarmed and the skeptical takes on AI and jobs on purpose. Read this next to the Census and Brookings data in this collection and form your own view rather than borrowing a headline.
Ramp's data report using anonymized corporate spending and hiring signals to track where AI is actually changing headcount and job functions.
Why I recommend it: Real transaction data instead of survey guesses. Useful if you want evidence about which roles are shifting rather than opinions.
Noah Smith's data-driven argument that AI adoption has not yet produced the labor-market displacement the headlines promise, with a look at what the employment numbers actually show.
Why I recommend it: Read this before you panic about your field disappearing. It is the most level-headed counterweight I have found to the "AI took the jobs" narrative.
The September 2 Beige Book finds scarce AI engineers but weaker demand for some junior technology and administrative-support roles.
From the site: The September 2 Beige Book finds scarce AI engineers but weaker demand for some junior technology and administrative-support roles.
Why I recommend it: A useful data point showing that AI is reshaping hiring unevenly—senior AI talent is scarce while some entry-level demand softens.
Fast Company look inside Shopify's decision to let engineers adopt AI tools without central approval, and how it changed expectations for output.
Why I recommend it: This is the emerging standard: AI fluency as a baseline job requirement, not a bonus. Plan your skills accordingly.
Glassdoor research on worker attitudes toward AI in 2026 — covering adoption, concerns, and what employees expect from employers.
Why I recommend it: A useful snapshot of public sentiment around AI at work. Helpful for coaching conversations about which skills matter and how to talk about AI on the job.
Harvard Business School AI Institute breakdown of new research on agentic AI: how autonomy and context integration shift the cost structure of knowledge work, expanding both productivity and the scope of what workers take on.
Why I recommend it: Read this before you assume AI just speeds up your current tasks. The useful takeaway for job seekers: agents lower the cost per step, so the valuable human skills become specifying goals clearly and verifying output. Practice describing outcomes, not keystrokes, and put "agent workflow design" language in your resume bullets.
