The verdict
An excellent résumé pointed one level below the target. Every number on the page proves engineering got cheaper, faster, or more stable — and not one proves the business got bigger. That's the right proof for Director and the wrong proof for VP.
What it found 5 findings, worst first
- Every number proves efficiency; none proves growthDoes it prove anything? · Does it argue for the job?
Fourteen figures, all of them cost, speed, or stability. None connects to revenue, customers, or a product the business sold. A VP committee is deciding whether you belong on an executive team — and those are built around growth.
Cut cloud spend 34% ($2.1M annualized) in 11 months
- The summary opens on cost, which sets the wrong frameDoes it prove anything? · Reason to pick you
Strong writing that frames you as the leader brought in to make engineering efficient. Right at a company cutting margin, wrong at one hiring a VP to scale — and it colors how every figure below it is read.
Engineering leader who turns platform cost and delivery speed into board-level outcomes.
- Your stated influence stops at the edge of your own organizationDoes it argue for the job? · Reason to pick you
Nothing describes setting direction above your own function — no company strategy, no executive team, no acquisition work. A committee has to guess whether you operate at the altitude the role needs.
- Executive vocabulary appears in your skills but not your experienceDoes it prove anything?
Org design, platform strategy, and budget ownership are claimed in a list and never shown in a bullet. A list is a claim; a bullet is evidence — and search weighs them that way.
- One header carries four different kinds of proofCan it be read? · Does it argue for the job?
Talks, writing, open source, and a certification share one heading. Strong items, weakened by arrangement. Split them and both a scanning reader and a parser find them instantly.
The plan 275 → 294
- Attach a business outcome to your three largest projects+6
- Add the altitude above your own function+4
- Move executive vocabulary into the work itself+4
- Reframe the summary around what you build, not what you save+3
- Split the credentials into two headers+2
Rewritten for you
Against the job you want VP Engineering posting
on your résumé in the posting, missing from yours