Как AI пузырь УНИЧТОЖИЛ найм в IT

Core claim

The so-called “AI bubble” is framed as a financial bubble rather than a straightforward productivity story. It is driven by:

• Loss-making buildout
• Heavy borrowing
• Inflated valuations

This framing is explicitly analogized to the dot-com bubble.

Business execution impact (HR/IT hiring)

The summary claims that “AI is killing programmers,” but the mechanism is not that programmers can no longer code. Instead, it’s mainly attributed to:

• Changes in hiring filters
• Automation of workflows
• Changes in company operating models

Frameworks and analogies used

Dot-com bubble comparison

The narrative follows dot-com bubble “logic”:

• Unprofitable startups raise money → inflated valuations → collapse risk
• “Picks and shovels” pattern: infrastructure vendors benefit disproportionately
  • (Example analogies include Cisco in the dot-com era; Nvidia here)

“Bubble mechanics” as a loop

A repeating cycle is described:

• Large profitable tech firms issue debt/bonds to fund AI spend
• Cloud purchase contracts reinforce the cycle
• Chip suppliers reinvest and expand supply of compute
• This sustains capital circulation and leverage

Key “bubble” mechanics & concrete examples (high-level)

Loss / sustainability stress

• Major AI companies are said to operate at significant losses (expenses far exceeding income)
• Example cited: xAI burns ~$1B/month

Debt + contract loop example (Microsoft / OpenAI / Nvidia)

The summary describes a circular funding pathway:

• Microsoft → OpenAI: invests $13B total
• OpenAI → Azure/cloud: a $250B cloud services contract is described
• OpenAI cloud spend:
  • $8.6B in first 9 months of 2025 on Azure
  • >$12B total since 2024
• Microsoft revenue share:
  • Microsoft receives ~20% of OpenAI revenue
  • Stated as $865M in first 3 quarters of 2025

Reinvestment path (as described):

• Nvidia sells chips to Microsoft
• Profits → bonds/debt → cloud contracts → buy more chips → repeat

Data center utilization & compute costs

• Data centers for AI are claimed to operate at ~80% occupancy
• Compute efficiency/ROI is questioned via an example:
  • If search costs $10, why not do it via standard Google?
• The implication is ROI uncertainty in parts of the stack

Valuation overheating

Nvidia is described as having very high valuation multiples:

• Mentioned multiple: ~45x
• Some companies: up to 200x

This is framed as euphoria/overheating with a likely future correction.

IT hiring impact: what’s said to change (“execution”)

1) “Layoffs due to AI writing code” as narrative vs reality

• Some companies are said to publicize layoffs as “replacement by AI”
• The summary suggests this may mask removal of excess headcount from earlier expansions

Example (described):

• A company blog/news story tied to former Twitter/X founders (context described as “Blog”)
• Claimed firing: ~4,000–6,000 employees

Interpretation:

• Companies allegedly couldn’t admit “downsizing” without stock impact
• They instead reframe as: “AI increases productivity; roles replaced.”

Analogy suggested:

• Similar framing may apply to Amazon/Microsoft, where earlier buildouts may have created “ballast” later cut.

2) Hiring shifts, not just “coding changes”

The claim: hiring declines because companies need a different skill mix, not because developers can’t code.

Examples of skill reorientation:

• Less demand for “classic” product teams (e.g., large sets of front-end/back-end/testers for small services)
• More demand for AI-adjacent capabilities and/or fast-funded “gold rush” domains
  • Example domains mentioned: blockchain, email automation, integrations

Result:

• “Old hiring died”
• Developers are expected to reposition toward higher-demand areas

3) ATS/HR automation reduces human screening

The summary claims HR is “lazy” (speaker phrasing) and that screening is largely automated:

• Resume parsing from recruiters/headhunters
• Automated analysis and decision-making by systems

Implication:

• Many candidates are filtered out without meaningful human review

4) “Bots interviewing bots”

The summary claims recruiting increasingly involves:

• Candidates using assistants for text interviews
• Delegating test tasks
• Automation assisting communication during calls

Resulting “process state”:

• Selection/negotiation is performed by automated agents rather than direct human evaluation

Practical takeaway described:

• Resumes must be formatted to pass bot filters
• The speaker implies there may be a need to “hack” ATS-like systems to improve compatibility

Actionable recommendations implied

Optimize resumes for automation

• Adapt resume content/format to increase acceptance by automated parsers and scoring systems

Prepare for bot-mediated recruiting

• Expect text-interview automation, delegated test tasks, and agent-driven screening

Re-skill / reposition

• Move away from “classic” low-demand service work toward AI-connected roles or whatever new “gold rush” domain is funded

Metrics / KPIs mentioned (as stated)

Financial scale / losses

• ~$1B/month burn (xAI)
• Qualitative claim: expenses exceed revenue by many times (no universal KPI given)

Contract / value loop figures

• Microsoft investment: $13B
• OpenAI cloud contract size: $250B
• OpenAI Azure spend:
  • $8.6B (first 9 months of 2025)
  • >$12B total since 2024
• Microsoft share of OpenAI revenue: ~20%
• Microsoft revenue from that share: $865M (first 3 quarters of 2025)

Data center / capacity

• Data centers “occupied” around ~80%

AI hiring narrative metric

• Layoff claim: ~4,000–6,000 employees (example described)

Presenter / source attribution

• Presenter: Roman Sakutin
  • Programmer with 15 years’ experience; owner of an accredited IT company
• Named external sources/companies mentioned:
  • Goldman Sachs (quoted executive)
  • Microsoft
  • OpenAI
  • Nvidia
  • Amazon
  • Anthropic
  • AMD
  • Google
  • xAI
  • Tesla/X context (Elon Musk referenced)
  • Cisco (dot-com analogy)
  • “Blog” / Twitter post-acquisition context (as described)
  • Amazon/Microsoft (as analogies)