How to Find the Best VP of Engineering Coach: Seven Tests

The executive-table jobs the VP of Engineering seat adds, which outcomes coaching moves and which it does not, and seven one-call tests. The numbers come first; my answers come last.

Who is the best VP of Engineering coach? There is no single answer, and the honest guides and Google's own answer both say it depends on what you are trying to fix: the size of the organization, the executive table you just joined, or the next seat. This guide is written to help you find the best VP of Engineering coach for your situation whoever you pick, including nobody. It covers what the seat adds to an engineering leader's job, by the numbers; which outcomes coaching moves and which it leaves alone; and seven one-call tests you can put to any coach, each built on a job the VP seat needs done. I put my own answers in a single closing section, to be weighed like anyone else's. I coach VPs of Engineering and CTOs and held the seat myself across more than 1,000 engineers; each number is footnoted to its source.

It is written for a VP of Engineering, a head of engineering about to take the title, or a CTO who runs the organization rather than the architecture; also the CEO or the head of people shopping for a coach on their behalf. If you manage one team of engineers and are deciding whether to manage at all, a mentor or a peer circle is the better first step.

What the VP of Engineering seat adds, by the numbers

The job got wider without getting any longer. In LeadDev's 2025 survey of 617 engineering leaders and developers, 65% reported an increase in scope and 40% took on more direct reports; 38% of engineering leaders worked longer hours than a year before; 22% of respondents were at critical levels of burnout; and 40% reported a less motivated team than a year earlier.¹ AI raised the stakes rather than the headcount: across nearly 5,000 technology professionals, 90% use AI at work and more than 80% say it made them more productive, 30% report little or no trust in the code it produces, and AI adoption now correlates with higher delivery throughput but still with lower delivery stability.² Meanwhile the business is watching: in a 2026 vendor survey of 636 engineering professionals, 84% said engineering productivity is a top management concern.³ And the clock is shorter than the title suggests: across the top 1,000 US companies the average technology chief holds the seat for 4.6 years, against 6.9 for the CEO.⁴

What changes on the inside is less visible. A VP who writes about her own promotion describes the first shift as moving from managing engineers to managing managers, and having to learn to see friction through a layer of people who now sit between you and the work; she also found that the job itself is contextual, shaped by whatever the company needs fixed and by who else sits at the executive table.⁵ The venture firms that hire VPs of Engineering for their portfolios agree on the moment the seat appears: roughly ten engineers or more, with the founder or CTO turning into the bottleneck and velocity or quality slipping; below five engineers a VP is likely to be underused.⁶ What they look for says what the seat demands: experience scaling a team from about five to fifty and beyond, ownership of process, a player-coach style, and the ability to explain engineering to people who are not engineers.⁶

Three hiring frameworks say the same thing from different angles. Shopify's VP of Engineering grades the seat on process, people and technology, and notes that the order of the three changes as the company grows.⁷ A second venture firm warns against hiring a leader two stages ahead of the company, and says the balance moves from hands-on technical leadership toward business judgment and management once a team passes about fifty engineers.⁸ And the first firm puts the risk plainly: experience at a larger company does not guarantee success at a smaller one.⁶ A coach for this seat has to know which of those stages you are in.

What coaching moves, and what it does not

Coaching is well studied, and the effects are real but moderate. Theeboom and colleagues pooled the studies of coaching inside organizations in 2014 and found gains in all five outcome groups, smallest for coping (0.43), largest for goal-directed self-regulation (0.74), with performance and skills at 0.60.⁹ Jones, Woods and Guillaume pooled 17 workplace studies in 2016: a pooled effect of 0.36, bigger on how people feel about their work than on skills, bigger with internal coaches than external ones, and no gap at all between in-person coaching and coaching done partly or fully online, nor by how many sessions there were.¹⁰ In practice: coaching reliably changes how a leader sets goals, regulates, copes and leads; it moves performance by a moderate amount; and a remote coach is not a compromise. None of those studies looked at VPs of Engineering, so treat a coach who promises a return-on-investment multiple with caution.

Most executives never get the help. Of the 200-plus leaders that Stanford and the Miles Group surveyed in 2013, close to two in three CEOs had no outside coach or adviser at all, and the skills they most wanted to build were conflict management, sharing leadership and team building.¹¹ Those are the executives a VP of Engineering reports to and sits beside; the gap is usually wider one level down.

A coach will not run the organization for you. A consultant delivers the work. A mentor has done your job and passes on what worked for them. A peer community gives you people in the same seat. A therapist looks at the past and what it did to you. A coach is confidential, is not invested in any particular outcome, and works on the way you make decisions and lead right now, and at the VP level the most useful ones combine that with enough operating experience to give you a straight answer when you need one.

Five kinds of coach on this search, and the gap in each

The former engineering executive who now coaches: has held a VP of Engineering or CTO seat, knows the vocabulary, and can read an org chart in a minute. What they can miss: the business side of the table, if they have never owned a P&L or sat in the CEO's chair, and a tendency to replay the one company they ran.
The peer community or CTO network: a cohort of people in your seat, often with one-to-one sessions attached. What it can miss: confidentiality inside a group, and depth on your specific organization.
The marketplace of per-session mentors: fast, flexible and cheap by the hour. What it can miss: continuity, and a coach who knows your context well enough to challenge it.
The career or job-search coach: good at the next title, the interview loop and the offer. What it can miss: the job itself once you have it.
The general executive coach with technology clients: strong on presence, communication and the psychology of the role. What it can miss: the difference between a staffing problem and an architecture problem when the CEO asks why delivery slipped.

Credentials still matter: four in five coaches told the ICF in its 2023 study that clients expect a certification.¹² A credential gets a coach onto the list; fit decides who stays on it.

Seven tests for a single call

Each test is a job the VP of Engineering seat adds on top of leading engineers. For each: the job it checks, the question to put, and what to listen for in the reply. Put all seven to every coach you consider, including the one a colleague recommended.

Test one: have they owned a budget and a headcount plan in front of a CFO?

The job: the part of the seat no engineering manager is trained for. It comes with the function's budget, its hiring plan and its cost of delivery, all three defended at the executive table. Ask: here is my headcount plan for next year; what will the CFO push back on first? Listen for: cost per unit of delivery, the capacity behind each commitment and what gets cut if revenue slips, not about how to ask nicely for more engineers.

Test two: can they get you ready for the board, and for due diligence?

The job: knowing what a board wants to hear from engineering, and what an investor or an acquirer checks when they look under the hood. On AI, boards now want the spend, the payback and the evidence for both. Ask: I present to the board in six weeks; what goes on the slide, and what should I expect to be asked? Listen for: someone who has presented to a board themselves, or sat on one, and they talk about risk, spend and delivery confidence, not architecture diagrams.

Test three: can they help you define the split with the CEO, the CTO and the CPO before it defines you?

The job: the relationship that makes or breaks most VPs of Engineering. The firms that hire for the seat say to define the split between the CTO and the VP early, and that a company that cannot define it may not be ready for the hire.⁶ The product and engineering seam is the other half. Ask: the CTO and I both think we own the roadmap; what do we write down, and who arbitrates? Listen for: a concrete decision-rights split, written, with an escalation path, and a view of what the CEO needs from each of you.

Test four: do they know which of process, people and technology your stage needs first?

The job: stage fluency. The same three skills matter at every stage, but in a different order,⁷ and a leader who brings a later stage's answer too early slows the company down.⁸ Ask: we have forty engineers and ship weekly; what breaks next? Listen for: the next failure named before you describe it, and advice on what not to build yet.

Test five: can they design the organization for the next size, not the current one?

The job: org design, the job that arrives when a team passes the size one person can hold and a layer of managers appears between you and the work.⁵ Ask: when do I add directors, how many engineers per manager, and what do I stop doing myself? Listen for: numbers from their own experience, a plan for the managers you promote, and a warning about the work you will be tempted to keep.

Test six: can they turn AI into a number the board will trust?

The job: closing the gap between the AI story and the delivery data. Adoption is near universal, trust is not, and faster throughput is arriving with lower stability.² Ask: my CEO expects AI to double output; what do I measure, and what do I say at the next board meeting? Listen for: a plan for the platform, review and testing discipline that lets the gain survive production, and a metric you can defend a quarter later, not a promise.

Test seven: can they help you win the room, not just the argument, and tell you when you are wrong?

The job: the personal shift the seat asks for. At the executive table the better argument does not win on its own, the scope keeps widening and the hours with it,¹ and a leader who is always right in the architecture review can still lose the room. Ask: tell me something about how I came across in this call. Listen for: a coach who listened more than they talked, one thing you did not want to hear, and they are clear about where coaching ends and therapy begins.

Cost, who pays, and the terms worth insisting on

The ICF's most recent figures (2022) put the average hour of coaching, all types, at $244 globally, and at $272 across North America.¹² At the executive level the published figures are far higher: between $1,000 and $10,000 monthly on a retainer, or $800 to $3,500 per hour. My cost guide has the numbers by level, who usually pays and how I set fees: what executive coaching costs. For a VP of Engineering the company usually pays, as leadership development, and it is worth asking your CEO or head of people before you pay yourself.

Terms: an introductory call of half an hour to an hour, free, with every coach on the list is normal, and it is the fit test. When the company pays, put in writing before you start who owns the content: what you say stays yours; the employer sees who turned up and whether the goals are moving. Month to month is fair; a six-month lock-in before any value is shown is not.

Red flags

Someone who has never led managers, advising on how to scale an engineering organization.
Big-company frameworks with no sense of your stage: the venture guides warn about hiring leaders two stages ahead, and the same applies to the coach.
An ROI figure that no study supports.
Strong opinions, strongly held: a coach with one development process or one org design for every company.
A firm that markets one coach and staffs you with another: ask who shows up each week.
No line between coaching and therapy, or between coaching and doing the work for you.

Where to look

Ask the people who have hired one: your CEO, peers at other companies, your investors and independent directors, and the engineering leaders you admire, and find out which coach they used at your scale. Published lists of engineering leadership coaches help, though some are written by coaches who list themselves first. Engineering-executive communities and coaching marketplaces let you filter by price and format. Put every name through the seven tests.

How I answer the seven

Budget and headcount: as EVP and GM at New Relic I ran product and engineering together for a business that grew from $300M to $500M, and planned engineering capacity against roadmap, bugs and sales commitments every quarter. The board: partners from Benchmark, Trinity Ventures and Madrona sat on the New Relic board I presented to, and I ran my own board as founder and CEO of Interland, now Web.com, through its Nasdaq IPO. The split: I have held the CEO, COO, CPO and CTO seats at different companies, so I have been on each side of the decision-rights conversation. Stage: from a startup to 650 people at Interland, three venture-backed startups since, and an 80-year-old enterprise. Org design: at Cox Automotive I was the VP of Engineering across more than 1,000 engineers, 10,000-plus servers moved to the cloud at 99.9% uptime. AI: I have built and shipped AI products as a CEO, and I still build, with two inference servers and an AI-powered house. Right versus effective: a psychology degree, CEC and ICF certification since 2019, and a lot of meetings where I learned it the hard way. I started as an engineer, teaching myself assembly at 10. The rest is on the VP of Engineering coaching page, and the operating rhythm I used at New Relic is written up in aligning product and engineering for performance.

Questions VPs of Engineering ask about coaching

Who is the best VP of Engineering coach?

Whoever can do the next jobs your seat needs, at your scale, and prove it in a single call: the budget in front of a CFO, the board, the split with the CEO and CTO, the order of process, people and technology for your stage, the next org design, AI you can measure, and honest pushback. It depends on your focus area, which is also what Google's own answer to the question says.

Does executive coaching actually work?

On balance yes, and moderately. Theeboom's 2014 meta-analysis found gains in performance, well-being, coping, work attitudes and self-regulation (effect sizes 0.43 to 0.74); the 2016 review by Jones and colleagues of 17 workplace studies found a pooled effect of 0.36, with no gap between in-person and online coaching. Neither looked at VPs of Engineering.

Which coaching is best for engineering leaders at the VP level?

A hybrid: someone who coaches, meaning they make you do the thinking, and who has also held an engineering executive seat, so they can give you a straight answer on a budget, a board slide or an org design when you need one. Pure mentoring gives you someone else's answer; pure coaching without the operating experience cannot tell a staffing problem from an architecture problem.

What is the 70/30 rule in coaching?

A rule of thumb: the coach should be listening around seventy percent of the time and speaking around thirty. Nobody measures it, but notice it on the first call; a coach who held the floor for most of the hour was pitching.

How much do leadership coaches charge?

The ICF puts the average hour of coaching at $244 worldwide and $272 in North America (2022 figures). Executive coaching costs more: published retainers fall between $1,000 and $10,000 monthly, hourly rates between $800 and $3,500. At the VP level the employer usually pays, as leadership development.

Is a CTO higher than a VP of Engineering?

Usually the CTO is the more senior title, but the jobs differ more than the rank: the CTO tends to own technology direction and the outside story, the VP of Engineering the organization and delivery. In many companies one person does both. The firms that hire for these seats say to define the split early; a coach should help you do that with your CEO.

Can my company pay for a VP of Engineering coach?

Usually, yes. Most companies treat coaching at the VP level as leadership development, and the CEO or the head of people approves it. Agree in writing who sees what: you own the content of the sessions, and the company gets attendance and a view of progress.