AT&T and ServiceNow each posted software-engineering openings that explicitly center on “AI-native” work on September 15, 2026. AT&T advertised a Senior AI-Native Software Engineer role in Alpharetta, Georgia, while ServiceNow posted a Senior Staff AI-Native Software Engineer – Agentic Systems role in San Francisco.
The AT&T posting says the role requires experience with AI-enabled application development, agentic workflows, Large Language Models, and agent frameworks. It also says the job will build production-grade applications, APIs, and intelligent workflow automations to transform how work gets done across the enterprise.
ServiceNow says the team is building agentic AI and enterprise-scale search systems and describes itself as building an “AI-native culture.” Its posting says the role involves designing and operating production-grade agentic AI systems, including multi-agent orchestration, tool use, planning loops, memory, and failure recovery.
What the postings say
AT&T’s listing is titled “AI-Native Software Engineer, Senior” and gives Alpharetta, Georgia as the location. The supplied source identifies the posting date as 09/15/2026. ServiceNow’s listing is titled “Senior Staff AI-Native Software Engineer – Agentic Systems” and is located in San Francisco. The supplied source identifies that posting as September 15, 2026.
The supplied sources support those job details and requirements. They do not state whether the roles replace other openings, whether they are part of a broader hiring change, or any other companywide staffing plan.
Why this matters
The postings show AI-specific language appearing directly in engineering job titles and requirements. AT&T centers the job on production-grade software and workflow automation, while ServiceNow centers the job on agentic AI systems and enterprise-scale search.
The research bundle also says the immediate hiring impact is a tilt toward AI-enabled application development, agent orchestration, and LLM experience. For software engineers, that could matter for candidates whose experience already includes production AI work; however, the supplied sources do not establish a universal hiring standard across the sector.
What to watch next
What to watch is whether other employers begin using the same “AI-native” and “agentic” language in posted engineering roles, and whether future listings preserve the same mix of requirements. The supplied sources do not identify any timetable, policy change, or downstream staffing plan beyond these two postings.
For now, the concrete evidence is narrow: AT&T and ServiceNow each posted one AI-native engineering role, each posting ties the work to production systems, and each posting uses specific language about LLMs or agentic AI.