Is being a VP of Engineering
at risk from AI?

No, not in any foreseeable timeline. The VP of Engineering role is fundamentally about leadership, judgment, and organizational influence—capabilities AI does not possess. While AI will automate portions of technical oversight (code review, metrics dashboards, incident triage), it cannot build trust with a CEO, negotiate competing priorities across product and sales, or inspire a demoralized team through a layoff. The role will evolve toward more strategic work, but demand for experienced engineering executives remains strong.

Routine technical oversight tasks are most exposed: reviewing pull requests for style and bugs, generating sprint reports, analyzing performance metrics, and drafting postmortems. AI coding assistants and agent frameworks can handle much of this today. Middle-management coordination—status updates, resource allocation suggestions—will also see significant automation. However, these tasks typically consume 20-30% of a VP's time. The strategic, relational, and political dimensions of the role remain firmly human.

Double down on the irreplaceable: strategic thinking, executive communication, and people leadership. Invest in understanding AI capabilities deeply—not to code models yourself, but to make informed build-vs-buy decisions and set realistic expectations with the board. Strengthen your financial literacy (unit economics, ROI modeling) and cross-functional influence. Finally, cultivate a public presence through writing or speaking; visibility raises your market value and signals you're a thought leader, not just an operator.

Unlikely in the near term. Compensation for senior engineering executives is driven by scarcity of proven leadership talent, not hours worked. If anything, VPs who successfully lead AI transformation initiatives may command premium comp as companies compete for leaders who can navigate this shift. However, organizations may flatten hierarchies—eliminating some director or senior manager layers—which could reduce the total number of VP seats over time. The best-compensated VPs will be those who demonstrate clear business impact and strategic value.

Large enterprises offer more structural resilience—established budgets, complex org charts, regulatory requirements—but also more bureaucracy that AI may streamline. Startups offer higher impact per individual but less job security overall. For VPs specifically, the safest position is at a growth-stage company (Series B-D) where you're building the engineering org from 20 to 200+ people. Early-stage startups may not need a VP; mature enterprises may consolidate layers. Geographic factors matter less for executive roles, which are increasingly remote-friendly.

Directors face moderately higher risk because their role skews more toward execution and team coordination—areas where AI agents and automation tools are advancing quickly. VPs operate at a higher level of abstraction: setting strategy, managing budgets, interfacing with the C-suite and board. These responsibilities require organizational context, political savvy, and trust that AI cannot replicate. That said, both roles will see their day-to-day tasks shift; the key differentiator is how much of your value comes from strategic influence versus operational management.

No, not unless you find it personally interesting. Your value as a VP is not in writing PyTorch or fine-tuning LLMs—it's in understanding what AI can and cannot do, making smart build-vs-buy decisions, and leading your organization through adoption. Focus on strategic AI literacy: read case studies, experiment with tools like GitHub Copilot or Cursor, and talk to vendors. Your job is to set direction and evaluate trade-offs, not to be the most technical person in the room.