Entry level hiring needs a capability reset, not a bigger training catalog
SAP is betting that entry level work in the AI era depends more on judgment, trust and rapid learning. If that holds in adopting organizations, the bigger issue for CHROs and CLOs is not course volume, it is whether entry roles still build the capabilities the business will later need.
SAP says the new entry level job in the AI era depends on three things: judgment, the ability to build trust in work, and rapid learning. In the same SAP News Center piece, SAP says 69% of organizations acknowledge that AI is expanding employees' day to day responsibilities, and that more than half report upskilling and reskilling are not keeping pace with AI adoption.
That is a vendor view, not proof of a market wide shift. It still raises a practical question for organizations already putting AI into daily work: are they changing entry roles faster than they are changing the path that builds capability?
I would start with the work. If AI takes on more routine drafting, searching or synthesis, some junior employees may lose tasks that once helped them build context through repetition and close review. A business can then expect faster contribution from new hires while removing part of the route that used to build sound judgment and reliable execution. The risk is there.
This does not sit with L&D alone. The CHRO may own the workforce question, but talent acquisition, business unit leaders and the senior executive responsible for capability or workforce transformation also shape the answer through role design, hiring criteria and manager expectations. When entry roles widen before those conditions change, manager load can rise because judgment and trust are not confirmed by course completion. Time to proficiency can also become harder to predict when the role asks for stronger decisions earlier but approvals, supervision and work design still assume a narrower junior remit.
Check which tasks in a target entry role AI is changing now. Then check which of those tasks used to help people build judgment, credibility or learning speed. If those tasks are shrinking, decide what will replace that developmental value before changing hiring criteria or onboarding.
I would inspect the task mix first, then the approval path, then the manager review points. If the work no longer gives new hires enough chances to make bounded decisions, get feedback and earn trust, those parts of the operating system need attention before anyone asks for a broader AI training response. Learning may help, along with manager coaching or guided practice, but only after the work gives people a real way to build those capabilities.
The limits are straightforward. This is SAP's framing from the SAP News Center, and it does not establish long term performance outcomes or broad adoption across employers. Some organizations may see little change in entry level roles because their AI adoption is still limited. Even where AI use is growing, some controls should stay in place because they protect quality, compliance or separation of duties.
I would not rush to rewrite every graduate program. I would review where entry level work is already changing and ask whether the current role still gives people a credible path to build judgment and trusted execution. If the answer is no, redesign the work and decision path that develops those capabilities, and attach learning where it helps.
The signal I’m watching
Whether adopting organizations start changing entry level job design, assessment and manager oversight to create deliberate practice in judgment and trusted execution, rather than only adding AI skills training.
What would strengthen this signal
Comparable evidence from multiple employers showing that AI has removed or compressed junior developmental tasks, followed by measurable changes in hiring criteria, onboarding design, time to proficiency or manager load.
Sources
- SAP News Center — SAP(2026-11-05)