On Friday, a software engineer with a decade of experience published a post on Bear Blog titled “LLMs are eroding my software engineering career and I don’t know what to do.” By Sunday it had cleared 830 points on Hacker News, 800-plus comments, and the unmistakable hum of a profession worried it’s being devoured from within. The post is honest, anxious, and entirely reasonable. It is also, in one important respect, wrong about what’s actually happening.

The essay’s core claim — that LLMs are steadily replacing the kind of mid-level frontend engineering work the author does — is an anecdote searching for a data set. And the data sets we do have, from the spring layoff cycle that just tore through the industry, point somewhere the thread isn’t looking.

150,000 Layoffs, and Frontend Engineers Were Not the Main Target

According to Tech Insider’s running tally, more than 150,000 tech jobs have been cut so far in 2026. The numbers are staggering: Oracle alone shed up to 30,000 employees via a 6 a.m. email in April. Meta cut 8,000 roles — roughly 10 percent of its workforce — explicitly to fund AI research. Block laid off 4,000 workers, framing the decision in terms that made the substitution logic impossible to miss: AI could do the work, so the company would pay for AI instead.

Read those announcements carefully and a pattern emerges. The roles being cut are not, by and large, the IC5 frontend engineers writing React components. They are middle management, program managers, internal-tools teams, QA orgs, and — at Oracle — entire cloud and healthcare sales divisions. The “AI is coming for your job” story that dominates Hacker News threads imagines a developer being replaced by a prompt. The actual layoff notices describe something closer to a thinning of the organizational layer cake: fewer people coordinating work, fewer people checking work, fewer people selling work.

This is a real shift. It just isn’t the one the viral post describes.

The Bear Blog’s Blind Spot Is the Same One the Industry Has

The author’s complaint is specific: he used to be paid well to build web frontends, and now LLMs can generate acceptable frontend code faster than he can. His freelance pipeline has dried up. His confidence has cratered. It is a painful read, in part because it is so plainly sincere.

But here is what the essay does not grapple with: the 10-year frontend engineer who only writes frontend code was already in trouble before GPT-4 shipped. The market for pure-implementation roles — “take this Figma file and translate it to JSX” — has been compressing for years. Offshoring, component libraries, no-code tools, and the sheer maturity of the web platform all ate into that niche long before anyone typed a prompt into Cursor.

The LLM didn’t kill the job. It finished a kill that was already mostly complete. And that distinction matters, because it changes what the right response is.

What the Laid-Off Oracle Managers Understand That the Essayist Doesn’t

“You want to know who’s actually scared?” said one engineer who survived the April cuts at a major cloud provider, speaking over Signal from a conference room he’d booked just to have somewhere quiet to think. “It’s not the people who can build things. It’s the people whose whole job was being a router. Read an email, figure out who needs to know, forward it. That’s gone. Nobody’s going to miss it.”

SQ Magazine’s analysis of the 2026 layoff cycle supports this: the roles vanishing fastest are coordinators, QA leads, and middle-tier managers whose primary output was status updates. The engineers who ship code — including frontend engineers who have picked up even modest backend or infrastructure skills — are surviving at higher rates. The severance packages are going to the routers.

This is not a story about AI replacing software engineering. It is a story about AI revealing which jobs were software engineering and which jobs were something else — something the industry tolerated during a hiring bubble and no longer needs to fund.

The Anxiety Is Real. The Conclusion Is Backward.

The Bear Blog author ends with a kind of resignation: maybe this career was a temporary aberration, maybe the party is over, maybe it’s time to find something else. That is one reading of the evidence. Here is another: the party that’s ending is the one where you could build a comfortable 20-year career on a single skill that a motivated high-schooler with Claude can replicate in an afternoon.

That is a brutal thing to hear if you spent a decade specializing in that skill. It is also, arguably, a correction the industry needed. The median salary for a frontend engineer at a Bay Area tech company in 2023 was north of $180,000. Companies were paying that not because React is hard but because capital was cheap and hiring was a land grab. The cheap-capital era is over. The land-grab era is over. What is emerging in its place is a market that prices implementation skills the way it prices any other commoditized input — and pays a premium for the people who can decide what to build, not just how to build it.

If you are a 10-year engineer and the only thing you bring to the table is the ability to produce code faster than a junior, you have a problem. But the problem is not the LLM. It’s that you spent a decade in an industry that rewarded depth without breadth, and the bill just came due.

Sources