Here's the situation I was trying to fix.
My resume had been "good enough" for years. Polished verbs, tidy bullet points, a clean one-page layout. It also said almost nothing. Every line was an adjective wearing a job title: results-driven, cross-functional, data-informed, owned end-to-end. I could have swapped my name for a stranger's and the document would have worked just as well.
That's the tell. A resume built on adjectives is interchangeable. A resume built on evidence isn't.
This is the second half of the work I started in [Use AI to Find the Evidence Hidden in Your Own Work History]. That piece was about excavation—digging the real numbers and outcomes out of your own history. This piece is about assembly: turning what you found into a document that survives a six-second skim and a skeptical hiring manager.
Why Adjectives Fail and Evidence Holds
Before the rebuild, it's worth understanding what's actually broken about the adjective-driven resume.
Adjectives Are Unfalsifiable
"Strategic thinker" can't be checked. Neither can "detail-oriented" or "passionate about impact." A reader has two options: believe you or don't. Most default to don't, because every other resume makes the same claim.
Evidence is falsifiable, which is what makes it credible. "Cut the weekly reporting cycle from four hours to ninety minutes" can be verified, questioned, and discussed. That's the point.
Hiring Managers Are Reading for Risk
Here's the part most resume advice skips. A hiring manager isn't looking for the most impressive candidate. They're looking for the candidate least likely to be a mistake. Every vague claim is a small risk signal: what is this person actually hiding? Every specific claim reduces it.
AI Makes Adjective Sludge Worse
This matters more now than it did two years ago. Language models are extremely good at producing confident, generic, well-formatted nothing. If you prompt "rewrite my resume to be more impactful," you'll get a document that sounds better and says the same amount—which is nothing. The tool amplifies whatever input you give it. Feed it adjectives, get back polished adjectives.
The workflow below uses AI in the opposite direction: as an interrogator and a structurer, not a ghostwriter.
The Workflow
Here's the system. It runs on the evidence you already gathered, so if you haven't done the excavation pass yet, start there.
Step 1: Dump the Raw Material
For each role, write down everything you actually did that had a measurable or observable outcome. Don't format. Don't polish. Just list.
What changed because you were there?
What got faster, cheaper, cleaner, or less risky?
What did you build that's still running?
What did someone else stop having to worry about?
Include the numbers even if they're approximate. "Around 30%" is more useful than nothing. Note your confidence level on each one—this matters later.
Step 2: Have AI Interrogate Each Bullet
This is the highest-value use of AI in the entire process, and it's the opposite of what most people do. Don't ask it to rewrite. Ask it to find the holes.
A prompt that works:
Here is a resume bullet. Ask me the questions a skeptical hiring manager would ask. Do not rewrite the bullet. Only ask questions.
Bullet: "Improved the weekly reporting process."
A good model comes back with things like:
Improved how? What was the before state?
By what measure—time, accuracy, or something else?
Did you do this alone or lead a team?
What was the business impact beyond the process itself?
How long did the improvement hold?
Answer those, and the bullet builds itself. This is the move: AI as adversary, not author.
Step 3: Apply the Evidence Formula
Once the gaps are filled, structure each bullet the same way:
Action → Method → Measurable Outcome → Scope
Action: Rebuilt the weekly operations report
Method: consolidating three manual data pulls into a single automated query
Outcome: cutting production time from four hours to ninety minutes
Scope: across a five-person team
Not every bullet needs all four. But the absence of an outcome is the most common gap, and it's the one that kills credibility fastest.
Step 4: Compress Ruthlessly
This is the second place AI genuinely helps. Specificity has a cost: it's longer. Once the evidence is in, ask the model to cut each bullet to its shortest truthful version without dropping the number or the method.
One caution: make the model preserve the numbers verbatim. Models will sometimes round or "improve" a figure in a way that changes its meaning. Every number gets checked by you before it ships. Non-negotiable.
Step 5: Label Your Confidence
This is the step almost nobody does, and it's what keeps the resume honest.
For each bullet, tag it internally:
Tested: You have the number documented and could defend it in an interview.
Approximate: You remember roughly, but the exact figure is fuzzy.
Inferred: You're describing impact you believe happened but didn't directly measure.
Only the first two belong on the resume as hard numbers. Inferred impact gets written qualitatively—"reduced manual effort across the team"—without a fabricated percentage. If you can't defend a number in an interview, it's a liability, not an asset.
The Before and After
Here's a real pair from my own rebuild, mildly anonymized.
Before:
Results-driven operations professional with a passion for process improvement and cross-functional collaboration. Proven ability to drive efficiency and deliver impactful solutions in fast-paced environments.
After:
Rebuilt the weekly operations report by consolidating three manual data pulls into one automated query, cutting production time from four hours to ninety minutes for a five-person team. System has run unchanged for eleven months.
The first one could describe ten thousand people. The second one could describe exactly one, and it invites a follow-up question instead of ending the conversation. That's what you want. A resume's job isn't to close the deal—it's to earn the next conversation.
What Still Needs You
Here's the part of this workflow that doesn't get automated, and shouldn't.
Choosing what to cut. A resume isn't a record. It's an argument for a specific role. AI doesn't know which evidence supports the story you're telling, and it will happily include everything.
Defending the numbers. You're the only one who can verify that "30%" is real. The model can't know what you didn't measure.
Deciding the through-line. The best resumes read as a coherent arc, not a list. That judgment is yours. AI can suggest patterns, but it can't know which ones are true.
Reading the room. A resume for a startup ops role and one for a large-company PM role make different arguments from the same evidence. Context is human.
The model drafts and interrogates. You decide what's true and what it's arguing for.
The Two-Hour Version
If you want to try this before committing to a full rebuild:
Pick your three strongest current bullets.
Feed them to AI with the interrogation prompt. Answer the questions it asks.
Rewrite just those three using Action → Method → Outcome → Scope.
Tag each with your confidence level.
Check every number.
Three bullets, done properly, will outperform a whole page of adjectives. Run it this week and see which of your existing bullets survives the interrogation—the ones that don't are the ones you already knew were filler.
This is the assembly half of a two-part method. The excavation half lives in [Use AI to Find the Evidence Hidden in Your Own Work History]. Together they turn a resume from a list of claims into a record of things you actually did.
Better work first. More options next.
Make the workflow earn its place.
No feedback yet — submit the first.