I watched a video of a graduation speaker pausing as a chorus of boos rolled across the lawn. I felt the tilt in the room—pride meeting panic—and I wanted you to see what that tilt means. You can hear the tension: it was louder than the applause.
On stages across the country, graduates booed mentions of AI.
You’ve seen the clips: Princeton students rejecting jacket designs, an Arizona ceremony where a name-reading AI skipped seniors, and speakers getting met with a long, sustained chorus of disapproval. Those moments didn’t come from nowhere. They are a pressure point—young people reacting to a future that looks less like opportunity and more like competition from code.
When you strip away the spectacle, the boos are shorthand for a list of grievances: lost entry-level work, creative labor treated as fungible, and a widening gap between those who own AI infrastructure and those who sell their labor. I’m not asking you to cheer or to jeer. I’m asking you to read the signals.
Why did graduates boo AI at commencements?
The short answer is fear and anger braided together. Students are seeing a labor market where internships disappear, writing and design gigs are automated, and recruiters talk about productivity gains while pay stagnates. That mix breeds a visceral reaction—less philosophical objection, more a defense of livelihoods and dignity.
At Microsoft, Brad Smith heard the boos and answered with an essay.
He wrote a long piece—about 3,000 words—positioning the reaction as a consumer preference rather than a political or economic demand. Smith invoked the 19th-century camera-versus-artist debate and urged graduates to accept progress while “speaking loudly for values.”
I read the essay as a practiced executive move: acknowledge the pain, reframe it as taste, and nudge people toward adaptation. The speech landed like a politely wrapped gift that smelled faintly of machine oil.
What did Brad Smith say about the boos?
Smith argued that people will decide when and how AI is used, likening the backlash to rejecting artificial fibers or products people don’t like. He claimed graduates recognize AI’s benefits but prefer limits. That’s a comforting narrative for industry leaders: change will be smooth because consumers will choose differently.
It’s important to remember context: another Microsoft executive’s public comment this year warned white-collar roles could be reshaped faster than many expect, and platforms from GitHub Copilot to ChatGPT are already part of hiring and workflow conversations. Framing the issue as mere preference sidesteps the economic realities.
On job boards and in dorm-room group chats, the stakes feel immediate.
Students aren’t debating metaphysics; they’re worrying about rent and resumes. When platforms like LinkedIn publish AI-driven productivity narratives and recruiters ask for AI fluency, the implicit message is: adapt or fade. That’s why organizing, collective bargaining, and policy work are surfacing as logical responses.
If you want a next step beyond boos, consider pressure on employers, clearer rules about attribution and ownership, and protections for early-career roles. The campus boos were a pressure valve blowing off steam, but valves can be redirected into levers of change.
I’m not calling for a techno-panicked retreat. I’m asking you—graduates, early-career workers, and bystanders—to be deliberate about what you accept and what you demand. Will you let the conversation be framed by executives and PR essays, or will you write the terms that govern the work you’ll do next?
So which side of that line are you on?