Proof Builder — Get Hired in a Broken Job Market

A Word of Caution Read This First

This won't write your résumé. It'll dig up the specifics your résumé needs — the actual before-and-after, the actual mechanism, the actual proof — so what you write isn't a guess dressed up in confident language. Most résumés fail not because the writing is bad but because there was never anything underneath the writing. Fix that first, then go write the résumé. It'll take you ten minutes and it'll be a better résumé than the one you'd have written without it.

1. The Core Four Quick Start

Answer these four and you already know whether you have anything. Classification, proof, and references come next — this part just tells you if it's worth the trip.

Your occupation Optional, and the place to start if you're stuck. Type a few letters of your job ("billing," "dispatcher," "controller") and pick the closest of about 900 federal occupation titles. You'll see what the job typically involves, which is a good way to jog your memory about what you actually changed.

What did you actually do? Plain language. "I rebuilt the onboarding checklist," not "spearheaded an initiative."

Before What was true before you touched it?

After What was true once you'd changed it?

Mechanism Why is the "after" connected to you, specifically — and not the market, a coworker, or luck?

2. Make It Defensible Classification & Proof

Now the part that turns a good story into something HR can verify: what field this sits in, who backs it up, and where the receipts are.

Category Pick the lane your claim lives in. If nothing fits, it's probably not a proof point yet — it's an activity.

Revenue

Cost

Time

Risk

People

Process

Job Function Filled in when you pick an occupation in step 1, or choose the broad group yourself. Either way, this shows you what "output" typically looks like in that kind of work.

Employer Which job was this?

Functional Title The role you were actually doing, which may not match your job title

Proof Source Where could you point someone if they asked you to back this up — a report, a dashboard, an email, a performance review, a former manager who'd confirm it? References Who Can Attest to This Up to four people who could confirm this result if someone called them. Doesn't have to be all four — even one solid name beats none.

3. Synthesis Believability Check

This is the interviewer's job, done in advance. If a claim survives this, it'll survive the room.

Your Proof Log

Every claim you've built, sorted by category. Click a row to see it exported into resume, LinkedIn, and interview-story formats.

Filter By Employer / Role Once you've got claims from more than one job, this scopes the log, the comparison below, and any bundle you build to just that one.

No claims saved yet. Build one above.

Prints the claims you've checked, or every claim in the current filter if none are checked.

Compare Against a Job Posting Optional

Paste a job posting. This checks which of your saved claims speak to what it's asking for, and flags what you haven't covered yet. It's a keyword match, not a reading of intent — it'll miss claims that say the same thing in different words, so treat gaps as "check this," not "you're unqualified." Uses the same employer/role filter as your Proof Log above, so if you've narrowed that down, this compares against that same set.

Exported Formats

Same claim, three jobs. Edit freely — these are starting points, not final copy.

How To Read This Caveats

This tool can tell you whether a claim is specific enough to survive a follow-up question. It can't tell you whether the claim is true, whether it's impressive relative to your field, or whether the person reading your resume will care. It also can't manufacture proof that doesn't exist — if you genuinely can't identify a before-and-after, the honest move is to say so and talk instead about scope, judgment, or what you learned. A vague flag here means "sharpen this," not "you have no value."