Career Watt
Résumé Effectiveness Assessment
Career Assessment Report · 18 September 2026
Marcus Reyes
Director of Engineering → target role: VP Engineering
An excellent résumé pointed one level below the target
This résumé is in the top 5% of documents this assessment sees. Outcomes are quantified in nearly every bullet, the fourteen-year progression is legible at a glance, and the credibility section does work that most senior résumés skip entirely. Against Director of Engineering postings it would be difficult to improve.
The remaining 25 points are not spread evenly across small errors. They cluster around a single pattern: every outcome on the page is an efficiency outcome. Cost down, latency down, deploy frequency up, retention up. Fourteen figures, all of them proving you make engineering cheaper, faster, and more stable — and not one proving you made the business larger.
That is the correct proof for the role you hold and the wrong proof for the role you want. A VP Engineering committee is deciding whether you belong on an executive team, and executive teams are assembled around growth. The findings below are narrow, and each one is worth more than its point value suggests.
Where the points went
| ATS Compatibility | 29 / 30 | Excellent |
| Structure & Length | 24 / 25 | Excellent |
| Contact & Metadata | 15 / 15 | Full |
| Grammar & Consistency | 15 / 15 | Full |
| Section Completeness | 14 / 15 | Excellent |
| Achievement Quantification | 27 / 30 | Excellent |
| Action Verb Strength | 18 / 20 | Strong |
| Keyword Optimization | 18 / 20 | Strong |
| Relevance & Prioritization | 18 / 20 | Strong |
| Summary Impact | 9 / 10 | Strong |
| Value Proposition Clarity | 22 / 25 | Strong |
| Career Progression Narrative | 19 / 20 | Excellent |
| Skills Section Strategy | 13 / 15 | Strong |
| Education Positioning | 9 / 10 | Strong |
| Differentiation | 8 / 10 | Strong |
| Credibility Indicators | 9 / 10 | Excellent |
| Personal Brand Alignment | 4 / 5 | Strong |
| Industry Authority Signals | 4 / 5 | Strong |
Four things most senior résumés never achieve
Nearly every bullet carries a figure
Fourteen quantified outcomes across five roles, with before-and-after framing on the largest projects rather than bare endpoints. Achievement Quantification scored 27 of 30 — this category is where most senior résumés lose the most ground, and yours is close to the ceiling.
"Raised deploy frequency from 1.2/week to 41/day and reduced change-failure rate from 18% to 4.2%"
The credibility section does real work
A conference talk, a widely-read written piece, a maintained open-source project, a professional certification, and a named peer forum. Layer 4 is the section most candidates leave empty, and it is the clearest separator in a field of similarly-titled applicants. Credibility Indicators scored 9 of 10.
Speaker, SREcon Americas 2025 · Maintainer, Terraform module suite (2.4k stars) · AWS Certified Solutions Architect – Professional
Technical depth is proven, not implied
The 2011–2013 and 2013–2016 entries each carry one substantive line. This answers the question a committee always raises about a leader a decade into management, and it answers it without spending space. Career Progression Narrative scored 19 of 20.
"Led design of the distributed job scheduler still running the company's batch workloads"
People outcomes are quantified, which is rare
Retention against a company baseline, offer-accept rate, promotions with destinations. Most engineering leadership résumés state team size and stop. These figures are among the strongest available signals for an executive hiring committee, and they are already on the page.
"Sustained 94% voluntary retention across the org over four years against a 79% company average; promoted 7 engineers, 3 into management"
Findings, in order of cost
Every number proves efficiency; none proves growth
Layer 2 · Achievement Quantification · Layer 3 · Value Proposition Clarity
Fourteen quantified outcomes appear across the document. Cost reduction, latency reduction, failure-rate reduction, onboarding-time reduction, downtime reduction, retention. Every one is a measure of engineering becoming cheaper, faster, or more stable. Not one connects to revenue, customer growth, market expansion, or a product outcome the business sold.
This is the most expensive pattern here precisely because the numbers are so good. A reader concludes, correctly, that you are exceptional at running an engineering organization efficiently — and has no evidence about whether you can grow one toward a business result. At the Director level that distinction rarely comes up. At the VP level it is often the entire deliberation.
The summary opens on cost, which sets the wrong frame
Layer 2 · Summary Impact · Layer 4 · Differentiation
Your first sentence names cost and delivery speed as what you convert into outcomes, and the supporting sentence leads with a 34% spend reduction. The summary is strong writing — specific, quantified, free of filler — and it frames you as the leader you bring in to make engineering efficient.
That framing is an asset at a company under margin pressure and a liability at a company hiring a VP to scale. Since the frame is set in the first ten seconds of reading, it colors how the rest of the figures are interpreted: growth evidence further down gets read as supporting detail rather than as the headline.
Your stated influence stops at the edge of your own organization
Layer 3 · Career Progression · Layer 4 · Industry Authority
Every accomplishment on the page happens inside platform engineering. The internal developer platform is noted as used by all nine engineering teams, which is the one place the document reaches beyond your org — and it is stated as adoption rather than as influence you exercised.
Nothing describes setting direction above your own function: no company engineering strategy, no executive team or board contribution, no technical diligence on an acquisition, no cross-functional initiative you owned outside your reporting line. A committee reading this sees a superb functional leader and has to guess at whether you operate at the altitude the role requires.
Executive vocabulary appears in your skills but not in your experience
Layer 2 · Keyword Optimization · Action Verb Strength
Org design, platform strategy, and budget ownership are listed as capabilities. None of the three appears as a described action in any role. Applicant tracking systems and human readers both weight terms found in experience more heavily than terms found in a list, because a list is a claim and a bullet is evidence.
The underlying work is clearly there — restructuring a 22-person org across three teams is org design. It is simply narrated in operational language rather than in the language a VP posting uses.
One header carries four different kinds of proof
Layer 1 · Section Completeness · Layer 3 · Skills Strategy
Speaking, writing, open-source maintenance, a certification, and a forum membership sit under a single combined heading. These are strong items weakened by arrangement — a reader scanning for credentials and a parser indexing for certifications both have to work harder than necessary.
Splitting them into two headers, with thought leadership separated from credentials, costs one line and makes the section's contents legible in a scan rather than a read.
Checks that could not run
Each of these is a check the assessment was prepared to run and could not, because the document never states the value it needed. At this score, the absences are more informative than the deductions.
- No revenue, bookings, or customer-growth figure appears in any role. Business-impact evaluation could not run. Your current employer is described as $180M ARR, so the context exists; your contribution to it is never stated.
- No executive team or board interaction is described. Seniority-altitude evaluation could not run — the single highest-weighted signal for VP-tier targets.
- No product outcome is named. The API v2 launch states delivery and partner migration but never what it enabled commercially.
- No budget authority outside infrastructure is stated. Total ownership scope could not be assessed. The $4.3M figure is explicitly infrastructure and tooling; headcount cost for 22 engineers is not stated and is likely the larger number.
- No forward-looking statement of what you would own appears. Target-role fit evaluation could not run. The document proves what you did and never claims what you are prepared to run.
Five actions, ordered by points recovered
Attach a business outcome to your three largest projects
Layer 2 · Achievement Quantification · Layer 3 · Value Proposition
The migration, the developer platform, and the ingestion rebuild each enabled something the business sold — a customer tier, a contract retained, a market entered, a roadmap unblocked. Name it. One clause per bullet converts efficiency proof into growth proof without removing a single existing figure.
Add the altitude above your own function
Layer 3 · Progression · Layer 4 · Industry Authority
Executive team contribution, company-level engineering strategy, acquisition diligence, or a cross-functional initiative you owned outside your reporting line. One bullet in the current role. This addresses the question a VP committee will otherwise have to answer by guessing.
Move executive vocabulary out of the skills list and into the work
Layer 2 · Keyword Optimization · Action Verb Strength
Rewrite the bullets where you already did org design, owned budget, and set platform strategy so they use those words. The work does not change — only whether a parser and a reader can find it where they look first.
Reframe the summary around what you build, not what you save
Layer 2 · Summary Impact · Layer 4 · Differentiation
Keep the specificity and the figures. Change which one leads. Opening on scale, growth, or organizational capability sets a frame in which the cost results read as evidence of rigor rather than as the headline achievement.
Split the credentials block into two headers
Layer 1 · Section Completeness · Layer 3 · Skills Strategy
Thought leadership — speaking, writing, open source — under one heading; certifications and professional memberships under another. One extra line, and both a scanning reader and an indexing parser find what they are looking for immediately.
All five actions are edits to existing bullets rather than new material, and none requires a fact you do not already have. Completing them holds the Exceptional tier while closing the gap that currently separates a superb Director résumé from a VP Engineering résumé. Actions 1 and 2 carry the argument; the rest are polish. Re-run the assessment afterward to confirm the movement.
What the assessment examined and passed
- Reverse-chronological ordering throughout
- No unexplained employment gaps across fourteen years
- Date formatting consistent across all five roles
- No graphics, tables, columns, or text boxes that break applicant tracking parsers
- Standard section headers that parsers recognize
- Complete contact block including professional profile and code repository links
- Verb tense correct throughout — present for current role, past for prior roles
- Parallel grammatical structure maintained across all bullets
- Bullet weighting proportional to recency and relevance
- Company context supplied where it aids interpretation of scope
- Education placed and sized appropriately for years of experience
- No outdated conventions — no objective statement, no references line, no photograph
- No first-person pronouns
- Figures internally consistent; no stated number contradicts another
Method
The Résumé Effectiveness Assessment evaluates a résumé across four layers and eighteen scored categories against a fixed 300-point model. Every finding in this report cites the résumé text that produced it. Scores are awarded against stated criteria, not against a comparison group.
Scope
This assessment evaluates the document as submitted, against the stated target role. It does not evaluate the candidate, the career, or the likelihood of any particular hiring outcome.
What this is not
This is an evaluation and a prescription. It is not a rewrite. The report identifies what to change and what each change is worth; applying the changes and re-running the assessment confirms the movement.
Tier thresholds
Exceptional 270–300 · Strong 240–269 · Good 210–239 · Adequate 180–209 · Needs Improvement below 180.