TL;DR / Key Takeaways

Modern layoffs happen fast, scripted, and remote, and the access revocation hits before the call ends.
Thirty years of institutional knowledge means nothing to a company running a headcount reduction.
The moment your professional identity gets revoked by someone reading from a document is the moment you understand why building something you own matters.
Predict & Profit exists partly because of this exact realization: code you own can't be taken away on a Tuesday morning.

I have not been laid off. I want to be clear about that upfront.

But I have watched it happen. Up close. To people I worked alongside for years. And I have sat in enough reorgs, enough "strategic realignments," enough all-hands meetings with that particular energy in the room, to know exactly how it goes.

And here is the thing: watching it happen to someone else is almost worse. Because you see the whole machinery of it clearly.

The Call Itself

It comes with no warning. Or rather, it comes with all the warnings you trained yourself to ignore.

The calendar invite shows up the night before or early that morning. No agenda. Organizer is someone from HR you have never spoken to directly, plus your manager, plus someone above your manager. The meeting is thirty minutes. Thirty minutes is the tell. A real one-on-one is fifteen. A project sync is an hour. Thirty minutes is exactly long enough to deliver news, answer three questions, and end the call before things get emotional.

You join. You see the grid. HR is already on, camera off. Your manager looks like they have not slept well. The senior person above them is there to make it feel official.

Someone starts reading.

Not speaking, reading. There is a script. There is always a script, because the company's legal team reviewed every word of it and HR rehearsed the delivery. The words are careful. "Position elimination." "Restructuring." "We value your contributions." The phrases are chosen specifically to be compassionate-sounding and legally airtight simultaneously.

You stop hearing the words after the first sentence. You already understood.

The Access Goes First

This is the part nobody warns you about.

Before the call ends, sometimes before it ends, your badge stops working. Your email starts bouncing. Your Slack goes read-only and then goes nothing. Thirty years of emails, documents, code commits, architecture diagrams, project notes, all of it becomes inaccessible at a timestamp that was set before you even joined the call.

The company is not being cruel. They are following procedure. They have had people go rogue before. They have seen what a disgruntled employee with admin access can do in twenty minutes. The access revocation is policy.

But knowing it is policy does not make it feel less like having your hands cut off.

You are still on the call. HR is explaining COBRA. Your manager is saying something about being available as a reference. And somewhere in a data center you have never seen, a script ran your employee ID through a deprovisioning workflow and you are already gone.

What Gets Taken

The paycheck is obvious. That is what everyone focuses on in the first hour. The paycheck and the benefits and the logistics of what comes next.

But that is not actually what hurts most.

What hurts is the identity.

After thirty years in this industry, a significant part of who you are is what you do. Senior Data Engineer. Platform Architect. The person who fixed that production incident at 3am in 2019. The person who mentored three junior engineers who are now leads themselves. The person who knew where every skeleton was buried in that codebase because you helped bury some of them.

All of that exists in your head and nowhere else. The company did not take your knowledge. They just stopped paying for access to it.

But it does not feel that way. It feels like erasure.

The LinkedIn Post

Three days later, sometimes two, you write the post.

You have read enough of them to know the format. "After X years at Company, I am excited to announce that I am exploring new opportunities." You talk about the journey. You thank your colleagues. You end with something about being open to conversations.

The post gets four hundred likes. Mostly from people you have not spoken to in years. Three or four genuine messages from people who actually care. The rest is the LinkedIn algorithm treating professional grief as engagement content.

Recruiters start appearing in your inbox, most of them for roles two levels below where you were, most of them clearly automated.

You feel simultaneously supported and completely alone.

What It Teaches You

I am going to say something that is going to sound obvious once I say it, but it took me a long time to actually feel it rather than just understand it intellectually.

You cannot own your job.

You can be excellent at it. You can be indispensable, or feel indispensable, which is not the same thing. You can build institutional knowledge that takes years to replace. You can care deeply about the work and the people and the product.

None of that is equity. None of it is yours.

The company owns the output. The company owns the codebase. The company owns the relationships with customers and vendors. You own your skills and your experience and your reputation, and those are genuinely valuable, but you cannot take them to market at 9am on a Tuesday without going through another interview process that may take six months.

The asymmetry is brutal. You give thirty years. They give you thirty minutes.

What You Can Own

Code you write on your own time, on your own machine, for a product you control.

That is not a new idea. But I think the layoff moment is when people finally feel the weight of it rather than just nodding at it.

I built Predict & Profit while working full time. I built it on evenings and weekends in Atlanta, usually with a kitten on my lap and something quiet on in the background. I built it because the engineering problems were interesting and because I was tired of the only thing I had to show for a week of work being a Jira ticket moved to Done.

But I also built it because I understood, somewhere underneath everything, that I wanted something that could not be deprovisioned.

The bot runs on my server. The code is in my repo. The product is on my Gumroad account. If my employer calls a thirty-minute meeting tomorrow morning, the bot keeps running. The revenue keeps depositing. The thing I built does not care about the org chart.

That matters to me in a way I could not have articulated at thirty but can articulate clearly at sixty.

The Skills Are Yours

Here is what I tell anyone going through it, or watching it happen to someone they know.

The company took the job. They did not take what you learned doing it.

Thirty years of debugging production systems teaches you something. Thirty years of building things that have to actually work, not just pass code review, but survive real load and real users and real edge cases, that is portable. That lives in you.

The question is whether you are going to sell that knowledge to the next employer in another thirty-minute interview, or whether you are going to point it at something you own.

Both are valid choices. I am not here to tell anyone what to do with their career.

But I know which one I chose. And I know why.

The layoff on a Teams call is not the end of a career. It usually is not even the worst thing that has ever happened to the person sitting in that grid.

What it is, if you let it be, is a moment of clarity. The contract was always temporary. The identity was always borrowed. The only thing that was ever really yours was what you knew how to build.

Go build something.

The Layoff That Came on a Teams Call