THE 4 EMAILS
RECRUITERS SEND.

Cold inbound looks the same in your inbox. It isn't. Here are the four distinct emails recruiters send, what each one signals about the role, and the right reply for each.

Every senior candidate gets recruiter email. Most of it looks identical from the outside — a friendly opener, a vague pitch, a calendar link. The differences matter.

Underneath the boilerplate, there are four distinct categories of cold recruiter outreach. Each one signals something different about the role, the recruiter, and how much of your time the conversation deserves. Knowing which one you got tells you whether to reply today, reply with questions, or pass.

Type 1 — The real role

Specific company. Specific team. Specific scope. The recruiter names the hiring manager or at least the function. There's a comp range, even a wide one. There's evidence the recruiter read your background — they reference a company, a project, or a title from your resume.

This email is a real opportunity. Someone has a req open, a budget approved, and a timeline. The recruiter is doing pipeline work, not prospect work. The role exists.

How to respond: Reply within 48 hours, even if the answer is no. If you're interested, ask three sharp questions before the call — level, comp band, who you'd report to. If you're not interested, say so politely and ask them to keep you in mind. Real recruiters remember candidates who replied like a human.

Type 2 — The mass blast

Generic opener. Vague company description ("a Series B fintech"). No named hiring manager. The pitch is a template — the same email went to hundreds of people with your title. There's batch-tooling tells: "your background is impressive," "candidates like you," a calendar link to a 30-minute slot with no context.

Often the role is real. The recruiter just hasn't done the work to vet whether you're a fit before reaching out. They're throwing a wide net and letting you sort yourself.

How to respond: Reply with questions before booking. If they can't tell you the level, the comp range, or who you'd report to, the conversation is going to be a waste of your time. Recruiters who can answer those three questions promptly are doing their job. Recruiters who can't are auditioning for the job. Don't pay them to learn.

Type 3 — The database fishing trip

The email isn't about a specific role. It's about "your goals," "what you're open to," "having a conversation about the market." The recruiter wants to add you to their pipeline, not place you in a job. Tells: contingency-firm language, "I work with companies like X, Y, Z" instead of one specific company, "let's hop on a call to talk through what you're looking for."

The recruiter is harvesting candidate intent. Once you're in their database, they'll pitch you to whatever role they happen to be working on, regardless of fit. Some of those roles will be real. Most won't.

How to respond: Pass. If you're flattered by recruiter attention, get over it — your time is more valuable than the half hour they're asking for. The exception is if they specialize in a sector you're targeting and you want to be on their radar. In that case, ask them to forward roles directly when they come up. Skip the call.

Type 4 — The low-signal lead

The role is real. The fit is wrong. They reached out because your title matches a search query, but the actual role is at a different level, in a different stack, or in an industry you don't want to be in. The recruiter didn't read closely enough to catch the mismatch.

This is the most common type of recruiter email senior candidates get, and it's the most exhausting. It looks legitimate. It can even be from a recruiter you'd want to work with eventually. But the specific role isn't a fit.

How to respond: Reply with a specific reason it's not a fit. Don't ghost — that burns the relationship. A two-sentence "thanks, this is too junior / wrong stack / I'm not relocating" leaves the door open for a future fit and signals you're a thoughtful candidate. Recruiters remember who replies cleanly.

The pattern under all four

The diagnostic is the same regardless of category: how specific is the email about the role, the company, and you?

Real roles are specific. Mass blasts are vague about the role. Database fishing is vague about the role and the company. Low-signal leads are specific but mismatched to your actual background.

Recruiters who respect your time write specific emails. Recruiters who don't, write templates. The reply quality you give back should match the email quality you received.

What's buried in every recruiter email

Even the best recruiter emails leave things out. Comp range below the line. Level ambiguity. The fact that the role has been open for 6 months. Whether the team had three EMs leave last quarter.

Reading a recruiter email well means surfacing what they didn't say. Three questions get you most of the way there:

  1. What's the comp band, end to end? If they only quote a range or "competitive," push for a specific number. The willingness to share is itself a signal.
  2. Why is the role open? New headcount? Backfill? Re-org? "Backfill" with no further detail usually means someone left and they don't want to say why.
  3. Who would I report to and where do they sit on the org chart? The recruiter should know. If they don't, the role was opened recently or the hiring manager is detached from the search. Both are signals about how the process will go.

Get those answers in writing before the call. The half hour you save is the half hour you don't spend learning what you could have asked in two emails.

The fastest read on any inbound

Ari decodes recruiter emails for you. Paste the cold inbound — Ari classifies it, surfaces what's buried, drafts the three questions to ask back, and writes the reply. Free. Decode an email →

The job search rewards the prepared. Knowing which inbound to engage with — and which to pass on — is the most leveraged decision you make every week.

Recruiter decoder

Got a recruiter email?
Decode it.

Paste the cold inbound. Ari classifies the signal, pulls what's buried, drafts the reply. Free.

Decode an email →
← All posts