VP of engineering resume example

What recruiters look for

• Org size and shape: engineers, teams, managers and directors reporting to you, and the budget you own. A reader should be able to sketch your org chart.
• Predictable delivery: roadmap commitments met, lead time, deploy frequency, incident trends. CEOs hire a VP of engineering to stop being surprised.
• A bench of leaders: managers and directors you hired or grew, promotions, regretted attrition. Your leaders are your output now.
• Money: headcount plans, cloud spend, vendor decisions and cost per customer. Finance will be in the interview loop.
• Business outcomes you enabled: enterprise deals unlocked by compliance work, revenue from a platform, churn cut by reliability.

Writing the summary

Give your years in software and in leadership, the size of the org and company you run (engineers, revenue, stage), and the two or three things you are known for. Keep technology names out of the summary unless the role depends on them; a VP summary is about the organization.

Bullet points that work

Strong lines for this role, beyond the ones in the example. Borrow the shape and put in your own numbers.

• Reorganized 12 component teams into 7 product-aligned teams with clear ownership, cutting cross-team dependencies in planning from 40 to 11.
• Hired 4 directors and 9 engineering managers in 18 months; 3 of the managers were internal promotions from senior engineers.
• Brought the engineering budget from 31% to 24% of revenue over two years while headcount grew, by reallocating 20 roles from maintenance to growth work.
• Reduced severity 1 incidents from 26 a year to 7 by funding an SRE team and making error budgets part of quarterly planning.
• Opened an engineering hub in Lisbon that reached 35 engineers in a year, with retention matching the home office.
• Ran technical due diligence on 3 acquisition targets and led integration of the one completed, retiring its stack within 9 months.
• Raised the engineering engagement score from 64 to 81 after a reorganization, through a new career ladder and transparent promotion calibration.
• Negotiated a 3-year cloud commitment that cut infrastructure costs by $4.2 million against list price.
• Partnered with product to retire 9 low-usage features, freeing two teams for the company’s top-priority platform bet.
• Built the engineering metrics dashboard reviewed monthly by the executive team, covering delivery, quality, cost and people.

Skills to list

Certifications and licenses worth listing

• No certification is expected: VP of engineering hiring is decided on the organizations you have built and what they delivered.
• AWS, Google Cloud or Azure professional-level certifications: a small plus if you will own a large cloud budget or a migration, but list them in one line.
• Executive education (a leadership program at a business school, for example) can go under Education if it is recent and relevant.

Length and format

Two pages. Page one holds the summary and your current role in full; your director and manager roles go next with two or three bullets each. Engineering roles from before management can be one line each. A short skills section of leadership and platform areas helps recruiters search, but leave out long lists of languages.

Common mistakes

• Writing like a staff engineer: architecture and technologies with no mention of teams, budget or managers.
• Leaving out the size of your organization and budget, which is the first thing a CEO or recruiter checks.
• Claiming every engineering win personally. Say what the org delivered and what you changed to make it possible.
• No cost story. A VP who cannot talk about engineering spend as a share of revenue looks junior to a CFO.
• Listing 25 technologies in the skills section. At this level they suggest you have not let go of the code.