Some resumes describe people who think. Some describe people who do. Hiring managers can tell which is which in five seconds, and they reject the wrong one for the role.
If you’re applying to execution-coded roles and getting silence, your resume is probably reading too strategic. Verb shape is the fix.
What “too strategic” actually means
Open your resume. Read the first word of every bullet. Tally:
| Strategic verbs | Execution verbs |
|---|---|
| Led | Shipped |
| Drove | Built |
| Aligned | Debugged |
| Championed | Deployed |
| Defined | Designed |
| Owned the strategy for | Wrote |
| Set the direction | Implemented |
| Influenced | Refactored |
If 60%+ of your first words are in the left column, your resume reads strategy. For an execution role — Senior Engineer, Staff Engineer, IC PM — this is a near-automatic reject.
Why hiring managers reject on verb shape
Verb shape is a fast proxy for what kind of work the candidate actually does. The hiring manager reading the bullets is asking, sub-vocally:
- “Will this person sit and ship code, or will I have to manage their meetings?”
- “Do they describe artifacts (the thing they built) or processes (how they ran the team)?”
- “Will they unblock themselves, or will they need 3 stakeholders aligned?”
Strategic verbs answer the second half of each question. Execution verbs answer the first half. The role wants one of the two.
Execution verbs vs strategic verbs is the deeper read.
The conversion technique
Same work. Different verbs. Some examples:
Before (strategic)
Led the v2 architecture migration across 12 services, aligning 3 squads and championing the new observability strategy.
After (execution)
Designed and shipped the v2 architecture migration across 12 services. Built the new observability stack (OpenTelemetry → Grafana). Cut p99 latency 41%.
Same migration. Same outcome. Different shape.
Before
Owned the strategy for the platform team and set technical direction for 3 squads.
After
Designed the platform’s storage layer; rewrote the ingestion pipeline (50k events/sec); ran weekly architecture reviews across 3 squads.
The leadership is still there. It’s just no longer the first thing the reviewer reads.
When 100% conversion is wrong
A senior IC role isn’t pure execution. Some strategic verbs are appropriate — usually 20–30% of bullets. The rule is role mirror:
- Role implies 80% execution → resume should be ~70% execution / 30% strategic.
- Role implies 60% execution → resume should be ~55% execution / 45% strategic.
- Role implies pure leadership → resume should be ~70% strategic / 30% execution.
Read the JD for level cues to figure out the target ratio.
Run the verb-shape check
The diagnostic reads verb density on your bullets and on the JD, then returns the gap. If the Execution indicator is red, you have a verb-shape problem.
For each red bullet, you’ll get a before/after rewrite with one-line rationale. Two free runs, no card.
The 12-minute fix
Most candidates with a strategic-verb problem need 4–6 bullet rewrites to flip the read. That’s 8–12 minutes of work. The callback rate change is roughly 3x for execution-coded role applications once the verb shape matches.
The leverage is real. The fix is small.
Related reading
- Execution verbs vs strategic verbs — the canonical conversion list.
- Mirror the job description in your resume — phrase-mirroring done right.
- Find weak bullet points in my resume — bullet-level diagnosis.
- Rewrite resume bullets for a job description — the per-bullet framework.