How to Respond to the Drop in Entry-Level AI Jobs
Entry-level jobs in AI-exposed fields have dropped 16% for 22-to-25-year-olds since late 2022, according to a Stanford study led by Erik Brynjolfsson. The roles disappearing fastest are the ones built around routine workflows: basic code generation, triage, entry-level customer service. But the contraction doesn't mean companies need fewer people overall. It means they need fewer people to carry out rote execution.
The historical parallel, as the Stanford research notes, is the introduction of digital spreadsheets in accounting. Software reduced repetitive manual tabulations but expanded the need for professionals who could interpret data, spot edge cases, and guide decisions. Today, you need to prove you can manage automated workflows, evaluate outputs for accuracy, and tie your work directly to operational goals. The old playbook of "prove you can complete repetitive tasks" is broken.
Rewrite your resume around outcomes, not tasks
Most entry-level resumes read like a list of chores. When employers can automate chore work, a list of chores makes you look replaceable. Fortune reported that corporate leaders are pausing early-career recruitment, leaving more than 4 million Gen Z individuals out of work, education, or training. As executive coach Bill Hoogterp explained in that report, companies now hire candidates who operate as self-directed problem-solvers.
Delete passive task descriptions. Remove phrases like "Responsible for handling support tickets" or "Wrote test scripts for QA." Anchor every bullet on results and tool oversight. Instead of "Drafted client support emails," write: "Resolved 45 escalated client inquiries weekly by refining scripted templates, reducing average resolution time while maintaining customer satisfaction." Instead of "Built internal dashboard," write: "Automated weekly performance reporting using internal APIs and automated scripts, cutting cross-team status syncs from two hours to thirty minutes."
If you have rough bullets from an internship or class project, Destava's AI career manager can rewrite them to put the business result first before you save them in the resume builder.
Sharpen your LinkedIn and build credibility before applying
Recruiters scanning early-career profiles look for signs you understand how a department actually functions. A bare list of coursework or software languages is no longer sufficient. Replace generic headlines like "Aspiring Software Engineer" with concrete focus areas: "Software Engineer | Systems Reliability & API Integration." Destava's LinkedIn profile feature can review your headline and About section line by line to ensure you communicate domain focus rather than student status.
In your experience section, describe edge cases you solved. Mention how you handled unexpected system downtime, resolved conflicting business requirements, or audited third-party software outputs. Comment thoughtfully on posts by engineering or product leaders in your niche. Destava's Comment Assist can draft structured observations that highlight your grasp of industry trends and bring visibility to your profile.
Keep your search organized. Log every contact, referral request, and interview stage so you consistently follow up within 48 hours of every conversation.
Ask workflow-focused questions in interviews
Early-career interviews often falter because applicants focus solely on what they want to learn. Managers hire people who immediately ease their daily workload. When asked about a past project, explain how you gathered context, what roadblock you hit, and how you resolved it before turning in the work. Talk openly about how you use software to double-check your work so your manager receives clean deliverables.
Probe how the team works and whether the role is designed for growth or vulnerable to immediate automation. Ask: "What tools does the team currently use to handle routine documentation and reporting, and how does this role review or build on those outputs?" Ask: "How does this team evaluate success for an entry-level contributor beyond ticket volume or raw output?" Ask: "What is one repetitive step in your team's weekly workflow that currently slows down delivery, and what would a junior hire need to take off your plate in the first 60 days?"
These questions prove you understand how modern teams operate and ensure you don't accept a role that could be phased out within months.