July 13, 2026
July 13, 2026
Photo by Matheus Bertelli: https://www.pexels.com/photo/man-using-laptop-wit-chat-gpt-16094044/
The pressure on American companies to demonstrate AI capability has never been more intense. Boards are asking how their organizations are using AI. Investors want to know which teams are AI-enabled. CEOs are leading with it publicly: in earnings calls, at industry events, in the language they use to describe what makes their workforce competitive. Scroll through LinkedIn on any given morning and you can see it reflected back: organizations announcing AI-ready teams, AI-upskilled workforces, commitments to AI fluency as a defining capability.
The urgency behind all of that is legitimate. According to McKinsey’s 2025 State of AI report, nearly nine in 10 organizations now regularly use AI in their operations. The companies that cannot staff for that reality face a competitive disadvantage that builds quietly over time. When that pressure reaches the hiring function, the response is predictable: AI fluency becomes a formal requirement. Ninety-five percent of U.S. organizations have made it one, according to TestGorilla’s State of Hiring for AI Fluency 2026, a survey of 1,928 U.S. and U.K. hiring leaders.
Yet 59% of them still made a bad AI hire last year.
That number is worth sitting with. These are not organizations that ignored the problem. They cared enough to formalize the requirement, train their managers to screen for it and build it into their hiring process. The process still produced the wrong outcome more than half the time. Something upstream is broken.
Part of the explanation is that the U.S. is measuring something easier to detect than what actually matters. The same survey finds that 45% of U.S. employers are setting the AI fluency bar at basic tool awareness, knowing a tool exists and being able to name it in an interview. In the U.K., that figure is 29%. U.S. organizations report frequent AI-driven errors, at 33% versus 13% in the U.K. Those numbers move together for a reason.
Read the full article here: