Tech Industry on Shane's Personal Blog

Chapter 2: The Comfortable Cage

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 2: The Comfortable Cage

Three years earlier.

The badge beeps. Green light. David walks through TechCorp’s glass doors for the thousandth time.

9:47 AM. Seventeen minutes late. No one cares. The engineering floor doesn’t start until ten—“flexible hours,” they call it.

He looks like everyone else here. Button-down untucked, dark circles from scrolling too late, jeans that cost more than a week of groceries used to. The elevator reflects him back: indistinguishable.

Seventh floor. Open-plan. Long wooden tables, expensive coffee, kombucha on tap. Sarah from DevOps waves. He waves back. Everyone is nice here.

His monitor wakes. Three Slack channels. Two calendar invites. A pull request waiting for review.

He wrote that code three days ago. Six hours of work. A feature that lets users customize dashboard widgets. The analytics say 2% of users will touch it. But a competitor has it, so they need it too.

David reviews. Approves. Merges.

Somewhere, a server updates. A feature no one needs joins millions of others.

Alex texts: Lunch today?

David tries Thursday. Alex is in Seattle. Next week, then. Both know it won’t happen.

Slack: “Great Q3 launch! Hit 97% OKRs!”

Nights and weekends for that. Pizza boxes. “Crunch time.” They shipped an onboarding flow nobody asked for, backend tweaks nobody noticed.

His mother asks about houses. Will look this weekend, he lies. This weekend: sleep, takeout, the novel he never starts.

Noon. Sprint planning. “Prioritize Q4 roadmap. Discuss technical debt.”

Technical debt—code built fast and broken, never fixed. Just pile more features on top. It works. Makes money. Stock goes up. Everyone gets bonuses.

Kevin pulls him into a conference room. “You’re getting promoted. Senior Engineer. 15% raise.”

David’s stomach tightens.

Fifteen percent. Down payment in eighteen months. Expensive coffee without guilt. Parents proud. And harder to leave.

“Thanks,” he says.

“You’ll interview junior engineers too. We’re scaling.”

David wonders if he’ll recognize himself in them. The ones who think shipping code will feel different than college. Who think “making an impact” means more than optimizing conversion rates.

Through the glass wall: eighty people at desks. Headphones. Pair-programming. Laughter from the kitchen.

Good people. Smart people. Building someone else’s vision for salary and benefits.

David opens his Notes app. Past grocery lists to a document from two years ago: “Ideas.”

Thirty-seven entries. Startup concepts. Problems nobody’s solving. The last one from six months ago.

He hasn’t added anything since.

Sprint planning in fifteen minutes. He closes the app. Straightens his shirt.

The city sprawls below. How many people calculating the exact dollar amount that would make them stay?

How many winning?

At his desk: Jira tickets. “Implement A/B test for button colors.” “Refactor authentication module.” “Add logging.”

Necessary. Reasonable. Uninspiring.

He accepts them all. Joins the planning call. Camera off. Says just enough: “Sounds good.” “I can take that.” “Two days seems reasonable.”

For six hours he writes code. Tests. Refactors. The world falls away.

This is why he became an engineer. Not the meetings. The craft. Making something work beautifully.

Even if the thing being built doesn’t matter.

October becomes November.

The promotion is official. David’s new title appears in his email signature: Senior Software Engineer. His salary increases by $18,000.

His mother calls. “Your aunt heard about your promotion. She’s very proud.”

David sits in his apartment—the nice one he moved to six months ago. Floor-to-ceiling windows. In-unit washer-dryer. The kitchen has granite countertops he’s never cooked on.

“That’s nice,” he says.

“You don’t sound excited.”

“I am. Just tired.”

“You’re always tired.” Her voice shifts. Concerned. “Are you taking care of yourself?”

He looks around. Takeout containers on the counter from the past three days. He meant to throw them out. The apartment smells faintly of old Thai food and recycled air. When did he last open a window?

“Yeah, Mom. I’m fine.”

They talk for seven more minutes. She tells him about his cousin’s wedding. His father’s new glasses. The neighbor’s dog that barks at 6 AM.

David says “uh-huh” at the right intervals. When they hang up, he can’t remember a single detail.

November becomes December.

Holiday party at TechCorp. Open bar, catered food, a DJ playing music nobody dances to.

David stands near the appetizer table with Sarah and two other engineers. They’re talking about the latest reorg. Who got promoted. Who didn’t. The politics of it.

“Did you hear Chen applied for Staff?” Sarah says. “Third time.”

“He’s not going to get it,” Tom says. “Not political enough.”

They talk about Chen like he’s not a real person. Just a piece in the game. David eats a spring roll. It’s good. He eats another.

Kevin—his manager—walks over. Slightly drunk. Friendly. “David! There’s my senior engineer. How’s the new salary treating you?”

“Good. Thanks again.”

“You earned it, man. That authentication refactor saved us three weeks. Leadership noticed.”

Leadership noticed. David wonders who “leadership” is. Faceless VPs who read metrics. Who care about quarterly numbers. Who laid off eighty people last year to hit profit targets.

“Glad to help,” David says.

Kevin leans closer. Whispers conspiratorially. “Between us—I’m pushing for you to interview lead engineer candidates next year. Get you into the hiring pipeline. Good for your career.”

His career. The ladder. The next rung.

David nods. Smiles. Says thank you.

Kevin claps him on the shoulder and wanders off.

Sarah rolls her eyes. “Lead engineer interviews. Great, more meetings.”

“At least the pay bump is good,” Tom says.

They talk about pay for ten more minutes. RSU vesting schedules. 401k matching. Health insurance deductibles.

David excuses himself. Goes to the bathroom. Stares at himself in the mirror.

He’s wearing the same button-down he wore to his college graduation. It fit better then. His face looks older. Not in a good way. Tired. The fluorescent lights make his skin look gray.

When did he last feel excited about anything?

The question arrives without warning. He can’t answer it.

David washes his hands. The soap smells like fake lavender. Returns to the party. Stays another hour because leaving early would be noticed.

Drives home at 9 PM. The city is decorated for Christmas. Lights strung across buildings. Inflatable Santas. Everywhere, the performance of joy.

December becomes January.

David’s calendar fills. Q1 planning. OKR setting. One-on-ones with Kevin. Tech talks he doesn’t care about. An all-hands where the CEO talks about “exciting growth opportunities” while the stock price declines.

On January 17th, a Tuesday, something shifts.

It’s not dramatic. No lightning bolt. Just a moment that cracks something.

David is in a conference room. Fourth floor. Windows overlooking the parking lot. There are seven people in the meeting. The topic: whether to deprecate a legacy API that three customers still use.

The product manager—Jen, nice enough—argues they should keep it. “Three customers is three customers. We can’t just abandon them.”

The engineering director—Michael, not nice—argues they should sunset it. “It’s costing us maintenance hours. Three customers don’t justify the overhead.”

They debate for thirty minutes. Data gets pulled up. Spreadsheets. Customer lifetime value calculations. Engineering hour costs.

David sits quietly. Listening. Watching.

At some point, Jen says: “But what about the users? Don’t we have a responsibility?”

Michael doesn’t even pause. “Our responsibility is to the bottom line. That’s how we stay in business.”

The room nods. It’s the right answer. The practical answer.

David feels something cold settle in his chest.

He thinks about the three customers. Real people somewhere. Using this API in their products. Trusting that it’ll keep working. Now about to be deprecated because the spreadsheet says they’re not worth it.

The meeting ends. They vote to sunset the API. Jen will send the deprecation notice. Engineering will archive the code. The three customers will get six months to migrate.

David walks back to his desk. Sits down. Opens the code for the API they just voted to kill.

It’s not elegant code. Written five years ago by someone who left the company. But it works. And someone is using it.

He closes the file.

Opens his Notes app. Scrolls to “Ideas.”

Thirty-seven entries. He hasn’t looked at this in—what? Four months? Five?

The last entry is from September. Six months ago. “Micro-learning platform - adaptive flashcards.”

He reads through them. Some are stupid. Some might be good. All of them gathering dust.

David closes the app.

Checks his email. Seventeen unread. He processes them mechanically. Yes. No. Will circle back. Looks good.

At 4:47 PM, his mother texts: Your cousin is pregnant. You’re going to be a… second cousin?

David types back: Great. Congratulations to her.

But he thinks: I’m 28. My cousin is building a family. Alex just proposed to his girlfriend. Sarah is buying a house.

And David is—what? Comfortable. Successful. Moving up the ladder.

To where?

He doesn’t add a thirty-eighth idea. Doesn’t delete the thirty-seven. Just closes the app.

The screen goes dark. His reflection stares back.

He looks tired.

January becomes February. February becomes March.

David’s calendar stays full. The meetings blur together. Planning. Retrospectives. Design reviews. Coffee chats with junior engineers who think working here is exciting.

He does his job well. Ships code. Reviews PRs. Participates in discussions. Says the right things.

But somewhere—quietly, invisibly—something is dying.

It’s the part of him that once believed this work mattered. That building software was building the future. That solving technical problems was changing the world.

Now he knows: most problems aren’t worth solving. Most features aren’t worth building. Most meetings aren’t worth having.

But the salary is good. The benefits are good. His mother is proud. His father is relieved.

So David stays.

The golden handcuffs, tightening one day at a time.

On March 15th, he goes to lunch with a college friend. Marcus—different Marcus than high school. They meet at a Thai place downtown.

Marcus works at a startup. Terrible pay, long hours, uncertainty. He complains about it for twenty minutes. The broken deployment pipeline. The founder who keeps changing direction. The runway down to four months.

“But,” Marcus says, fork hovering over his pad thai, “at least I care about what we’re building. You know? Like, it might fail. Probably will. But I’d rather fail at something I care about than succeed at something I don’t.”

He looks at David. “You get it, right?”

David chews slowly. Swallows. “Yeah.”

But he doesn’t get it anymore. Or he does, and that’s worse.

When lunch ends, Marcus pays for both of them. “You can get next time. I know you’re probably saving for a house or something.”

David doesn’t correct him.

Walks back to the office. The badge beeps. Green light. The elevator to the seventh floor.

At his desk, he opens his Notes app without meaning to. Muscle memory. The list of thirty-seven ideas.

He hovers over the ”+” button.

Thinks about Marcus. The startup that might fail. The certainty that failing matters if you care about what you’re failing at.

Thinks about the API they deprecated. The three customers who didn’t matter enough.

Thinks about sixteen-year-old David in a library. Hearing Jobs’s voice. Thinking there was another way to live.

He doesn’t add an idea.

Doesn’t delete them either.

Just closes the app. Returns to Jira. Picks up the next ticket.

At 7 PM he’s still at his desk. Most people have gone home. The office is quiet. Just the hum of climate control and distant keyboard clicks.

David saves his work. Closes his laptop. Stands up.

His lower back aches. How many hours did he sit today? Eight? Nine?

He walks to the window. The city sprawls below. March evening. Not quite spring. The light is fading.

Jobs’s voice echoes from ten years ago: Don’t let the noise of others’ opinions drown out your own inner voice.

David wonders if he still has an inner voice. Or if he traded it somewhere along the way. For salary. For security. For the look of relief on his father’s face when David said he got promoted.

He stands at the window for a long time.

The city below pulses with life. People heading home. To families. To partners. To lives that make sense.

David feels nothing about that. Not envy. Not contentment. Just—distance.

Like he’s watching through glass. Separate. Safe. Numb.

This is the cage. Not cruel. Just comfortable.

The kind you don’t notice until you’ve been inside it for years.

David picks up his laptop bag. Badges out. The badge beeps. Green light. A thousand times. Ten thousand.

How many more times will he hear that sound?

He doesn’t know.

But he knows he can’t stop. Not yet. The mortgage his parents want him to get. The wife they want him to find. The life they want him to build.

All requiring this. The steady paycheck. The career advancement. The responsible choice.

David drives home. Orders delivery. Thai food, ironically. Eats in front of his laptop.

The Notes app is closed. The thirty-seven ideas are sleeping.

Tomorrow he’ll wake up. Badge in. Do it again.

The comfortable cage.

Safe.

Shrinking.

Killing him slowly.

End of Chapter 2

AI and the Zero-Sum Fallacy: Why Tech CEOs' AI Talk Might Mislead You

Sun, 09 Nov 2025 00:00:00 GMT

The Hype: Augmenting Humans, Not Replacing Them

If you listen to most tech CEOs, AI is just a helpful sidekick. Google’s Sundar Pichai insists “The future of AI is not about replacing humans, it’s about augmenting human capabilities.”¹ Microsoft’s Satya Nadella claims “AI is the defining technology of our times… It’s augmenting human ingenuity and helping us solve some of society’s most pressing challenges.”² In this narrative, AI handles drudge work while humans focus on higher-value tasks—a win-win scenario.

This optimism is comforting. Nobody wants to believe their job could vanish overnight. But is this the full story? Recent candor from AI insiders and CEOs themselves reveals a much starker reality.

The Quiet Part Out Loud: AI Will Replace Jobs, Fast

Behind closed doors—and increasingly in public—tech leaders are admitting that AI will eliminate many jobs. “AI could wipe out half of all entry-level white-collar jobs — and spike unemployment to 10–20% in the next one to five years,” warns Dario Amodei, CEO of Anthropic.³ This isn’t a tech skeptic talking—it’s from someone building the most advanced AI. He’s urged fellow CEOs to stop “sugar-coating” what’s coming: “We, as the producers of this technology, have a duty and an obligation to be honest about what is coming.”⁴

Geoffrey Hinton, AI pioneer and Nobel Prize winner often called the “Godfather of AI,” is even more direct. When asked if massive AI investments can pay off without eliminating jobs, Hinton replied: “I believe that it can’t. I believe that to make money you’re going to have to replace human labor… the big companies are betting on it causing massive job replacement by AI, because that’s where the big money is going to be.”⁵

This isn’t just theory. The cuts have already begun:

Amazon’s Andy Jassy cut 14,000 corporate jobs while telling employees in an internal memo: “We expect that this will reduce our total corporate workforce as we get efficiency gains from using AI extensively across the company.”⁶ He pushed for “scrappier teams”—corporate-speak for fewer people doing more work.

Salesforce’s Marc Benioff slashed his customer support team from 9,000 to 5,000 people—a 44% cut. His explanation? “I need less heads.”⁷ The result: a 17% cost reduction that he celebrated publicly.

Klarna’s Sebastian Siemiatkowski reduced his workforce by 40%, from 5,000 to 3,000 employees, through a hiring freeze and attrition. His reasoning: “I am of the opinion that AI can already do all of the jobs that we as humans do. It’s just a question of how we apply it and use it.”⁸ He warns this displacement is “unavoidable” and could trigger a recession.⁹

IBM’s Arvind Krishna announced in 2023 that 30% of back-office roles—roughly 7,800 jobs—would be replaced by AI over five years, saying: “I could easily see 30% of that getting replaced by AI and automation.”¹⁰

Meta’s Mark Zuckerberg announced 10,000 job cuts in his “Year of Efficiency” memo, explicitly stating: “Part of our work will involve removing jobs — and that will be in service of both building a leaner, more technical company.”¹¹

And it’s not just tech. JPMorgan’s CEO Jamie Dimon warned that those who don’t think job losses from AI are inevitable should “stop sticking their head in the sand.”¹²

One tech CEO emailed his staff bluntly: “It does not matter if you are a programmer, designer, project manager, data scientist, lawyer, customer support rep, salesperson, or a finance person — AI is coming for you.”¹³

Why Are CEOs So Eager to Replace Humans?

If augmenting humans is so great, why do companies act like AI is a zero-sum game—either the bot or the human? The answer is cold economics. For a gigantic corporation under pressure to increase profits, AI presents an irresistible way to cut costs. Unlike humans, software doesn’t take salaries, demand benefits, or quit. Once running, each automated role drops straight to the bottom line.

Geoffrey Hinton explicitly calls out this profit motive: “What’s actually going to happen is rich people are going to use AI to replace workers. It’s going to create massive unemployment and a huge rise in profits. It will make a few people much richer and most people poorer.”¹⁴ He emphasizes that “The problem isn’t AI — it’s the way society is organized.”¹⁵

There’s brutal short-term logic at play. Replacing people with AI happens faster than retraining an entire workforce. Investors reward quarterly profit jumps, not nebulous promises of future innovation. Salesforce’s 44% support staff reduction and 17% cost savings is exactly the kind of metric Wall Street loves. IBM pausing hiring for 7,800 roles? That’s immediate shareholder value.

Dario Amodei warns that companies will “stop backfilling jobs, then replace [workers] with automated alternatives” and “the public only realizes it when it’s too late.”¹⁶ This could “unfold almost overnight” as CEOs suddenly “see the savings.”¹⁷

Crucially, though, this is the CEOs’ reality—it doesn’t have to be yours. Big Tech may use AI to cut labor, but individuals have a completely different playing field.

Breaking the Zero-Sum Mindset: More Pie, New Jobs

It’s easy to despair when a CEO says “AI is coming for you.” But history suggests otherwise. New technologies often create new kinds of work even as they obsolete old tasks. The lamplighters lost their jobs when electric lights came, but we gained electricians, photographers, software engineers, and countless roles no one in the gaslight era could envision.

Many experts believe AI will be similar—shifting jobs rather than annihilating them. A Harvard Business Review piece captures it perfectly: “AI won’t replace humans — but humans with AI will replace humans without AI.”¹⁸ Those who learn to leverage AI will outcompete those who don’t.

Instead of viewing AI as a rival taking a finite slice of pie, individuals can see it as a chance to grow the pie or bake a new kind. There are countless problems and unmet needs that AI can help tackle if we’re creative. With AI, a small startup (or ambitious individual) can attempt projects that used to require huge teams. New products, services, and industries can sprout.

The mistake is responding like a deer in headlights, assuming the game is over. Your advantage as a human is the ability to adapt and leverage new tools. Rather than thinking like an Amazon executive managing a fixed workforce, think like an entrepreneur. How can you use AI to amplify your skills or break into new areas?

Your Career Strategy in the AI Era

Concretely, this means:

Upskill in AI literacy. Become the person who knows how to get the best out of new tools. Don’t wait for your employer to train you—they might eliminate your role first.
Shift into uniquely human domains. Leadership, complex problem-solving, interpersonal communication, creativity—these remain difficult for AI. Hinton notes that physical and creative jobs may be safer for longer as machines still struggle there.¹⁹
Consider entrepreneurship. Create your own job by starting a venture that harnesses AI in novel ways. The world of AI is full of opportunity; it’s not just the domain of trillion-dollar companies.
Demand better policies. As Hinton emphasizes, “The problem is not ultimately due to AI itself… It’s due to how we structure our society and our economy.”²⁰ If we collectively deploy AI purely to pad profits, we’ll get a harsher economy. But if we use it to augment human potential, we get a different outcome. This requires policy choices (education, job training, safety nets) and individual choices (continuous learning, openness to change).

Amodei is right that “you can’t just step in front of the train and stop it.” However, “the only move that’s going to work is steering the train” in a direction that benefits as many people as possible.²¹

Conclusion: Filter CEO Words Through Your Own Reality

Tech CEOs command attention, but their reality is not yours. When a CEO speaks about AI, they’re often thinking about maximizing efficiency and profits in the next few quarters. That leads to a pessimistic, zero-sum view on jobs—because for them, in a saturated market, maybe it is somewhat zero-sum.

But as an individual, your career is not a closed system like a Fortune 500 balance sheet. Your potential is not capped by last year’s revenue or investor expectations. There are infinite problems to solve and new ventures to build if you stay curious and proactive.

The numbers are sobering: Salesforce cut 4,000 jobs. Klarna reduced headcount by 40%. IBM plans to replace 7,800 roles. Amazon shed 14,000 workers. These aren’t predictions—they’re already happening. But they don’t have to spell doom for you.

By viewing AI as augmentation and focusing on uniquely human value you can bring (often with AI’s help), you turn a zero-sum game into a new game entirely. The CEOs might manage the trains, but you’re free to lay new tracks.

Don’t let the CEO of Amazon or Klarna define the limits of your ambition. The best way to prove the gloomy forecasts wrong is to not play by the old rules. Don’t just take the CEO’s word for what AI will do—decide for yourself what you will do with AI. That mindset shift is where real job security in the age of AI will come from.

Sources

Sundar Pichai, CEO, Google/Alphabet. “15 Quotes on the Future of AI,” TIME, https://time.com/partner-article/7279245/15-quotes-on-the-future-of-ai/ ↩
Satya Nadella, CEO, Microsoft. “Microsoft CEO Satya Nadella Quotes,” Supply Chain Today, https://www.supplychaintoday.com/microsoft-ceo-satya-nadella-quotes/ ↩
Dario Amodei, CEO, Anthropic. Interview with Axios, May 28, 2025. “AI jobs danger: Sleepwalking into a white-collar bloodbath,” Axios, https://www.axios.com/2025/05/28/ai-jobs-white-collar-unemployment-anthropic ↩
Dario Amodei, CEO, Anthropic. “Why this leading AI CEO is warning the tech could cause mass unemployment,” CNN Business, May 29, 2025, https://www.cnn.com/2025/05/29/tech/ai-anthropic-ceo-dario-amodei-unemployment ↩
Geoffrey Hinton, Nobel Prize winner (2024 Physics), Professor Emeritus, University of Toronto, former Google VP and Engineering Fellow. Bloomberg TV’s “Wall Street Week,” November 1, 2025. “‘Godfather of AI’ says tech giants can’t profit from their astronomical investments unless human labor is replaced,” Fortune, https://fortune.com/2025/11/01/geoffrey-hinton-godfather-of-ai-investment-tech-company-profits-human-labor-replacement/ ↩
Andy Jassy, CEO, Amazon. Internal memo to employees, June 17, 2025. “Amazon says it will reduce its workforce as AI replaces human employees,” CNN Business, https://www.cnn.com/2025/06/17/business/amazon-ai-human-employees-jobs ↩
Marc Benioff, CEO, Salesforce. The Logan Bartlett Show Podcast, September 2, 2025. “Salesforce CEO Marc Benioff says AI has already replaced 4,000 jobs,” San Francisco Chronicle, https://www.sfchronicle.com/tech/article/salesforce-ai-job-cuts-benioff-21025920.php ↩
Sebastian Siemiatkowski, CEO, Klarna. Bloomberg TV interview, December 2024. “Klarna’s CEO says it stopped hiring thanks to AI but still advertises many open positions,” TechCrunch, https://techcrunch.com/2024/12/14/klarnas-ceo-says-it-stopped-hiring-thanks-to-ai-but-still-advertises-many-open-positions/ ↩
Sebastian Siemiatkowski, CEO, Klarna. The Times Tech Podcast, June 2025. “Klarna CEO predicts AI-driven job displacement will cause a recession,” Fortune Europe, https://fortune.com/europe/2025/06/09/bnpl-loans-klarna-ceo-predicts-ai-recession/ ↩
Arvind Krishna, CEO, IBM. Bloomberg interview, May 1, 2023. “IBM’s CEO expects A.I. to be so good at back office work that he plans to pause hiring humans for those jobs,” Fortune, https://fortune.com/2023/05/01/ibm-ceo-ai-artificial-intelligence-back-office-jobs-pause-hiring/ ↩
Mark Zuckerberg, CEO, Meta. Official company memo, March 14, 2023. “Update on Meta’s Year of Efficiency,” Meta Official Blog, https://about.fb.com/news/2023/03/mark-zuckerberg-meta-year-of-efficiency/ ↩
Jamie Dimon, CEO & Chairman, JPMorgan Chase. Fortune’s Most Powerful Women Summit, October 2025. “JPMorgan CEO Jamie Dimon says people who don’t think job losses due to AI are inevitable, ‘should stop sticking their head in the sand’,” Fortune, https://fortune.com/2025/10/15/jpmorgan-ceo-jamie-dimon-ai-job-losses/ ↩
Eric Vaughan, CEO, IgniteTech. Fortune magazine interview, August 17, 2025. “This CEO laid off nearly 80% of his staff because they refused to adopt AI fast enough. 2 years later, he says he’d do it again,” Fortune, https://fortune.com/2025/08/17/ceo-laid-off-80-percent-workforce-ai-sabotage/ ↩
Geoffrey Hinton. Financial Times interview, September 2025. “Geoffrey Hinton says AI will cause massive unemployment and send profits soaring,” Fortune, https://fortune.com/2025/09/06/godfather-of-ai-geoffrey-hinton-massive-unemployment-soaring-profits-capitalist-system/ ↩
Geoffrey Hinton. Various interviews, 2025. “‘Elon Musk will get richer, many others will be unemployed’: ‘Godfather of AI’ Geoffrey Hinton warns of dark future,” The Economic Times, https://economictimes.indiatimes.com/news/international/global-trends/elon-musk-will-get-richer-many-others-will-be-unemployed-godfather-of-ai-geoffrey-hinton-warns-of-dark-future/articleshow/125077848.cms ↩
Dario Amodei, CEO, Anthropic. Axios interview, May 28, 2025. https://www.axios.com/2025/05/28/ai-jobs-white-collar-unemployment-anthropic ↩
Dario Amodei, CEO, Anthropic. “AI Could Wipe Out 50% of Entry-Level White Collar Jobs,” Marketing AI Institute, https://www.marketingaiinstitute.com/blog/dario-amodei-ai-entry-level-jobs ↩
“AI Won’t Replace Humans - But Humans With AI Will Replace Humans Without AI,” Harvard Business Review, August 2023, https://hbr.org/2023/08/ai-wont-replace-humans-but-humans-with-ai-will-replace-humans-without-ai ↩
Geoffrey Hinton. Diary of a CEO podcast, June 2025. “Automation will replace white-collar jobs; manual trades safe: Father of AI,” Business Standard, https://www.business-standard.com/technology/tech-news/ai-job-loss-geoffrey-hinton-automation-fears-125061701046_1.html ↩
Geoffrey Hinton. Various interviews, 2025. The Economic Times, https://economictimes.indiatimes.com/news/international/global-trends/elon-musk-will-get-richer-many-others-will-be-unemployed-godfather-of-ai-geoffrey-hinton-warns-of-dark-future/articleshow/125077848.cms ↩
Dario Amodei, CEO, Anthropic. “Anthropic CEO thinks half of entry-level roles will be eliminated by 2030,” UNLEASH, https://www.unleash.ai/artificial-intelligence/anthropic-ceo-thinks-half-of-entry-level-roles-will-be-eliminated-by-2030-how-can-hr-turn-this-fear-into-possibility/ ↩

Tech Industry on Shane's Personal Blog

Chapter 2: The Comfortable Cage

Chapter 2: The Comfortable Cage

AI and the Zero-Sum Fallacy: Why Tech CEOs' AI Talk Might Mislead You

The Hype: Augmenting Humans, Not Replacing Them

The Quiet Part Out Loud: AI Will Replace Jobs, Fast

Why Are CEOs So Eager to Replace Humans?

Breaking the Zero-Sum Mindset: More Pie, New Jobs

Your Career Strategy in the AI Era

Conclusion: Filter CEO Words Through Your Own Reality

Sources

Footnotes