Laid off in the AI shakeout? Keep shipping so you don't go stale

Getting cut in a downsizing is disorienting in a specific way: it usually has nothing to do with how good you are. Whole teams go in a single quarter. Roles get "consolidated." Budgets that funded your seat get redirected toward automation. You did the work well and the work went away anyway. That's a genuinely different experience from being managed out, and it deserves a different response.

But the job market doesn't see your inbox or your performance reviews. It sees a CV that stopped on a date. And right now, in a market flooded with other people cut in the same wave, the candidates who get traction aren't the ones with the best layoff story. They're the ones who never stopped shipping.

The two clocks that start the day you're let go

From the moment your role ends, two clocks begin running, and they pull in opposite directions:

• The recency clock. Every month without shipping makes your last real work older and your skills look less current. This one works against you automatically — doing nothing winds it forward.
• The proof clock. Every piece of visible work you ship resets your recency and adds fresh evidence. This one works for you — but only if you keep it running.

Most people, in the shock after a layoff, let the recency clock run while they "take some time" or send applications into the void. Understandable — but it's the worst of both, because applications don't reset recency and time off doesn't either. The move is to start the proof clock fast, while you also search.

The AI twist: turn the thing that cut you into your edge

Here's the part specific to this wave of layoffs. If AI tooling was part of why your role shrank, then the single most reassuring thing you can show a future employer is that you build fluently with those exact tools. Not as a threat you survived — as a capability you've absorbed.

Every serious engineering org is right now trying to answer one question internally: who on our team actually ships more because of AI, versus who just talks about it? A candidate who can point to recent, real work built the modern way — AI in the loop, fundamentals intact — answers that question before it's asked. As one industry leader put it, software engineering has shifted from typing code to understanding systems, and the engineers who thrive are the ones who see the whole picture and still build real solutions.

Experience isn't a substitute for recency

If you've been working for years, there's a trap waiting for you that grads don't face: the belief that your track record speaks for itself. It did — while you were employed. The moment there's a gap, a long CV with an old last-entry can actually read worse than a junior's, because it raises the question "if they're so experienced, why is the most recent thing a year old?"

Seniority doesn't exempt you from the recency clock. It raises the bar. The fix is the same as for everyone else, just more urgent: get one current, visible, vouched-for piece of work onto the top of the page so your experience has something fresh to stand on.

What to ship when you don't have a job to ship from

The obvious objection: "I'd happily keep shipping, but shipping happens at a job, and that's the thing I just lost." Fair. Personal side projects help, but they have a weakness — no one vouches for them, and a recruiter can't tell a serious one from a weekend toy. What you want is real work on a real product, with someone credible to confirm you did it. Concretely:

• Real users, not a sandbox. Work that's live and in production carries weight a personal repo can't.
• A bounded scope. A four-week, well-defined piece you can actually finish beats an open-ended project you'll abandon when an interview heats up.
• A reference attached. The deliverable isn't just the code — it's a named person, on the record, saying you shipped it.
• Modern tooling on display. Build it the way teams build now, so the work itself demonstrates you're current.

This is precisely the gap The Academy fills. You join a live Irish software project — the kind of thing with a real codebase and real traffic — ship a bounded piece of it under a mentor over about four weeks, and walk away with a public reference at a verifiable URL, co-signed by Raven Design and Built In Ireland. It's free, it's fast, and it's built to run alongside your job search, not instead of it.

The bottom line

Being laid off in a downsizing isn't a verdict on your ability, and you shouldn't let it become one in the eyes of the market. The way you keep it from sticking is simple to say and entirely in your control: don't let the recency clock run unanswered. Ship something real, ship it soon, build it with the tools that are reshaping the field, and get someone to vouch for it. Do that, and your story stops being "my role was automated" and starts being "I adapted faster than the people still waiting."