What the last Meta layoff teaches us
When AI becomes the new headcount
Meta just cut around 8,000 jobs, about 10% of its global workforce, and froze roughly 6,000 open roles, all while reallocating about 7,000 people to AI teams and data-center workstreams.
Wall Street is happy, the stock likes “efficiency”, and every Software Engineer on LinkedIn is asking the same question: what does this teach us about our own careers?
Spoiler: this is not a Meta story.
It is a story about you, your skills, and how you show them to the market.
Layoffs are the new normal, not the exception
Meta is not a special case.
Across Big Tech, layoffs have become a recurring pattern to fund massive AI bets: Amazon, Microsoft, Oracle, Intel, and others have all cut thousands of roles in the last 18 months to “reallocate resources” toward AI infrastructure.
The narrative is always the same:
“We are investing heavily in AI.
To stay lean and efficient, we have to reduce headcount.”
Look at the Meta numbers:
About 10% of the workforce gone in one shot, roughly 8,000 people.
Thousands of roles cancelled before anyone could even be hired.
Around 7,000 people moved from “legacy” work to AI-related teams.
This is a systemic refactor of the org chart.
And if you treat your job as a static thing that someone owes you, you are acting like legacy code that nobody wants to maintain.
The real lesson: you are either a cost or a component
In these stories, companies publicly say they are cutting roles because AI lets smaller teams do more and they want to fund gigantic AI infrastructure budgets.
Read that again.
They are literally telling you the new mental model:
Compute is an asset.
Headcount is a liability.
Inside this model, every engineer becomes either:
A cost center: someone who just “implements tickets”.
A core component: someone who owns problems, influences direction, moves business metrics, and can drive or adopt AI-driven workflows.
Meta is reallocating thousands of people into AI-related work, not just firing.
So the message is not “you are doomed”.
The message is: if your role can be done by a smaller, more AI-augmented team, sooner or later someone will test that hypothesis.
You choose which side you are on.
The Code Monkey vs the Product Engineer
Imagine two backend engineers in a big company.
Same stack, same seniority, same salary.
Different mindset.
First one: the Task Taker.
They come online, open Jira, ask “what’s my ticket?”, ship the feature, log off.
Second one: the Product Engineer.
They still ship tickets, but they also:
Talk with PMs and designers to understand why this feature matters.
Measure impact: latency, revenue, churn, adoption.
Share clear updates on Slack and LinkedIn when they solve hard problems (without secrets, just stories and lessons).
Now imagine a layoff meeting.
Management has to cut 10% of the team because AI tools will cover some repetitive tasks.
Who do you think they see as “still critical”?
Not the one who silently ships tickets that now a smaller AI-augmented team can handle.
The one who:
Owns business outcomes.
Shows leadership beyond code.
Has a visible track record of solving relevant problems.
Same coding level. Different perception. Different outcome.
You cannot control layoffs, but you control your visibility
There is something brutal in this Meta layoff: many of the impacted people found out at 4 a.m. emails, with the press knowing almost at the same time.
It feels unfair.
It is unfair.
But you still have one lever that is completely under your control: how you present yourself to the market, every single week.
Think in terms of:
Input: your daily work, the problems you solve, the systems you touch.
Output: how you document and communicate that work.
Most engineers stop at the input.
“That’s what they pay me for.”
The problem is that when a recruiter, a hiring manager, or even your own leadership looks at you from the outside, they only see the output:
A silent profile with a job title and no context.
Or a profile with short posts about actual challenges, trade-offs, and results.
During a layoff wave, or right after, this difference is massive.
Layoffs compress the market, and LinkedIn becomes your CI pipeline
When 8,000 people are cut from one company, that talent does not disappear.
They all go to the same place: LinkedIn.
At the same time, other companies are doing similar cuts, often to fund the same AI bets.
So what happens?
More engineers on the market.
Fewer “classic” roles opened, more niche AI-adjacent roles.
Recruiters with less time per candidate.
In this environment, your LinkedIn profile is not a static CV.
It becomes your continuous integration pipeline for opportunities:
Each post is a new build of your professional story.
Each project you document is a new deploy into someone’s memory.
Each connection you nurture increases the “uptime” of your network.
If you refuse to “sell yourself”, you are basically:
Commenting out the only deployment pipeline for your career.
What to actually do this week
You don’t need to turn into a content creator.
You need a simple, boring, repeatable routine.
Here is one you can start after finishing this email:
Refactor your LinkedIn headline
Stop with “Software Engineer at X”.
Try “Backend Engineer | Reducing latency in payment systems” or “Mobile Engineer | Building reliable consumer apps”.
One line that says what problems you solve, not just where you sit.Ship one small post per week
Pick one problem from your work: a migration, a bug, a performance issue.
Write 5–7 lines about: context, the problem, what you tried, what worked, and what you learned.
No secrets, no NDAs broken, just your thought process.Keep a private changelog
In Notion, Obsidian, or even a Google Doc.
Every time you solve something non-trivial, log it: date, context, what you did, impact.
This becomes your internal “release notes” when you need to update your CV, your LinkedIn, or prepare for an interview.Talk with one person per week outside your team
Someone in product, design, data, or another company.
Ask what they are struggling with, how AI is changing their work, what skills they value today.
You are not selling anything. You are collecting requirements for your own roadmap.
None of this is “being an influencer”.
This is just observability for your career.
The Meta layoff as a warning signal, not a prophecy
If you are reading about Meta cutting thousands of jobs to pour billions into AI, and you think “this has nothing to do with me”, you are missing the real signal.
This is not about one company.
It is about a new default:
AI is a first-class citizen in budgets.
Headcount is a variable to optimize aggressively.
Engineers who only ship code without owning outcomes or telling their story are easy to replace on paper.
So treat this layoff like you would treat a scary production incident:
Don’t panic.
Don’t ignore it.
Run a postmortem on your own career.
Where are you still pure “cost center” in the eyes of others?
And what can you ship this month to change that perception?