Recruiter Outreach: A Complete Guide for Senior Professionals

At senior level a large share of hires happen through people. A posting may exist, but by the time it is public a shortlist often already exists alongside it.

That makes outreach one of the highest-leverage activities in a senior search, and it is the one most people do worst — usually because they are treating three quite different roles as one.

Three kinds of recruiter

Internal recruiters

Employed by the company. They fill that company's roles and nobody else's. They are measured on time-to-fill and quality-of-hire for a specific requisition list.

What they want: candidates who match an open requisition they are working on right now.

What that means for you: be specific and be timely. An internal recruiter with no matching requisition has nothing to do with your message, however impressive you are. The same message six weeks later, when a requisition opens, would have worked.

They are also the best route into a company you specifically want, because they know what is opening before it is posted.

Contingency agency recruiters

Paid a fee by the employer only if their candidate is hired. Typically working many roles at once, often the same roles as competing agencies.

What they want: placeable candidates, quickly.

What that means for you: they will be responsive when you match something live, and quiet otherwise. That is not rudeness; it is the economics. They are also incentivised toward volume, which means a candidate can be submitted to more places than they intended.

Be explicit that you want to approve every submission before it happens. A good agency recruiter will agree without friction. One who resists is telling you something.

Retained executive search consultants

Engaged and paid by a client company to run a specific search, whether or not it results in a hire. They work a small number of mandates at a time, deeply.

What they want: to build a map of a market so that when they are engaged on a search, they already know who the credible candidates are.

What that means for you — and this is the most misunderstood point in senior job searching: a retained consultant cannot place you in a role they are not working on. They have a handful of active mandates. Asking "do you have anything for me" is asking a question they almost always have to answer no to.

The productive approach is entirely different. You are not asking for a job. You are making yourself known as a credible operator in a specific domain, so you are on the map when a relevant mandate arrives. That conversation is worth having when you do not need anything, and it pays off eighteen months later.

Finding the right person

Specificity beats volume here even more than elsewhere.

For a target company: find the internal recruiter or talent partner who covers your function. A recruiter who covers sales cannot help with an engineering role and will not forward it usefully.

For a sector: identify the search firms that repeatedly place at your level in your industry. Look at who ran searches for comparable roles at comparable companies. Sector specialisation is real and it matters.

Signals a contact is worth approaching: they have posted or placed roles at your level, in your function, recently. Someone who places individual contributors is not the route to a VP role.

A short list of well-chosen contacts outperforms a long list every time. Twenty relevant people is a real campaign. Two hundred scraped addresses is a spam run that will be treated as one.

What to send

The structural problem with most outreach is that it makes the reader do the work — figure out who this is, what level they operate at, and what they want. A recruiter reading fifty messages will not do that work. They will move on.

Subject line

State the thing. Director of Engineering — platform / infra, Boston beats Exploring opportunities or Introduction.

First two lines

Who you are and what scope you operate at. Concretely.

I run a 40-person platform organisation at a Series D fintech, owning developer infrastructure and CI for around 300 engineers.

That single line does more than three paragraphs of adjectives. It tells the reader your level, your domain, and your context — the three things they need to decide whether to keep reading.

The evidence

One or two specifics, chosen for relevance rather than impressiveness. A number you can defend. A named constraint you worked under. Something that would be hard to say if it were not true.

The ask

One ask, and make it easy to answer.

For an internal recruiter, that is usually a specific role: I saw the Director of Platform role posted last week — is that still open, and is my background in range?

For a retained consultant, the ask is not a role. It is a conversation: I'm not urgently looking, but I'd value being on your radar for platform leadership mandates in fintech. Worth a short call?

For an agency recruiter: Are you working anything at this level in this space? Happy to send a resume if useful.

Length

Under 150 words. Every additional paragraph reduces the chance any of it is read.

What fails

No specific ask. "I'd love to connect and explore opportunities" gives the reader nothing to do. They cannot answer it, so they do not.

A resume with no message. An attachment and one line of text is a filing task, not a conversation.

Obvious templating. Dear [Recruiter], I was impressed by your work at [Company] — the mail-merge tell is unmissable and it says you did not spend thirty seconds on this.

Asking a retained consultant for a job. Covered above, and worth repeating because it is so common.

Length. Six paragraphs of career narrative is a document, not an approach.

Volume. Identical messages to fifty people at the same firm. They talk to each other, and it lands as spam because it is.

Vagueness about level. "Senior leadership roles" spans a fifteen-person team and a fifteen-hundred-person organisation. If you do not state your scope, the reader guesses, and the guess is not usually generous.

A worked example

What most people send:

Subject: Introduction

Hi Sarah,

I hope this email finds you well. I came across your profile and was impressed by your work in the technology recruitment space.

I am a seasoned engineering leader with over 15 years of experience building and scaling high-performing teams. I have a proven track record of delivering results in fast-paced environments and am passionate about developer experience and organisational excellence.

I am currently exploring new opportunities and would love to connect to discuss how my background might be a fit for roles you are working on. I have attached my resume for your reference.

Looking forward to hearing from you.

Nothing here is wrong, and nothing here is usable. The subject says nothing. The first paragraph is filler. The second could describe several thousand people and states no level, no domain, and no scope. The ask is "connect", which is not an action anyone can take. The reader has to do all the work, so they do none of it.

What works:

Subject: Director / VP Platform Engineering — fintech, Boston or remote

Hi Sarah,

I run a 45-person platform organisation at a Series D fintech — developer infrastructure, CI, and internal tooling for about 300 engineers. Before that I led infrastructure at a payments company through a migration off a monolith.

I saw you placed the VP Infrastructure role at Brightline last year, so platform leadership in fintech looks like your patch.

I'm not in a hurry, but I'd like to be on your radar for mandates at that level. Worth a fifteen-minute call in the next few weeks? Happy to send a resume if that's more useful first.

Ben

Ninety-eight words. The subject is a filter the reader can act on in one second. The first two lines establish level, domain, and scale. The third line proves this is not a mail merge and shows why this recipient. The ask is small, specific, and answerable with one word.

The final line matters more than it looks: offering the resume rather than attaching it converts an attachment into a reply.

When a recruiter approaches you

Most senior professionals receive inbound approaches regularly and handle them badly — usually by ignoring the ones that are not immediately relevant.

That is a mistake, because the cost of a good reply is about ninety seconds and the asset it builds compounds.

If it is genuinely irrelevant, decline warmly and leave the door open. Thanks — not the right fit for me, I'm focused on platform leadership at Series C and up. Happy to hear from you if something in that space comes up. That one sentence converts a dead approach into a correctly-calibrated contact who now knows what to send you.

If it is close but not now, say exactly that with a timeframe. Not looking right now, but I expect to be open around Q2. Worth reconnecting then?

If it is interesting, ask three questions before anything else: who is the client, what is the scope, and what is the compensation band. A recruiter who cannot answer the first is working contingency on a role they may not have a relationship with. One who will not discuss the third is wasting a process on both of you.

Never ignore an approach from someone you would want to hear from later. Silence is read as unavailability, and you are quietly removed from a list you would rather be on.

Timing and follow-up

One follow-up. Roughly a week later, short, adding something rather than repeating: a new piece of context, a specific role that has since been posted. Following up on the below adds nothing.

Then stop. A third and fourth message do not convert; they change how you are perceived. Silence is usually about their requisition list, not about you.

Reconnect on a real trigger. A relevant role posted, a funding announcement, a move you noticed. I saw you're building out the platform team — I'm the person I described in March is a reasonable message six months later. A generic check-in is not.

Building the relationship before you need it

The uncomfortable truth about senior job searching is that the highest-value outreach happens when you are not looking.

A conversation with a retained consultant while you are happily employed is an easy conversation. There is no urgency, no need to impress, and no pressure on either side. You are a credible operator describing your domain. That is exactly the position from which they want to know you.

The same conversation while unemployed and six months in is harder for reasons that have nothing to do with your ability.

Practically: two or three conversations a year with people who cover your sector. Answer approaches even when you are not looking — a polite decline that leaves the door open costs five minutes and keeps you on the map.

LinkedIn or email

Both, in a specific order.

LinkedIn is better for the first touch with someone you have no connection to. The context is already there — they can see your background in one click without you having to establish it — and a connection request with a short note is a lower-imposition opening than an unsolicited email.

Its weaknesses are real though. InMail and connection notes are heavily truncated, recruiter inboxes there are saturated, and messages are easy to lose. Treat it as an opener, not a channel for anything substantive.

Email is better for anything that matters: a genuine approach, a follow-up, materials, scheduling. It is searchable, it threads, it does not disappear behind a notification counter, and it reaches someone who is actually working rather than browsing.

The sequence that works: connect on LinkedIn with a two-line note, then move to email once there is any reciprocation. If you can find the address directly and the approach is well-targeted, going straight to email is fine — well-targeted being the operative condition.

One thing not to do: send the same message on both channels the same day. It reads as pressure, and it is noticed.

Mechanics that actually matter

A few unglamorous things that determine whether your message is read at all.

Send from a real address. A personal address you actually monitor. Messages from an address you never check are worse than not sending, because the reply arrives and dies.

Plain text over heavy formatting. Images, tracking pixels, and multi-part HTML raise spam scores and add nothing. A plain message from a normal account reaches the inbox.

Do not send in bulk from a personal account. Fifty near-identical messages in an hour from a personal Gmail account is a deliverability problem and an account-standing problem. Send fewer, spread out, genuinely varied.

Attachments. Offer the resume rather than attaching it cold. Unsolicited attachments are filtered more aggressively, and "happy to send my resume" invites a reply — which is the point.

Check the name. The single most damaging error available for the least effort.

Templates or writing

A reasonable middle position: keep a structure, not a script.

The structure is stable — subject states the role and level, first two lines state scope and domain, one or two pieces of evidence, one clear ask, under 150 words. That does not need reinventing.

What changes every time is the content: which evidence is relevant to this reader, what the ask actually is, why this company or this sector. That is the part that cannot be automated, because it is the part being evaluated.

Software drafting a starting point from your profile and the target is useful. Software sending it without you reading it is a mistake, for the same reason discussed in the application automation guide: outreach at senior level is a sample of your judgement.

Where PlaceMeFast fits

PlaceMeFast finds recruiter and company contacts relevant to a role, drafts outreach messages and cover letters from your profile and the specific job, and — if you choose to connect a Gmail account — can send them from your own address so replies come back to you.

Connecting Gmail is opt-in and off by default. Nothing is sent that you have not seen.

It covers U.S. searches only and is not publicly available yet. It helps you find the right person and draft a starting point; the judgement in what you actually say stays yours, which is the only arrangement that works here.

Join the early-access list to hear when it opens.