45,000 People. Three Months. And a Problem Nobody's Talking About.
By early March 2026, 45,363 tech workers had already lost their jobs. Meta is reportedly planning to cut up to 20% of its workforce to fund AI spending. Amazon has let go of 16,000 this year alone. Block slashed 4,000 roles.
But here's the number that stopped me: 20.4% of those tech layoffs were explicitly linked to AI and automation. Not restructuring. Not cost-cutting dressed up in vague language. Companies openly said "we're replacing these roles with AI."
That's nearly 9,300 people who were told, in so many words, that a machine can do what they did.
If you're one of those 45,000, or you're watching your company's Slack channels with a knot in your stomach, this post is for you. Because the problem nobody's talking about isn't finding open roles. It's that most people who've been employed for three, five, ten years have completely forgotten how to interview.
The Skills Gap Nobody Warns You About
Being brilliant at your job and being brilliant at talking about your job in an interview are two completely different skills. They use different muscles. And the interview muscles atrophy fast.
I once spoke with a senior engineer who'd been at the same company for seven years. Led a team of twelve. Architected systems handling millions of requests per day. Genuinely excellent at what she did. She went into her first interview in years and was asked, "Tell me about a time you dealt with a difficult stakeholder." Her answer was four minutes of context and about fifteen seconds of what she actually did. She knew the story. She just couldn't tell it under pressure.
This is incredibly common. When you're working, you don't need to narrate your achievements in neat 90-second packages with a clear beginning, middle, and end. You just do the work. The work speaks for itself.
Interviews don't care about that. Interviews care about whether you can articulate your impact clearly, concisely, and with enough specificity to be credible. If you haven't practised that in years, you're going to struggle. Not because you're not qualified. Because you're out of practice.
| Interview Skill | How It Atrophies | Why It Matters |
|---|---|---|
| Structured storytelling (STAR) | You stop packaging achievements into narratives | 90% of behavioural questions need this format |
| Concise delivery | Work conversations are long-form and collaborative | Interview answers need to land in 60 to 120 seconds |
| Speaking under pressure | You're comfortable in your domain, rarely put on the spot | Interviews are adversarial by design |
| Self-promotion | Good colleagues credit the team, not themselves | Interviewers need to hear what you did, specifically |
| Company research | You haven't had to research a company in years | Generic "why this company?" answers are an instant red flag |
What 45,000 Tech Layoffs Mean for Interview Competition
Here's where the maths gets uncomfortable. Those 45,000 laid-off workers aren't disappearing. They're all hitting the job market within the same few months. And they're competing for many of the same roles.
The KPMG/REC UK Report on Jobs for March shows the Permanent Placements Index at 49.2, up from 46.9 in January. That's the closest to positive territory in three years. Engineering is the only sector where demand for permanent staff is actually growing. Jon Holt, KPMG's UK Senior Partner, called it "the closest point to turning positive" since 2023.
So yes, hiring is warming up. But here's the catch: a warming market doesn't mean less competition. It means more competition, at least initially. Companies that froze hiring for 18 months are about to start posting roles again. And tens of thousands of experienced workers who've been waiting on the sidelines are about to rush in simultaneously.
| Metric | January 2026 | March 2026 |
|---|---|---|
| KPMG/REC Permanent Placements Index | 46.9 | 49.2 (3-year high) |
| Tech layoffs (2026 YTD) | ~18,000 | 45,363 |
| UK unemployment | 4.4% | 5.2% |
| Layoffs explicitly citing AI | ~15% | 20.4% |
The window is opening. But it's going to be crowded.
Why Experienced Workers Struggle More Than They Expect
This is the part that catches people off guard. If you've been working in tech for five or ten years, you're probably thinking: "I have real experience. I'll be fine." And you might be right. But seniority brings its own interview pitfalls.
You default to "we" instead of "I"
Senior people are often good at their jobs because they're collaborative. They think in terms of team outcomes, not personal contributions. That's great at work. It's poison in an interview. When you say "we redesigned the architecture," the interviewer has no idea what you specifically contributed. They need to hear "I" more than feels comfortable.
Your stories are too complex
After years of working on large systems, your examples tend to involve six teams, three quarters of work, and a dozen competing priorities. That's the real world. But interview answers need to be tight. Pick one thread and follow it. The interviewer doesn't need the full picture. They need a clear one.
You're rusty on fundamentals
Nobody asks a principal engineer to whiteboard a binary search tree at their day job. But interviews might. Nobody asks a VP of engineering to explain the STAR method in a team meeting. But a competency-based interview will absolutely expect that structure. The gap between what you do daily and what interviews test can be jarring.
What the AI-Displaced Cohort Faces Specifically
The 20.4% of layoffs explicitly linked to AI create a unique interview challenge. When your role was automated, every interviewer is going to ask some version of: "How do you work with AI?" or "How would you use AI tools in this role?"
If your answer is defensive ("AI can't replace what I do") or vague ("I'm open to learning"), you're done. The people who get hired will be the ones who can articulate a specific, practical relationship with AI tools. Not performative enthusiasm. Concrete examples.
"I used Copilot to handle boilerplate in our migration scripts, which freed me to focus on the edge cases around data integrity. Saved about six hours a week." That's an answer. "I think AI is a great tool and I'm excited to learn more" is not.
If you were laid off specifically because AI replaced your function, you need a narrative for why your skills are still valuable, just in a different context. That narrative won't write itself. You have to build it, refine it, and practise saying it out loud before someone asks the question for real.
The Timing Advantage Most People Miss
The ONS labour market data for March 2026 shows UK economic inactivity falling to 20.7%. That means more people are moving from "not looking" to "actively looking." Combine that with the KPMG data showing hiring is almost positive again, and you get a very specific window.
Right now, roles are starting to open. But the full flood of candidates hasn't hit yet. People are still updating CVs, still processing their redundancies. Most haven't even thought about interview prep yet. The ones who start preparing their interview skills now, before the rush, will have a measurable head start.
This isn't motivational poster stuff. It's simple queue theory. When everyone arrives at the door at the same time, the person who's already prepared gets through first.
What to Actually Do If You've Been Laid Off
Forget the CV for a moment. Everyone polishes their CV first. It's the least differentiating thing you can do. Here's where to spend your first week instead.
1. Build a story bank of eight strong examples. Cover these themes: a technical challenge you solved, a time you led through ambiguity, a conflict you navigated, a failure you learned from, a cross-functional collaboration, a time you worked under pressure, a time you influenced without authority, and a time you delivered something measurable. Write each one in STAR format. Then say them out loud. Not in your head. Out loud. The difference is enormous.
2. Record yourself answering three standard questions. Use your phone. Answer "Tell me about yourself," "Why are you looking for a new role?" and "Tell me about a time you dealt with a difficult situation." Play them back. I guarantee you'll hear things you didn't expect: filler words, rambling, a great point buried three minutes into a four-minute answer. Better to hear it now than in front of an interviewer.
3. Prepare your redundancy narrative. You're going to be asked why you left. Have a clean, honest, 30-second answer ready. "My role was part of a broader restructuring" or "The company shifted its technical direction and my team was affected" is fine. Don't badmouth. Don't over-explain. And don't be apologetic. Layoffs aren't a character flaw.
4. Research every company like you mean it. Twenty minutes per company. Read their engineering blog. Check their recent LinkedIn posts. Find one specific thing they've done recently that you can reference. The bar for company research in interviews is shockingly low. Most candidates don't bother. You should.
5. Do at least one practice interview before a real one. The goal isn't perfection. It's recalibration. You need to feel what it's like to answer questions under time pressure, to handle follow-ups you didn't expect, to hear yourself speak about your own work in a way that's structured and convincing. You will be rusty the first time. That's the point. Be rusty in private so you can be sharp when it counts.
The Bottom Line
45,000 tech workers have been laid off in 2026 so far. The pace is accelerating. One in five of those cuts explicitly cited AI. Meanwhile, the UK hiring market is showing its first real signs of recovery in three years, with engineering demand growing.
That combination creates a very specific moment. Roles are opening. Competition is about to surge. The people who start preparing their interview skills now, not next month, not when they see a role they like, but now, will be the ones who move fastest when the right opportunity appears.
Your job was doing the work. Your interview is telling the story of the work. They're not the same skill. And the second one needs practice too.
Adrian, Instant Interview
