← All posts

Pursuit blog

Your recruiter just got laid off

When your process goes silent, the reason may have nothing to do with you.

The screen went well. You know it went well — you could hear it in the pauses, the way she stopped selling the company halfway through and started asking what you’d want your first ninety days to look like. She said the team was moving fast. She said she’d come back to you early the following week.

That was three weeks ago.

You have already run the standard diagnostic. You have reread your thank-you note looking for something graceless. You have decided the answer is no and they’re being cowards about it. You have decided the answer is yes and there’s a comp approval stuck somewhere. You have refreshed an inbox that has nothing in it.

Here is a possibility that probably hasn’t occurred to you, because it has nothing to do with you: she doesn’t work there anymore.

Recruiting goes first

This isn’t cynicism, it’s arithmetic. A recruiting team is sized to hiring volume. Ten open roles need a certain number of recruiters, coordinators, and sourcers to run them. When a company decides to stop hiring — which is the first decision in nearly every cost reduction, and usually happens weeks before anything is announced — the recruiting function is instantly overstaffed by definition. It isn’t a judgment about the people in it. The work they were staffed against stopped existing.

So talent acquisition tends to get cut early, cut deep, and cut quietly, because a company announcing a workforce reduction has more urgent things to put in the press release than the fate of its sourcing team.

The consequence for you is specific and badly understood: the person carrying your candidacy is often the person with the least job security in the building. Not the hiring manager, who has a team to run either way. Not the engineers who interviewed you. The recruiter — your only real point of contact, the one who knew you were competitive, who had the context on why the loop ran long, who was going to walk your case into the debrief.

She’s gone, and your file is sitting in an applicant tracking system that recorded every stage you passed and none of the reasons.

First, work out whether it’s slow or dead

You can’t always tell, but you can do much better than guessing. Run these in order; the first two cost you almost nothing.

Send one email and watch for a bounce. If a message to her work address comes back undeliverable, she’s off the domain. That is the clearest signal you will ever get about anything in a job search, and it takes ninety seconds.

Check whether the posting is still live — then whether it was reposted. A role that vanished from the careers page is frozen or killed. A role taken down and posted fresh a week later usually means the process restarted under someone new, which is annoying but survivable, and very much worth knowing before you write anyone off.

Look at LinkedIn once. Not daily. You want one of three things: a farewell post, an “open to work” banner, or a current-company field that no longer says the company. Any of them answers the question.

Read silence carefully. Two weeks past a promised date means something has gone sideways in their process. It does not tell you what. People miss timelines constantly for reasons unrelated to you: the panel can’t get a debrief on the calendar, the approval chain grew a link, someone’s on leave.

Then go around, carefully

If you have reason to think your contact is gone, the instinct is to reapply through the portal. Don’t bother. If the req is frozen, the portal is a filing cabinet with nobody standing next to it.

The durable contact is the hiring manager. They were there before recruiting got involved and they’ll be there after. If you got past a screen, you’ve probably met them — that’s your door.

The note should be short, shouldn’t mention layoffs, and shouldn’t ask anyone to explain themselves:

Hi Marcus — I interviewed for the platform engineering role in June and really enjoyed our conversation about the migration. I haven’t been able to reach Priya, so I wanted to check in directly: is that search still active? Happy to pick it back up whenever the timing works.

Three sentences. You’ve given them an easy out (“it’s on hold”) and an easy yes, and you haven’t made them manage your feelings about a process that isn’t their fault either.

If you never met the hiring manager, work with whoever else touched the loop — a coordinator who scheduled you, a peer interviewer, anyone whose name you have. Their job isn’t to advocate for you. Their job, if they’re decent, is to tell you whether the thing is alive, and most people will.

Send it once. Then stop. A second follow-up a week later is fine; a third is you negotiating with your own anxiety in someone else’s inbox.

Write down what only you can keep

This event is expensive because it destroys context that lived in exactly one place. She knew why you were strong. She knew what you’d said about compensation. She knew the loop ran long because of a scheduling problem and not because of you. When she goes, all of it goes — and if the search restarts, you begin again from a résumé and a stage label.

You can’t prevent that on their side. You can refuse to let it happen on yours.

For every live conversation, keep the name and title of everyone you’ve spoken to, not just the recruiter. The date of last contact and what was actually promised, in their words. What you told them about your timeline and your number, because a new recruiter will ask you all of it again from scratch, and you want to answer in August the way you answered in May.

Then move the role to stalled — not rejected, not active. It’s a real state and it deserves its own line, because the thing you’re deciding is not whether they liked you. It’s how much of this week’s attention it still gets.

What’s yours, and what isn’t

Anxiety is an excellent pattern-matcher and a terrible analyst. It takes silence and produces a story, and the story is always about your inadequacy, because that is the only story it knows how to tell.

There’s a much older idea that cuts the problem differently. The Gita puts it roughly as this: you have a right to your actions, and no right at all to their fruits. Do the work because it’s yours to do, and hold the result loosely, because the result was never in your hands to begin with. A hiring plan cancelled in a finance meeting you’ll never hear about is as good an illustration of that as anything. What is meant for you is not lost because someone else’s job was.

But that belief only earns its keep when it’s carrying its other half. Trusting that things resolve is not a reason to skip the email. It’s what makes the email possible to send — without the desperation in it, without needing the reply to mean something about your worth. The effort is the part you owe. The outcome belongs to a system with more moving parts than you can see.

So: send the note. Write down the names. Give the stalled role the attention it actually merits and not one hour more, and spend the rest on the four conversations still moving.

Then let it go, which is not the same as giving up. It’s the recognition that you have already done the part that was ever yours.


Pursuit keeps the people, not just the stages — every contact, company, and conversation in one place, so a search survives the parts of it you don’t control.