Author: Nebula Walker Date: 28JUL2026 MYTHOGEN ENGINE (mythogenengine.com)
📌 Layoffs and record profits happening simultaneously. AI isn't the cause; it's the license. One exit, two sales: upstream to the hand pushing the button, downstream to the people under the button.
The Efficiency Trap · Sequel: You Thought You Won
Prologue: Xiaolin's Three Lessons
Act One
The day the senior engineer left, the office was unnervingly quiet.
Xiaolin remembered what the announcement said: "pursuing other career plans." No farewell party, no handover documents. A man who had been there for fourteen years cleared out his desk in a single afternoon.
The signs had been there all along—only no one had been willing to read them. Over six months, the senior's projects were reassigned one by one. His name quietly vanished from cross-departmental meeting invitations. When a production incident occurred—a decision that had never been in his hands—his name appeared in the responsibility column of the postmortem report. He appealed once. Then he never appealed again.
A month after the senior left, Xiaolin was promoted. His annual salary jumped from two million to three million. His manager clapped him on the shoulder and said: "The company believes in you. Young man, this is your era."
That evening, Xiaolin took his cohort out for dinner. He felt like he'd won. What he didn't know was that the person who'd held the position before him had earned ten million a year. The company had filled a ten-million hole with three million, netting seven million in savings on paper—and he was the name attached to that saving.
Act Two
After taking over, Xiaolin discovered the system ran deeper than he could fathom.
Some architectural decisions he couldn't understand—why it was designed that way wasn't written down in any documentation. Some incident-handling records had only conclusions but no process—because the process had lived in the senior's head, and the senior was gone. He started working overtime, started losing sleep, started staring at his screen in the empty office late at night.
At the quarterly review, the manager's tone was still gentle: "Xiaolin, your potential isn't the problem—it's just that in the AI era, your thinking needs to keep up." After the meeting, the manager privately sent him a link: "Take this course. The instructor used to be at our company—he really understands our industry."
Xiaolin clicked the link. The course title glittered in gold, with an early-bird price of 4,999 yuan. In the instructor's photo, the man wore a well-tailored suit and smiled with composure—
It was the senior.
He could afford it. The extra million from the promotion made 4,999 yuan seem like nothing.
Xiaolin paid. The online course ran three and a half hours—prompt engineering, workflows, survival rules for the AI era. The content was shallower than he expected—so shallow he wondered if he'd missed some advanced modules. But he didn't dare say so. Because the comment section was full of familiar faces—his colleagues, contacts from the next department, even the manager who'd sent him the link—all had clicked "Like."
In the final chapter of the course, the senior looked into the camera and said: "In the AI era, the greatest danger isn't being replaced—it's refusing to change. Embrace change."
The audience—if an online course can have an audience—was filled with his former company's junior staff.
Act Three
Three years later, the company announced it was being acquired.
The press release was beautifully written: three years of continuous workforce optimization, operating costs down 30%, profit margins at historic highs—an acquisition target with "first-class asset quality and technical team." The acquirer's CEO told reporters he was buying "the future."
Three months after closing, the new owners launched "organizational integration."
The day the list came out, Xiaolin stood in the corridor outside the conference room for a long time. His name was in the second batch. HR's wording was polite and standard: business overlap, structural adjustment, thank you for your contributions. Severance was at the statutory minimum—not a cent more.
He suddenly remembered many things. The afternoon the senior cleared out his desk. The manager's hand on his shoulder. "The company believes in you." The senior's composed smile in the 4,999-yuan course.
It turned out the senior hadn't been teaching him how to survive.
The senior had been demonstrating how he himself survived—with their tuition fees.
The company fired the senior, saving ten million; the senior launched a course, earning money from those who stayed; and the reason those who stayed were anxious enough to pay was precisely what the company's rounds of layoffs had taught them. Company, instructor, platform—all three got what they needed, running smoothly. The only one continuously paying was every Xiaolin who thought he'd won.
Even the raise that made him feel like a winner—part of it, passing through his hands, circled back into this chain. The extra money the company paid him sustained the courses that kept him too afraid to leave.
Outside the corridor window, it was getting late. Xiaolin took out his phone and scrolled through social media out of habit. The algorithm served him an ad:
"AI Career Pivot Bootcamp—early-bird discount, last three days. Don't get left behind by the times."
In the instructor's photo, the man wore a well-tailored suit and smiled with composure.
Xiaolin stared at that face for a long time, then pressed "Save."
On the chessboard, there are no allies or enemies—only pieces that haven't been exchanged yet.
The above is fiction. But the numbers that follow are not.
Chapter One: Take the Story Apart, Inside It's All Cash Flow
The prologue is fiction. But if you tag every sum of money in the story and trace the direction it flows, you'll find this isn't a story at all—it's a cash flow statement.
The First Sum: Seven Million, and Its Multiplier
The company fired the senior, saving ten million in annual salary; promoted Xiaolin, paying an extra one million. On paper, this position nets seven million in savings each year.
If the story ended here, it would be nothing more than routine cost control. The real key is this: that seven million doesn't exist at a value of seven million.
When enterprises are sold, valuations are typically calculated as a multiple of profit. Using the tech industry's common range of ten to fifteen times, every dollar of annual cost savings is magnified into ten to fifteen dollars of valuation at the moment of the transaction. The seven million saved from the senior's position is worth seventy to one hundred and five million at the negotiating table.
This is why layoff targets are always the highest-paid people—not because they contribute the least, but because their salaries are the biggest lever in the valuation formula. Firing one ten-million-a-year senior engineer contributes more to the transaction price than firing ten one-million-a-year juniors. And the systemic gaps, the loss of experience, the technical debt that won't detonate for three years? Those aren't in the formula. The formula only calculates up to closing day.
In other words: the senior wasn't replaced by AI. The senior was exchanged out by a valuation formula. AI was merely the exchange rate cited in the explanation.
The Second Sum: The One-Million Raise, and a Liability Booked as Profit
Xiaolin's annual salary went from two million to three million. He gained an extra million, taking on a position nominally worth ten million.
But we can't simply say "Xiaolin delivered ten million worth of labor." The KPIs on the report were the same—projects ran, systems operated, targets were met—but his actual capabilities were not the same. The senior's ten-million salary had never bought just hours of work. It bought decades of accumulated judgment: why things were designed that way back then, how the last incident was resolved, which corners look like they can be cut but absolutely must not be. These things don't appear on the KPI dashboard, because dashboards only measure visible output—deep capability only surfaces the moment things go wrong.
So the seven-million "saving" actually consists of two parts. One part is the genuine extra labor Xiaolin contributes—overtime, shouldering pressure, burning himself out to fill the experience gap—this is extracted labor value. The other part is the capability gap that no amount of effort from Xiaolin can close—no one delivers this portion, yet it's booked as savings, turned into profit, turned into valuation.
In other words, half of the seven million on the company's books is squeezed out of Xiaolin; the other half is fundamentally a liability—a liability booked as profit. It won't appear on any quarterly earnings report. It will surface one day as an incident, a delay, a "how come nobody knows why this system was built this way." And on that day, the person standing at the scene, name written in the responsibility column of the postmortem, will be Xiaolin—just as the senior experienced in the prologue.
So Xiaolin's "promotion" is essentially two things happening simultaneously: he delivers labor below its value, subsidizing a deal he's not on the beneficiary list for; and he takes on an invisible liability for the company, waiting for it to detonate and serving as the on-scene responsible party.
And he's grateful for it. This is the most elegant part of the entire mechanism: the person being exchanged, at the moment of exchange, experiences victory.
There's one more link. The gap he can't fill doesn't sit quietly in the system—it reminds him every day: you can't handle this. That feeling has a name, anxiety; and anxiety happens to be the easiest emotion to monetize in the market. The capability gap Xiaolin can't close ultimately flows, in the form of 4,999 yuan, into the senior's pocket—and since the prompt engineering and workflows taught in the course can't fill a hole made of decades of judgment, the anxiety doesn't disappear, it only accumulates until the next checkout. The liability the company booked as profit has come full circle, becoming the senior's revenue.
This is the third sum of money.
The Third Sum: 4,999 Yuan, and Zero Customer Acquisition Cost
Now look at the senior's course.
Anyone who's run a business knows that the most expensive part of selling courses isn't producing the content—it's customer acquisition. You have to spend money on ads, nurture traffic, build trust before a stranger will part with their cash. Marketing costs eating 30–50% of the price tag is the norm.
But the senior's customer acquisition cost approaches zero. Because his customers aren't brought in by advertising—they're delivered by the company.
Every round of layoffs the company conducts creates a batch of anxious potential students for him. Every time a manager privately forwards the course link, it's a precision referral. Every "Like" from a colleague in the comments section is a trust endorsement. The company manufactures fear; the senior sells the cure. And the cure can be priced far above the content's actual value—because what the students are buying was never those three and a half hours. It's the feeling of "I did something, so I'm temporarily safe."
The three parties complete an unsigned division of labor: the company saves millions in salary and gets a workforce that "self-funds continuing education and actively embraces AI"; the senior earns back the salary taken from him, one bill at a time, from his former juniors' pockets; the platform takes its cut and recommends the course to the next Xiaolin.
Nobody breaks the law. Nobody lies. Every party simply makes the most rational choice from their position. This is precisely what makes it terrifying—the structure doesn't need villains, only for everyone to be rational.
There's one more detail that only becomes visible when placed on the full ledger: the reason Xiaolin can afford this course is precisely because the company gave him that extra million.
A person earning two million a year, barely breaking even on living expenses, would hesitate at 4,999 yuan. A person who just got promoted to three million won't. The raise does two things simultaneously: it makes him believe he's on the rise, and it gives him disposable income—and what the anxiety market needs is precisely "anxious people who can afford to pay." Without that extra million, he's just an anxious person; with it, he becomes a customer.
And so the money completes a full circle: the company saves seven million from this position, allocates one million of it to Xiaolin, Xiaolin transfers part of it to the senior—and the senior is the very source of the company's seven-million saving. Money leaves the company, passes through Xiaolin's pocket, and returns to the person the company fired—while the company nets six million and gets a bonus: an employee who "self-funds continuing education and actively embraces AI."
The crucial point is: after completing this circle, Xiaolin's situation hasn't changed at all. He's still doing ten-million worth of work, earning three million, carrying the unrecoverable capability gap. The tuition he paid buys back none of his lost bargaining power. The raise, the learning, the professional development—at every step he did the right thing, and at every step he sank deeper into the position he was already in.
The Fourth Sum: The Invisible One—Public Funds
The story doesn't mention it, but in reality there's a fourth stream of money.
The ecosystem surrounding these courses is often ringed by various lectures, meetups, and annual conferences. Nominally priced at 2,000 yuan, in practice you can attend for free by surrendering your personal information—because what the organizer really wants isn't your money, but your registration record. Your email, your attendance, your headcount—these become "service person-counts," appearing in the final reports for government subsidies.
Government subsidies act as an amplifier in this structure: they allow organizers to use public funds to invite industry speakers; the speakers' reputations build credibility; credibility attracts more headcounts; more headcounts secure the next round of subsidies. A business that was originally constrained by the scale of private capital has its ceiling removed once connected to public funds.
And so the full version of this cash flow is: taxpayers subsidize the events, events feed the traffic, traffic converts into course sales, and the existence of course revenue in turn proves that "demand for AI education is booming"—becoming the basis for applying for the next round of subsidies.
Closing the Ledger
Now put all four sums on the same table and ask the simplest question: who is the net outflow party?
The company is net inflow: salary savings converted into valuation. The original shareholders and management are net inflow: transaction premiums pocketed. The senior is net inflow: salary recovered in a different form. The platform is net inflow: commissions and traffic. The government spent subsidies, but the money spent was taxpayers'.
The net outflow parties are only two kinds of people: the Xiaolins who paid tuition, contributed the labor price differential, and were ultimately severed at the statutory minimum; and the next wave of shareholders and employees who, after closing, inherit a hollowed-out organization.
The direction of cash flow is the direction of power. Throughout the prologue, Xiaolin couldn't understand his own situation—not because he wasn't smart enough, but because he was always looking upward from the outflow end. From that angle, every dollar flowing out looks like an opportunity.
Next, we shift the lens from the fictional Xiaolin to real numbers. In the first half of 2026: one hundred and fifty thousand Xiaolins.
Chapter Two: One Hundred and Fifty Thousand Xiaolins—When Layoffs and Record Earnings Appear in the Same Report
Before diving into the numbers, we must honestly confront a methodological objection.
The prologue and Chapter One strung six links into a chain: companies fire expensive staff and hire cheap replacements; "natural attrition" masks forced departures; capability gaps are booked as profit; anxiety is monetized through courses; public funds amplify the entire market; and it all serves a transaction. If these six links are merely inferences, the entire chain is a slippery slope—the first link holding doesn't mean the second necessarily follows. No matter how smoothly the story reads, it cannot substitute for proof.
So what this article does from here on is take each link out individually and nail it down with verifiable public evidence: earnings reports, regulatory filings, named research studies. This chain isn't inferred—it's verified, link by link.
Link One: Layoffs and Record Profits Happening Simultaneously—This Isn't Inference, It's the Earnings Report
Start with the aggregate.
According to tracking data from tech recruitment platform TrueUp, by mid-June 2026, the global tech industry had seen 363 layoff events affecting nearly 150,000 workers—an average of 974 people per day, 44% faster than the same period last year. And this is only the first half.
Looking at the numbers alone, you might assume this is a recession. But the 2026 wave differs fundamentally from every previous round of layoffs: these companies aren't losing money. Many of them are delivering their best financial results in history.
A few examples, all from public earnings reports and mainstream media coverage:
Internet infrastructure company Cloudflare, in the same earnings call, announced cutting 1,100 workers (20% of its workforce) while posting record quarterly revenue of $639.8 million, up 34% year-over-year. CEO Matthew Prince specifically emphasized: this is not cost-cutting. The company's internal AI usage had grown sixfold in three months.
Enterprise software giant Salesforce cut approximately 5,000 customer service positions across two rounds. CEO Marc Benioff's exact words were that he "needs fewer headcount," while at the same time the company's AI customer service product Agentforce was already handling 1.5 million customer conversations. The positions cut were entry-level.
Oracle laid off approximately 21,000 people over the past twelve months and publicly attributed the cuts to AI investment, while forecasting that AI would bring further reductions. Amazon eliminated 30,000 corporate positions over several months. Meta, in the same quarter it reported substantial revenue growth, laid off 8,000 people while directing tens of billions of dollars in capital expenditure toward AI infrastructure. Cisco posted record quarterly revenue of $15.8 billion while cutting 4,000 positions.
Put these together and the pattern is almost brutally clear: record revenue, record profit, record capital expenditure—and layoffs. The money hasn't disappeared. According to multiple media tallies, the major tech giants' combined capital expenditure commitments toward AI infrastructure in 2026 total approximately $700 billion. The salaries saved through layoffs are immediately converted into budgets for chips, data centers, and model training.
The money also went somewhere else: shareholders' pockets. Official data from S&P Dow Jones Indices shows that S&P 500 companies' stock buybacks breached $1 trillion for the first time in the twelve months ending September 2025, setting a historic record; the pace of buybacks in 2026 continues at record levels, with full-year expectations for another all-time high. The buyback mechanism is worth explaining once: the company purchases its own shares and retires them, causing earnings per share (EPS) to rise even when total earnings remain completely unchanged—this is the most direct fuel for executive compensation and stock price. The cost savings from layoffs and the EPS boost from buybacks mutually reinforce each other on the same earnings report.
What Kind of Layoff Is Reasonable
Before continuing, the strongest counterargument must be stated in full—otherwise nothing that follows will stand.
The counterargument goes like this, and it's quite powerful: when companies streamline their workforce, it's often genuine structural improvement, unrelated to AI or financial engineering.
Take the hardware industry as an example. A company that previously ran a "product proliferation" strategy—simultaneously maintaining thirty product lines, each with its own hardware team, drivers, testing, and supply chain contacts—had massive duplication across those lines. The same function written thirty times, the same problem solved thirty times, the same documentation maintained in thirty copies. When the company decides to consolidate into two shared platforms, keeping differentiation only at the outermost layer, the redundant work genuinely disappears. At that point, fewer people are truly needed—and not because "fewer people are doing the same work," but because "there's less work to do."
This kind of streamlining is correct. It doesn't just save costs—it actually makes the product better, because force previously scattered across thirty lines is finally concentrated on two. The software industry has equivalent versions: replacing fifteen homegrown tools with a single standard platform, or consolidating each team's independently maintained deployment scripts into unified infrastructure. These are genuine efficiency gains, and the accompanying headcount reduction is a reasonable outcome.
So the question was never "are layoffs always wrong." Layoffs can be right. The question is: how do you tell which kind?
There's a test—so simple it's almost crude, but very hard to fake: look at whether the workload actually decreased, and look at who left.
Genuine architectural consolidation has two inevitable characteristics. First, remaining employees' workload should stay flat or decrease—because the redundant parts have been eliminated. If, after consolidation, those who remain are working more overtime, carrying three people's load, handling at midnight what three teams used to share—then the redundancy hasn't been eliminated, only transferred to individuals. The work hasn't decreased; only the number of people bearing it has.
Second—and harder to fabricate: designing a platform that covers thirty scenarios requires more senior judgment, not less, than maintaining thirty independent product lines. To consolidate thirty lines into two, someone must know why each of those thirty lines was designed the way it was, which differences are essential, which are legacy baggage, and which one, if cut, will explode two years later. This knowledge exists only in the heads of people who've been there long enough. So a genuine architectural consolidation should retain precisely the most senior, most expensive people; what gets trimmed should be the redundant mid-level and junior work.
And so the test becomes very clear.
If a company announces structural streamlining, then retains senior architects, trims the redundant execution layer, the remaining staff's workload decreases, and two years later the system is genuinely more stable—that's real consolidation. This article's criticism has nothing to do with it.
If a company announces structural streamlining, and the first to disappear are the highest-paid, most senior people, the remaining staff's workload increases rather than decreases, and the new "platform" keeps breaking over the next two years because nobody knows why the original was designed that way—then what happened isn't consolidation. It's replacement. Streamlining is just the language it uses.
Chapter Three will show which answer this test yields against real data: under mandatory return-to-office and "natural attrition" policies, those who leave aren't the redundant execution layer but senior employees, high-skill workers, and senior managers—precisely the people architectural consolidation most needs to retain.
One sentence to summarize this section: When the work to be done actually decreases, that's efficiency. When the work to be done hasn't changed but the people doing it get cheaper, that's arbitrage. Both use the same vocabulary in press releases, both enter the same line item on the income statement, but three years later they leave completely different things in the system.
The Third Possibility: The Work Didn't Disappear—It Just Moved Off the Report
The previous section distinguished two categories: genuine efficiency, and arbitrage. But in practice, the most common case is actually a third category—and it's the hardest to expose, because it leaves almost no trace on the income statement.
That is: converting in-house work to outsourcing.
The operation is simple. Work previously done by internal teams—driver development, testing and verification, operations, customer service, certain software modules—is handed over to external vendors, ODMs, offshore teams, or contract workers. Internal headcount drops significantly, and the drop looks great.
The key is that these two things go into different line items.
Full-time employees' compensation is booked under personnel expenses, and "employee headcount" itself is a public figure that investors watch closely—disclosed in annual reports, compared by media. Cutting 10% becomes an achievement to announce. Outsourcing costs are different: they go into cost of goods sold or operating expenses under professional services, outsourced services, or procurement—mixed in with a pile of other expenditures. There's no separate line item called "we moved this work outside."
So the same thing gets two narratives. The internal and external story is: we adopted AI and automation, achieving the same output with a leaner organization—workforce efficiency up 30%. What actually happened: the workload hasn't decreased at all. The people doing it switched from on-payroll to off-payroll; the cost moved from one line item to another. AI didn't do anything, but the credit goes to it—because announcing AI results at this moment makes the stock price rise; announcing "we outsourced our R&D" doesn't.
Can this be verified? Yes, and you don't need insider information.
Open the same annual report and plot the change in employee headcount alongside the change in outsourcing/professional services/procurement spending. If headcount drops sharply while outsourcing spending rises by a comparable amount, then the "efficiency from AI" needs recalculating—genuine efficiency gains should see both lines trending down, not one down and one up. This comparison is tedious to do, so few people bother; but it's all public data, available to anyone.
And the cost of outsourcing surfaces later than arbitrage, and is harder to reverse.
Replacing expensive people with cheaper ones at least keeps the capability gap inside the company—theoretically recoverable. Outsourcing moves knowledge entirely outside the walls: three years later, no one on payroll knows why that module was written the way it was. When the vendor raises prices, you have no bargaining power because switching costs are prohibitively high. When you try to bring it back in-house, you discover there's no one in the company who can take it over—you've even lost the ability to judge whether the vendor's quote is reasonable. What you saved was salary; what you sold was optionality.
This point will resurface in Chapter Five. Because a company that has outsourced its core capabilities and looks extremely lean on paper is a perfect acquisition target—until the buyer discovers what they bought isn't a team, but a stack of contracts.
Link Two: "Fire Expensive, Hire Cheap"—High Out, Low In, With Data to Prove It
Chapter One hypothesized that companies fill expensive positions with cheaper people. The evidence for this link comes from both ends of the labor market.
The exit end: labor analytics firm Revelio Labs' data shows that among white-collar workers who changed jobs in late 2025, 40% accepted pay cuts exceeding 10%—the highest proportion in at least a decade. Researchers call this "wage scarring": once you re-enter the market at a lower price, future compensation anchors to the depressed level long-term. Job platform ZipRecruiter's quarterly survey similarly found that over a quarter of new hires earned less than in their previous role, while those willing to negotiate dropped to 30%.
The entry end is more direct: after cutting a quarter of its workforce in 2022–2023, Meta was confirmed by media to be rehiring some of the same laid-off employees—at lower compensation. The company even set up an "alumni portal" for former employees to reapply. Same person, same skills, fired once, price reset once. And this playbook isn't even an AI-era invention: back in 2007, American electronics retailer Circuit City publicly announced it was firing 3,400 employees whose "pay exceeded market rates" and inviting them to reapply for their original positions at lower wages after ten weeks. Back then, doing this made headlines and triggered boycotts. Today, the same logic, packaged as "organizational transformation," is treated as good news for the stock price.
Something must be stated clearly here: this article does not deny the real productivity changes brought by AI. The issue isn't whether AI is useful, but that the word "AI" has changed its function in earnings-report language.
In the past, layoffs required reasons: economic recession, pandemic adjustments, business contraction. These reasons were negative—the company had to bear reputational pressure, and stock prices usually fell. Now, a single phrase—"AI transformation"—turns layoffs from bad news into good news. It proves the company is at the forefront; it proves management has vision. Stock prices don't fall—they rise.
AI isn't the cause of layoffs. AI is the license for layoffs.
There's also a distributional issue hidden beneath the aggregate numbers that deserves even more alarm: this wave of layoffs didn't land evenly. Entry-level positions bore the heaviest impact. Data from Stanford's Human-Centered Artificial Intelligence Institute (Stanford HAI) shows that employment among software developers under 26 has dropped nearly 20% since 2024. Cryptocurrency exchange Coinbase, during its restructuring, directly eliminated "pure management" roles, reorganizing into small teams led by senior engineers directly commanding AI agents—a structure with no room for newcomers who need guidance, who need time to grow.
Place this back into the prologue's logic and you see a longer time bomb: Xiaolin at least had the chance to sit in that seat. The next generation of Xiaolins won't even get a ticket through the door. If nobody hires junior engineers today, there will be no senior engineers in ten years—but as Chapter One noted, ten years from now isn't in the valuation formula. The formula only calculates up to closing day.