Selling to a VP of engineering

A VP of engineering owns whether things ship. Not the vision, not the architecture debate. The release.

Sell to that and you'll get a reply. Sell to anything else and you'll get ignored.

What they own

The CTO sets direction. The VP of engineering runs the machine.

They own the teams, the hiring plan, the delivery process and the release calendar. They own the managers who run the squads. When a launch slips, they're the first person the CEO or the CTO looks at.

In smaller companies, the VP of engineering is often the top technical leader and does both jobs. In larger ones, there may be several, each running a group of teams.

They're measured on delivery against commitments, first. Did the features promised to customers and sales ship when they were supposed to?

Then quality. Incidents, outages, rollbacks. A VP whose teams ship fast and break things doesn't last.

Then the team itself. Hiring against plan, keeping good engineers, managers who can lead.

And cost, more and more. When budgets tighten, engineering is often the biggest line, and the VP gets asked to do the same with less.

What they ignore

Anything that sounds like it'll add work for their teams.

A pitch for a new methodology. A pitch that implies their engineers aren't good enough. A pitch that starts with "digital transformation" or any phrase they'd never say out loud.

And they ignore sellers who don't understand how engineering works. If your message suggests you think adding people makes a late project faster, they're gone.

Signals that matter for this seat

Hiring is the clearest one. A VP posting a run of senior roles in one area is telling you where they're short. If the roles have been open for months, they're struggling to fill them.

A new VP of engineering is strong too. They'll look at the delivery process, the team structure and the outside partners in their first 90 days.

Tech stack signals matter here. Job posts name the platforms they're on and the ones they're moving to. A posting that asks for experience migrating off one platform to another tells you a program is coming.

And topic signals. Engineering leaders post about their real pain more openly than most buyers. A VP who writes about slow builds or on-call burnout is telling you what hurts. The buying signals guide covers the full set.

What to send

Be concrete, technical where it helps and short.

Say a VP of engineering at a payments company has had five senior backend roles open for a couple of months, and the company just announced a new product line for later in the year.

Your team has had five senior backend roles open since the new product line was announced. With a launch date already public, that gap usually lands on the existing team as overtime and slipped side projects. My guess is the current roadmap is paying for the new one. Is that accurate, or is the bigger issue something else?

That message names something real. It speaks to their seat, the person who owns the date. And it's easy to correct. If they say hiring is fine and the real problem is test automation, you know where to go next.

Reach the rest of the committee

The VP of engineering is often the champion, not the final buyer. Large engagements may need the CTO or the CFO to sign.

Find the economic buyer above them and give that person a version about cost and risk to the roadmap. Find the technical lead, often a principal or staff engineer, and give them a version about the work itself. More on the CTO seat in selling to a CTO.

Engineering leaders trust people who've done the work.

Bring someone technical to the first call. Talk about how your teams run, how they hand off, how they test. Offer to start small, with a defined piece of work that proves quality before scale.

A VP of engineering who trusts your teams will bring you back for years. One who doesn't will never return your email. The first message decides which one you meet.