How to Get Recruiter Replies for Head of Machine Learning Roles: A Cold Outreach Template

A Head of ML cold email that gets replies leads with a business outcome you owned, not a list of models you shipped. Executive search recruiters and hiring VPs skim for signal that you've run a team through ambiguity and produced a number the board cared about. Everything else is noise they'll read later, if at all.

You're not applying for this role. You're being evaluated as a peer before the conversation even starts. That changes the entire outreach playbook.

Why IC-level cold outreach templates fail for Head of ML roles

Most ML cold email templates are written for individual contributors: "I have 5 years of experience with PyTorch and built a recommendation system that improved CTR." That's a resume bullet in email form. It works for a senior engineer role. It gets ignored for a Head of ML search.

Here's why. When a company opens a Head of ML or VP of ML search, they're usually not screening for technical depth alone. They already assume you can build models. They're screening for whether you can hire and retain a team, whether you've navigated a build-vs-buy decision under budget pressure, and whether you've sat in a room with a CEO and defended an ML roadmap when it wasn't converting fast enough. An email full of framework names signals you haven't done that yet.

In short: IC outreach sells skills. Executive outreach sells judgment.

What recruiters actually look for in ML leadership cold outreach

Talk to anyone who's run technical executive search and you'll hear the same pattern: they read the first two lines, then jump straight to "what did this person's team ship, and what happened to the business because of it." Not what algorithm. What outcome.

Three things get weighted heavily in that first scan:

• Team size and scope — did you manage 3 engineers or 30, one pod or a whole ML org spanning research and platform
• P&L or budget proximity — did you own a cost center, influence a revenue line, or just execute someone else's roadmap
• A named, checkable result — a product launch, a cost reduction, a retention lift, something a reference can confirm in one sentence

If your draft doesn't hit at least two of these in the opening paragraph, rewrite it before you send anything.

Plain-language summary

Executive recruiters don't scan for tech stacks. They scan for team scope, budget ownership, and one result someone else can verify.

The executive-level cold email template for Head of ML roles

Use this as a skeleton, not a script. Swap in your specifics and cut anything that doesn't survive a hard edit. Executive emails are shorter than people think, usually under 150 words in the body.

Subject: ML leadership at [Company] — quick note

Hi [First Name],

I lead the ML org at [Current/Recent Company], where I grew the team from [X] to [Y] and moved [specific metric] by [outcome, described qualitatively if you don't have an exact verified number] after we rebuilt our [system/pipeline/model class].

I saw [Company] is scaling [specific initiative, product line, or the open role itself] and wanted to reach out directly rather than go through the standard queue. My background is [1 sentence: research-to-production, platform-to-applied, or infra-to-model, whichever is true].

Open to a short call if the timing works on your end. Happy to send my deck on how I structured the last team if useful before that.

[Your name]
[LinkedIn] · [Portfolio or GitHub if relevant]

Notice what's missing: no bullet list of frameworks, no "I'm passionate about AI," no attached resume in the first touch. At this level, the email itself is the writing sample. If it's tight and confident, that's already a data point about how you'll communicate to a board.

How to structure the first line so a recruiter keeps reading

The subject line and first sentence do the heaviest lifting. Follow this order every time:

1. State your current scope in one clause — team size, function, company stage. Not your job title alone; titles are inflated everywhere, scope isn't.
2. Attach one result to that scope — a metric, a launch, a cost outcome. Keep it qualitative if you can't cite an exact number you're confident defending under questioning.
3. Name the reason you're writing to this specific company — a role they posted, a product launch, funding news, a technical blog post their team published. Generic outreach reads as mass-blasted, and executive recruiters can tell in one line.
4. Make the ask small — a short call, not "let's discuss the opportunity." Big asks feel like you're selling yourself; small asks feel like you're already operating as a peer.
5. Close with proof of seriousness — an offer to send more detail (a team structure, a case study, a one-pager) rather than dumping it all upfront.

Plain-language summary

Scope first, result second, reason-for-this-company third, small ask fourth, optional proof last. In that order, every time.

What to change when reaching out to a founder vs. a recruiter vs. a VP

The core template holds, but the emphasis shifts depending on who's on the other end.

Sending the same email to all four is the fastest way to get filtered out by at least two of them. A five-minute customization pass on the opening line is worth more than a longer email sent to everyone unchanged.

How many follow-ups before you stop and what to say in them

Executive inboxes are busier than IC recruiter inboxes, but the etiquette is stricter, not looser. A good rhythm:

1. Send the initial email using the template above, personalized to the recipient type.
2. Wait roughly a week. Executive schedules move slower than IC hiring cycles; a fast non-reply usually means it's genuinely buried, not ignored.
3. Send one follow-up that adds new information instead of just "checking in" — a relevant article, a metric you clarified, a mutual connection you found.
4. Wait another one to two weeks before a final, short close-out message that removes pressure: "No worries if the timing isn't right, happy to reconnect down the line."
5. Stop after that. A third chase reads as desperate at this level and can quietly hurt you if the recruiter resurfaces the role in six months.

The close-out message matters more than people think. It's often what gets forwarded internally when the role reopens later, because it reads as low-pressure and confident rather than needy.

How this connects to your broader ML leadership job search

A great cold email gets you a reply. It doesn't get you past the interview loop, which for Head of ML roles is its own animal, heavy on org design, hiring philosophy, and how you'd defend a roadmap under pressure. If you're prepping for that stage, our breakdown of Head of Machine Learning interview questions covers what actually gets asked once the reply comes in.

Outreach at this level is also a volume-and-precision problem at the same time: you need enough well-targeted sends to generate a pipeline, but each one has to be tailored enough that it doesn't read like a mail merge. That's the same tension IC candidates face with application volume, just at a smaller, higher-stakes scale, something we've written about for researchers moving out of academia in our postdoc-to-industry outreach template.

GiraffyReach's recruiter outreach engine was built for exactly this kind of targeted, high-signal sending: it tracks who opens, who forwards internally, and when to follow up, so you're not guessing at timing on a search that can take months. If you're running an executive-level job search alongside a full-time role, that kind of tracking is the difference between a template that sits in a drafts folder and one that actually turns into calls. Explore it at GiraffyReach.