Headhunter vs Recruiter: What the Difference Means

“Headhunter” and “recruiter” get used interchangeably, including by the people doing the work. Neither is a protected term and neither maps cleanly onto a job description.

But there is a real distinction underneath the vocabulary, and it is not the one most explanations reach for. It is not about seniority, and it is not about who is more professional. It is about whether the person you want is currently looking for a job — because that single fact changes the entire shape of the work.

The distinction worth drawing

Recruiting, in the general sense, works the responsive market. Applications, inbound interest, a database of people who have engaged before, referrals from people who know someone open to a move. The core skill is throughput and judgment: assessing many people accurately and moving them through a process without losing them.

Headhunting works the non-responsive market. Nobody applied. The work starts with a question: who could do this job? The people who answer it may have no idea the role exists and no intention of leaving. The core skill is identification and approach: working out who those people are from sources never created to help you find them, then making a conversation happen.

Everything else follows. Headhunting is slower, more expensive per hire, and usually engaged on a retainer rather than paid on placement, because the work happens before anyone knows whether a hire will land. Recruiting can be paid on outcome because the pool already exists.

Why the terms blur

Three reasons, all legitimate.

The same person often does both. A recruiter at a boutique firm may run a responsive process for one role and a genuine search for another in the same week.

The words carry different weight in different markets. In some places “headhunter” reads as slightly disreputable; in others it is simply the ordinary term for the job. Firms pick the label their clients respond to.

And the middle is genuinely blurry. A search that starts with a database query and ends with three cold approaches is doing both, and there is no useful line to draw through it.

So do not treat the title as a specification. Treat it as a hint about which market the person is set up to work, and check.

What actually changes when the pool is not looking

Identification becomes the work. In a responsive process, finding people is close to free — they came to you. In a search, everything before the first conversation is effort: mapping which companies produce the profile, working out who sits in those seats, reaching one sector over to where the job is functionally the same under a different industry label.

Evidence gets harder. Someone applying for a job hands you a document about themselves. Someone who is not looking has no reason to have one, and the record is whatever the public world happens to hold — announcements, filings, conference programs, an unmaintained profile. Reconstructing scope from those sources is a different skill from reading a CV.

The approach carries risk. A cold conversation with a sitting executive about leaving their job is confidential in a way an application never is. Handled badly, it costs the candidate something real.

Timelines stretch. Not because anyone is slow, but because you are asking someone to consider a change they had not been considering.

The seniority assumption, and why it misleads

The usual shorthand is that headhunters do executive roles and recruiters do everything else. It is roughly true and it misleads in both directions.

Plenty of senior roles sit in visible, mobile markets where a responsive process works perfectly well. And plenty of non-executive roles — a specialist engineer in a field with few practitioners, a regulatory lead with an unusual combination of exposure — are genuinely search problems, because the handful of people who qualify are employed and not looking.

Seniority correlates with search. It does not define it. The thing that defines it is whether the people you want will ever raise their hand.

The question is never how senior the role is. It is whether the person you want has any reason to be reading job listings.

The question worth asking instead

Rather than asking whether someone is a headhunter or a recruiter, ask what they will do in the first two weeks.

If the answer describes posting, screening inbound interest, and working an existing database, that is a responsive process: useful, often the right tool, and priced accordingly.

If the answer describes mapping which companies produce the profile, identifying who currently holds those seats, and approaching people who have not asked to be approached, that is a search — and it is worth understanding how the firm actually runs it before you commit.

Related reading: retained versus contingency search, how executive search researchers find candidates, and what active sourcing actually means in executive recruitment.