How is AI changing entry-level work?

Concern about junior work is not imaginary.

Stanford Digital Economy Lab research using payroll data found relative employment declines among workers aged 22–25 in highly AI-exposed occupations after widespread generative-AI adoption.

The authors present evidence consistent with an AI effect, not proof that every junior occupation or employer follows the same pattern.

Other forces still matter: economic cycles, experienced applicants moving down-market, outsourcing, local demand and changes in education.

Treat one aggregate percentage as a reason to investigate the target field, not a command to abandon it.

The useful question is narrower: which tasks used to train a beginner, which are now tool-assisted, and how does the employer replace that learning?

A role can survive while its first rung becomes harder to access.

Junior work has always included production and learning. Drafting, checking, documenting and handling routine cases teach the patterns needed for harder decisions.

If AI removes those repetitions, the employer needs a deliberate substitute: guided review, simulation, shadowing, rotated tasks or structured feedback.

Ask what a new hire owns after three, six and twelve months. Find out who reviews their work and whether they can see the original evidence behind an AI-assisted result.

“You will use AI from day one” is not a development plan.

Prefer roles where a beginner gains access to customers, systems, physical context, exceptions or accountable decisions over time.

Those experiences build domain judgement that cannot be acquired by generating more polished samples alone.

You cannot manufacture direct experience, but you can arrive with proof of task understanding.

Use a public dataset, course brief, volunteer project with permission or realistic synthetic case.

Show the standard, decisions, checks and feedback rather than a decorative final output.

Choose one task common to the target role and one task that sits closer to judgement.

An aspiring analyst might clean public data and then write a decision note explaining limitations.

A support candidate might classify requests and design escalation rules for ambiguous cases.

Get an informed review. A tutor, practitioner, open-source maintainer or supervisor can identify the assumptions a beginner misses.

Record the correction and what you would need to learn on the job.

A competitive direct title is not the only route into a field.

Consider apprenticeships, internships, project contracts, internal transfers, supplier roles, customer operations, professional associations and adjacent jobs that expose you to the same systems or users.

Compare the route on learning, pay, eligibility and progression. An adjacent role is useful only if it creates access to relevant tasks and relationships.

Do not accept indefinite low-paid work based on a vague promise that it might lead somewhere.

Use local labour-market evidence where possible.

National AI exposure cannot tell you whether a hospital, manufacturer, accountancy firm or public agency in your region is hiring and training beginners.

A beginner needs to understand enough of the task to detect failure. For selected practice runs, complete the outline, calculation or code without generation first.

Then compare the assisted process. This reveals what the tool changed and what knowledge you lack.

Ask the tool to critique or generate test cases after you have written a standard, not to replace the standard.

Keep original sources visible and explain the reasoning in your own words.

If you cannot reproduce the core step in an interview, the assistance has hidden rather than built skill.

Track where AI saves time and where review expands.

That record becomes useful interview evidence because it shows measured judgement rather than blind adoption or blanket refusal.