So You've Been Laid Off — Sella Rafaeli

The first weeks of 2023 have been brutal. Amazon, Microsoft, Google, and a long list of smaller companies have announced layoffs in the tens of thousands. Many of the people being let go are experienced engineers who did nothing wrong - they just happened to be in the wrong org chart when the spreadsheet came around.

If you’re one of them: I’m sorry. It’s not personal, even though it feels very personal. Here’s what I’d tell a friend who’s a senior developer and just got the email.

First week: don’t do anything big

Take a few days. You don’t need to start applying tomorrow. Being angry, sad, or weirdly relieved are all normal. Let it settle.
Sort out the practical stuff. Severance terms, health insurance, equity deadlines (some companies give you a short window to exercise options - read the fine print), unemployment benefits. Write down the dates.
Save your contacts. Before your accounts are closed, make sure you have the personal contact details of the people you liked working with. You’ll want them.
Don’t post the angry thread. You might be right. It still won’t help.

Figure out what you actually want

A layoff is a terrible thing that also gives you something rare: a clean break and some time to think. Before you jump at the first offer, ask yourself honestly:

Do I want the same job at a different company?
Do I want a smaller company, with more ownership and less process?
Do I want to manage, or stop managing?
Do I want to try going independent?
Is there something I’ve always wanted to build?

There’s no wrong answer. But “whatever I can get fastest” is often the answer people regret.

The job market is different now

A year ago, a senior engineer could get five offers in a week. That’s over, at least for now. Hiring has slowed sharply, there are a lot of talented people looking at the same time, and companies are being much more careful. Expect it to take longer than you’re used to, and don’t take the silence personally.

What still works, and works better than ever:

Your network. In a tight market, most good jobs are filled through someone who knows someone, often before they’re posted. Reach out to former colleagues, former managers, people you helped. Not to ask for a job directly - just to tell them what you’re looking for. Make it easy for them to think of you.

Showing, not telling. A resume says you’re good. A small project, a well-written post about a system you built, or a public repo shows it. Spend some of your free time making one or two things that demonstrate how you think.

Being specific. “Senior full-stack engineer open to opportunities” is invisible. “Backend engineer who’s spent eight years scaling payment systems, looking for a fintech team” is memorable.

Consider the bridge

If the search is taking a while, short freelance or contract work can be a great bridge. It keeps your skills sharp, keeps money coming in, and expands your network. Companies that just went through layoffs often still have work that needs doing - they just can’t add headcount. A senior contractor who can own a project for three months is exactly what some of them need.

Some people try it as a bridge and discover they prefer it.

Lean on other developers

This is why communities like indydevs exist. Other experienced developers will know who’s hiring, who’s legit, which companies are a mess, how to price a contract, and what the market actually looks like this month. And honestly, it helps a lot to talk to people who’ve been through the same thing and came out fine.

It’s going to be OK

I’ve seen a few downturns now. Every single time, the experienced, generous, reliable people landed well - sometimes better than before. The skills that made you valuable didn’t disappear with your badge access.

You were laid off, not let down by your skills. Take a breath, call your people, and go build the next thing.