VP of Engineering is one of the hardest targets for cold outreach because they have an extremely low tolerance for anything that reads as marketing. They think in systems, in tradeoffs, in evidence. An email that makes a claim without supporting evidence will be discarded in under ten seconds. An email that demonstrates technical understanding — even in one sentence — will be read in full.
The difference between a VP Eng and a CTO in most organisations: the VP Eng is more execution-oriented and closer to the daily realities of the engineering team. They are focused on delivery speed, team health, and technical debt — not strategic roadmap or board-level technology positioning.
What VP Engineering Outreach Should Address
- Developer experience and retention. Engineering talent is expensive and hard to retain. Solutions that genuinely improve developer experience — faster feedback loops, better tooling, less toil — have a clear business case.
- Incident rate and MTTR. Mean time to recovery from incidents is a key metric for engineering leadership. If your solution reduces incident frequency or recovery time, quantify it with real numbers.
- On-call burden. Engineering managers lose sleep over on-call rotation health. Solutions that reduce alert noise or improve system observability speak directly to this pain.
- Hiring and ramp time. Every VP Eng is managing a backlog of unfilled engineering roles and trying to get new hires productive as quickly as possible. Tools that accelerate onboarding are immediately relevant.
The Opening That Works
Reference their technology stack (visible through job listings, engineering blog posts, or open-source contributions) and connect it to a specific outcome. "You're running X at scale — here's where teams like yours typically hit the Y problem and how we address it" is the format. Technical specificity signals that you are not sending a mass campaign. That alone gets you more attention than most cold emails receive.