A recruiter asked for my resume. I sent it, along with the thing a resume can't do.

A recruiter asked for my resume last month. I sent it, because that is how the pipeline works. But I also sent the thing a resume cannot do: a link to work that can be checked.

Here is the asymmetry nobody in hiring talks about. A resume asks you to trust. Proof of work lets you check. Those are completely different requests to make of a stranger.

Every resume in your inbox says approximately the same thing: senior, results-driven, led cross-functional initiatives, improved performance by an impressive percentage measured by nobody. The format rewards confident assertion, and now that AI writes them, the assertions are better-written and even less informative. The signal-to-noise ratio of the resume was already low. It is now approaching zero.

Checkable work resists inflation. A production system either runs or it does not. A postmortem either names the real mistake or reads like PR. An architecture decision written down two years ago either aged well or it did not, and you can see which. Nobody can prompt-engineer their way to a system that has been serving real users for a year.

This is not an argument against resumes. Pipelines need them, and mine exists. It is an argument about where the actual decision should happen. The resume gets you the conversation. The checkable work is what an interviewer should spend the conversation on: pull up something the candidate owns and ask why questions until the story either holds or it does not.

For recruiters, there is a practical edge here. The candidate you submit with verifiable work attached survives the hiring manager's scrutiny at a much higher rate, because the claims were checked before the onsite instead of during it. Your shortlist gets a reputation for holding up. That is worth more than volume.