Tech Firms Aren't Just Encouraging Their Workers To Use AI. They're Enforcing It.

Slashdot

by msmash

February 26, 2026

AI-Generated Deep Dive Summary

Tech companies are increasingly enforcing AI usage among employees, moving beyond mere encouragement to actively tracking adoption and linking it to performance reviews. Giants like Google, Meta, Amazon, Microsoft, and Salesforce are leading this trend, with some even integrating AI usage metrics into employee evaluations for the first time. For instance, Google now factors AI tool usage into software engineer reviews, while Meta’s new performance system tracks how much code engineers write with AI assistance. Amazon Web Services (AWS) managers also monitor individual AI tool usage through dashboards, considering this when assessing promotions. These measures signal a shift toward prioritizing efficiency and productivity gains driven by AI. The trend is further evidenced by growing expectations from managers: 42% of tech workers report that their direct supervisors now expect daily use of AI tools, up from 32% just eight months prior, according to AI consulting firm Section. Companies like Autodesk are taking it a step further, with CEO Andrew Anagnost acknowledging that employees using initially blocked coding tools like Cursor without permission have faced warnings. He emphasized that those resistant to AI adoption “probably won’t survive long term,” underscoring the industry’s accelerating embrace of AI. This shift matters because it reflects a broader trend across the tech sector: AI is no longer optional but essential for staying competitive. Companies are leveraging AI tools to enhance efficiency, improve output quality, and maintain a competitive edge in an increasingly fast-paced digital landscape. Employees who adapt to these changes are likely to thrive, while those resistant risk falling behind. As more organizations adopt similar policies, the ability to effectively use AI tools will become a critical skill for tech professionals

Verticals

tech

Originally published on Slashdot on 2/26/2026