
What happened
Among respondents at companies with 1,001+ employees, 50.0% said AI is used company-wide, and 46.0% flagged AI-generated code being used without understanding its intent as the top risk.
Why it matters
The survey suggests adoption is outrunning governance, as 33.3% of large-company respondents said they cannot tell whether AI code was checked, and 55.0% said AI-related defects exceed what IT can handle, so quality gaps may go unseen.
What to watch
The outcome hinges on whether firms add their own safeguards: 56.0% of large-firm respondents most wanted tools that check AI-code quality and vulnerabilities, versus 18.0% wanting company-wide AI security and governance guidelines.
WHO IT HITSIT and engineering staff at large enterprises are the clear audience here, since they own the code review, security and governance decisions the survey shows are lagging behind adoption. Non-engineer staff who now build tools with AI are the other group whose output these safeguards would cover.
Summaries like this, in your inbox every morning.
The survey lands at a point where AI tools have moved from experiments into day-to-day development. Among employees at large firms, half now report company-wide AI use, and their non-engineer colleagues have joined in: 65.0% of large-company respondents said their company's non-engineers are using AI tools for development, against 40.0% overall. That spread is exactly why the survey's answers about checking AI output carry weight — code now reaches the whole company, but the survey indicates review has not kept pace. Only 9.1% of respondents at firms with 5,001 or more employees picked company-wide AI security and governance rules as a needed measure, far below the 38.2% at firms with 101 to 1,000 employees, even though the larger firms report the deeper governance gaps in this survey.
Where engineers sit shapes the answers. Among IT department respondents, 64.3% wanted cost-visibility and management tooling, well above the overall figure, and 41.4% chose it as a second priority, 15.4 points ahead of non-IT respondents. Non-IT respondents instead leaned toward ready-made standards for AI code development at 24.7%, versus 13.8% for IT staff. The free-comment section points to why: one respondent said AI was introduced with the instruction that final checks stay with humans, and another described a system that became an error after an unexpected event exceeded what AI could handle.
The open question is whether large firms turn these findings into internal rules. The survey suggests the pressure is real, since 55.0% of those using AI in development said AI-related defects and issues exceed what IT can handle. What remains unclear is whether the safeguards arrive through the code-checking tools most respondents asked for, or through the governance guidelines that smaller firms favored more. For IT staff at large companies, the practical test will be whether they can combine usage and cost visibility with a repeatable way to check AI-generated code.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
HBM is approaching half the cost of a GPU-HBM CoWoS package, prompting the question of whether memory remains…

DeepSeek is bringing more of the software it uses to develop its AI models to Huawei Technologies' Ascend 950…

Nvidia released the Open Agent Safety Platform on September 28, days after CEO Jensen Huang called warnings fr…

Oracle invoked "force majeure" to delay payment on its Project Jupiter data center, and its 2056 bonds then tr…

McDonald’s is increasingly using AI to guide menu prices in the U.S

OpenAI launched Dots — agents on GPT-6 Astra, each running on its own cloud computer and connecting to 4,000+…
