A resume is a stack of claims. Proof of work is what makes a hiring manager stop wondering whether they’re true.
Hiring managers aren’t buying claims – they’re buying the lowest-risk bet in the room. Proof of work hands them that bet: a case study they can read in 90 seconds, a thing you built that does what the role does, or a public trail they find when they Google you before the call. Most candidates skip all three, then wonder why they lose to someone with a thinner resume.
Why a resume can’t close the deal on its own
Every line on a resume is you describing you. “Led the migration to a new billing platform.” “Cut churn 30%.” The hiring manager reads that and does the only thing they can do: decide how much of it to believe.
That’s the whole game. Hiring managers don’t pick the most impressive candidate. They pick the one who’s clearly already done this job, because that person can operate on day two without a 90-day ramp. Impressive is a bonus. Obvious is the hire.
The research agrees. Schmidt and Hunter’s meta-analysis of 85 years of hiring studies found that work sample tests – watching someone do a piece of the actual job – predicted performance better than any other single method they measured. Better than a structured interview. Far better than years of experience or years of education. Hiring managers haven’t read the paper, but they act on the same instinct: show me, don’t tell me.
So when two finalists look the same on paper, the one who handed over evidence wins. Not because the evidence dazzles anyone. Because it removes doubt, and doubt is what kills offers.
What proof of work is (and what it isn’t)
Let me flag the failure mode first: proof of work isn’t a longer resume. It isn’t a portfolio site with a wall of company logos. It isn’t a cover letter, which is just more claims in paragraph form.
Proof of work is anything that lets the hiring manager watch you do the job without you in the room. Three tests:
- Can they see it without you narrating? If it only makes sense when you explain it on a call, it’s a story, not proof.
- Does it map to something in the job description? They handed you their order. Serve what they asked for, not a dish you’re proud of.
- Could they forward it? A one-pager gets passed to the panel. A verbal anecdote dies in the room.
Here’s the verb test I use with clients on AI interview questions, and it works for everything: “I chatted about it” is nothing. “I created one” is a one-time artifact. “I built it” means a thing exists that keeps working after you walk away. Proof of work lives at “built.”
Artifact one: the one-page case study
Take your best interview story and put it on one page. Problem, constraint, three actions, result. Add a number that’s directionally truthful – the right ballpark, not a forensic audit. If a diagram helps, include one. If a screenshot of the real dashboard would breach an NDA, sketch the shape of it instead.
The rules:
- Ninety seconds to read. If it takes longer, cut.
- Your three actions are the headings. That’s signposting on paper: the reader takes away exactly three things, the same three you’d say out loud.
- No confidential data. The story, not the spreadsheet.
Where it goes: in the thank-you note after the hiring-manager round. “You asked about the billing migration, so I put the full arc on one page. Easier than relying on my rambling.” That’s the version of you that gets discussed in the debrief, because it’s the version that’s still on their desk.
Artifact two: build the thing before the interview
If the job description says the role will do X, and you’ve done X once, go do it again this weekend. Set up the automation. Write the analysis. Build the small tool. Then walk into the interview able to say “I built” instead of “I’ve worked with.”
I give clients this instruction on AI-forward roles: if the JD wants someone who ships with AI and your only example is a one-off chat, build a project this weekend that does the thing you did. Not because the project impresses anyone. Because next week you’ll speak from experience instead of theory, and theory sounds junior while lived experience sounds senior.
The boundary matters, though. Show how you think, not a finished product. Enough to demonstrate the approach, never a deliverable they could ship without hiring you. If they’re asking for real production work with no offer on the table, that’s a different problem – here’s how to tell a test from free work.
Artifact three: the public trail
Hiring managers Google finalists. What they find is either nothing, a dormant profile, or evidence.
A teaching post is a work sample. If you write three short posts about the problem your target role solves – how you’d diagnose it, what most teams get wrong, what you’d do first – a hiring manager who reads one of them has effectively watched you think. That’s not a brag. It’s the same evidence as the case study, sitting in the place they’ll look before they ever talk to you.
Two rules so this doesn’t turn into content for its own sake:
- Write about their problem, not your search. “Open to work” tells them nothing. A post on why most churn dashboards measure the wrong thing tells them plenty.
- Three posts before the loop starts, not thirty. You need a trail, not a channel. If you want the mechanics, start with posting on LinkedIn so recruiters come to you.
How to use proof of work without looking desperate
One artifact per round. Tie each one to a requirement in the job description, and hand it over at a natural moment: the close of an answer, the thank-you email, or the “anything else you’d like us to see?” question near the end. Don’t open your tell-me-about-yourself with a slide deck.
And don’t over-polish. The candidate who sends a clean one-pager reads as a safe hire. The candidate who sends a 40-slide deck reads as someone who’ll spend their first month making decks.
In my practice, the candidates who reach the hiring-manager round with an artifact in hand get a different kind of conversation. The interviewer stops probing whether the story is true and starts asking how you’d do it here. That shift is the whole point. Doubt is gone, so they’re already treating you like the hire.
Proof of work FAQ
Isn’t a portfolio only for designers and engineers?
No. A product manager has roadmap decisions. A finance lead has a model. A customer success manager has the playbook that cut churn. Every role produces artifacts, but most people never write them down.
Do I need a personal website?
Not to start. A PDF one-pager and three LinkedIn posts do the job. A site helps once you’ve got more than one artifact to organize.
Won’t a hiring manager think I’m doing free work?
Not if you keep it to how you think rather than what they could ship. Diagnose the problem, name the options, say what you’d do first. Stop before the deliverable.
What to do next
If you want to know what a slow search is costing you while you build these, run the job search cost assessment. Ninety seconds, and it gives you a monthly dollar figure plus the stage of your search that’s leaking the most.
If you want to understand the decision your artifact is feeding into, read How Hiring Managers Decide: Obvious Beats Impressive next.
If you’d rather have someone look at your stories and tell you which one deserves a page, book a free strategy call.