Skip to main content
Corey Daley

Four Months Into a New Job, and the Recruiters Never Stopped Calling

· 5 min read · Corey Daley

The recruiter messages never slowed down.

I started a new job about four months ago. It’s going well, I’m not looking, and my LinkedIn profile says exactly how long I’ve been there — the start date is right at the top of my experience section, doing the math for anyone who cares to check. None of that changed the tempo of my inbox.

Not spam, either — some of it is the usual keyword-matched boilerplate, but a decent chunk is clearly a human who looked at my profile, saw the stack I work on, and decided I was worth a personalized message about a role they’re filling. Which means they also saw the part where I started this job in the spring.

And that’s the thing I keep turning over. Because from where I sit, there’s an asymmetry here that I can’t quite square, and I’d genuinely like someone on the recruiting side to explain it to me.

The asymmetry

Every engineer who’s been through a few hiring loops knows the rule: short stints on your résumé are a liability. Two or three roles under a year and you can feel the question coming before the screen even starts — “So, tell me about your time at…” Hiring managers read short tenure as risk. Recruiters know they read it that way, because recruiters are the ones who have to present the résumé and pre-empt the objection.

So the same industry that treats “left after six months” as a yellow-to-red flag on paper is also comfortable sending me a note that says: hey, you’ve been there four months — want to leave?

If I said yes, I’d become exactly the candidate that same recruiter would have to apologize for on the other end — “he’s great, don’t worry about the four-month stint he’s about to create by taking your offer.” The outreach only converts if I’m the kind of person who’d abandon a new job for a cold message, and that kind of person is a flight risk for the very role being pitched. The message is fishing for a quality that, if found, should disqualify the catch.

The explanations I can come up with

I’ve tried to steelman this from the recruiter’s side, and I can construct a few theories. I just don’t know which of them, if any, is the real one.

It’s a numbers game, and tenure isn’t in the filter. Sourcing tools let you slice by title, skills, location, company — and maybe time-in-role just isn’t a field anyone bothers to exclude on. If outreach is cheap and volume is the strategy, filtering out recent starters costs pipeline for a nuance most candidates will self-select on anyway. The four-month people simply don’t reply, and the funnel sorts it out.

The outreach isn’t really for now. Maybe the message isn’t “leave your job” so much as “let me introduce myself so that in eighteen months, when you are looking, I’m already in your inbox.” Pipeline building dressed up as a live req. If that’s the model, my current tenure is irrelevant — they’re planting a flag, not making an offer.

Tenure gets judged later, by someone else. The recruiter’s job is to fill the top of the funnel; the hiring manager’s job is to worry about flight risk. A recruiter who screens out short-tenure candidates is doing the hiring manager’s filtering for them, unpaid, at the cost of their own pipeline. Structurally, nobody at the outreach stage is incentivized to care.

A reply is the actual filter. This is the most interesting theory to me: maybe the outreach is the tenure test. Anyone who responds enthusiastically four months into a job has revealed something — that they’re unhappy, that they’re a chronic jumper, or that the market has repriced them and they know it. The recruiter learns more from the reply than from the profile. The message isn’t ignoring the red flag; it’s hunting for it.

One jump isn’t a pattern. Maybe I’m overweighting how bad a single short stint actually is. A résumé with five of them tells a story; a résumé with one, followed by a better role, mostly doesn’t. Recruiters may reasonably model “poachable at four months” as a one-time event — from their side of the table, they caused the short stint, and the next employer never has to know it was a cold DM that did it.

Each of these is plausible. Some of them are probably true simultaneously. But they’re all guesses from the outside, and the people who actually know are the ones sending the messages.

So, recruiters: I’m actually asking

This isn’t a complaint dressed up as a question. The outreach is flattering, mostly polite, and occasionally interesting. I’m asking because I think the answer would tell engineers something real about how the sourcing machine actually works.

If you source candidates for a living:

  • Is time-in-current-role part of your search criteria at all? Do you ever exclude people under six months, or a year? Is that even a supported filter in the tools you use?
  • When someone four months into a job replies with interest, what do you actually think? Green flag or red flag?
  • Do hiring managers ever push back when you present a candidate who’d be leaving a brand-new role? Or does nobody ask how the sausage was sourced?
  • Is the eighteen-month pipeline theory real? When you message someone who obviously just started, are you recruiting them for this req, or for a future one?

I suspect the honest answer is unglamorous. But I’d rather hear it from the people doing the work than keep reverse-engineering it from my inbox.

Recruiters: when you message someone four months into a job — and their profile told you it’s been four months — what are you actually hoping their reply reveals?