Prospecting playbook · Updated September 28, 2026

How to prospect engineering leaders on LinkedIn

Engineering leaders are the most outreach-averse buyers on LinkedIn. Many barely check it, and the rest have a folder of unread vendor notes. What reaches them is a note that is short, technically literate and about something they actually wrote, such as an incident, a migration or a hiring post.

Who to target

Software companies of roughly 20 to 1,000 people. At the low end the CTO buys, and at the high end a platform team does.

Titles to search

CTOVP EngineeringHead of EngineeringDirector of EngineeringEngineering ManagerHead of PlatformHead of Infrastructure

Skip these, they only look the part

  • Developer advocates and devrel, who post constantly and do not buy.
  • Engineering recruiters.
  • Fractional CTOs and dev-shop owners, unless agencies are your market.
  • Individual engineers, unless you sell a tool engineers adopt bottom-up.

Where engineering leaders show up

Ranked for this audience, best first. Each one is a source an outreach agent can watch.

  1. 1

    Keyword posts

    Engineering leaders writing about incidents, migrations, on-call load, build times and cloud costs.

    Technical posts are specific by nature, so they make the best openers.

  2. 2

    Buying events

    New CTOs and VPs of engineering, fast engineering hiring, and recent funding.

    Engineering leaders post rarely. Events catch the ones who do not.

  3. 3

    Competitor engagement

    People engaging with competitors’ technical posts and launches.

    Engineers comment on tools they are evaluating, sometimes bluntly.

  4. 4

    Creator audiences

    Comment sections of respected engineering-management writers.

    Good source of managers and directors. Qualify on company size.

Words they actually post

Watch posts that use the words engineering leaders use for their own problems, not the words vendors use to sell to them. The author of a post like that is usually the buyer. The commenters under a vendor post usually aren’t.

postmortemon-callplatform teamKubernetes migrationcloud costsCI build timesdeveloper experiencetech debt

Timing: which buying events matter

Buying events are public and dated. They say when a person or a company is likely to buy, but not what they want to buy.

Job change

Strong

A new VP Engineering or CTO revisits tooling and platform choices in the first months.

Hiring

Strong

Hiring many engineers at once strains onboarding, CI and on-call.

Funding

Useful

Funding often pays for platform work that was deferred.

Three connection notes that fit

Each one cites something true about the person, stays under LinkedIn’s 300-character limit and leaves out links. When there is nothing to cite, say how you found them. Don’t invent a reason.

After: They wrote a public postmortem
“Hi Arjun, your write-up of the queue backlog incident was unusually candid, especially the part about the alert that fired and nobody owned. I work on on-call tooling. Would be glad to connect.”

193 / 300 characters

After: Their team is hiring 12 engineers
“Hi Clara, saw the team is hiring twelve engineers this quarter. Onboarding usually hurts at that pace, with CI and review queues first. I work on that part. Happy to connect.”

174 / 300 characters

After: They posted about cloud costs
“Hi Felix, your post about the cloud bill that doubled from one misconfigured log pipeline got a laugh and a wince from me. I build cost tooling for platform teams. Would be good to connect.”

189 / 300 characters

What doesn’t work

  • Marketing language. Engineers read words like “revolutionary” as a warning.
  • Pitching engineering managers on tools that need VP sign-off.
  • Asking for a demo in the note.

Questions

Do engineering leaders respond to LinkedIn outreach?

Less than most buyers, which makes targeting matter more. Reach the ones who post, write about what they posted, and leave out the ask.

Should I target the CTO or the VP of Engineering?

At under 50 people, the CTO. Above that, the VP of Engineering or the head of the platform team usually owns tooling decisions.

What is the best signal for engineering leaders?

A technical post about a problem you solve. Failing that, a new role or a big hiring push.

Run this playbook as an agent

Paste your website and rivomi drafts the segment for you. An agent then watches these sources for engineering leaders, explains why each person fits, and drafts a note. Turn on review mode and nothing is sent until you approve it.