blog · 8 min read

Proof of Work: The Hiring Signal That Can't Be Faked

Proof of work: public, dated, linked evidence of what you built. Why it beats a résumé, what counts, and how to build yours without extra effort.

By the FeedCred team · Published August 17, 2026

What is proof of work in hiring?

Proof of work is output made public, before anyone was asking, that a third party can check. A commit on a public repo. A post explaining a system you built. A talk with a video link. It does not have to be impressive — it has to be real. The name comes from crypto, where the same idea applies: effort that anyone can verify, without taking the claimant's word for it. Hiring never had that mechanism. The résumé is a document where the person being evaluated writes the evaluation.

What counts as proof of work?

Anything public, dated, and attributable — those three properties are what make a claim checkable.

• Public — it happened where other people could see it. A private accomplishment you can only describe is a claim, not evidence.
• Dated — it happened at a specific time, before the interview and the job ad. A trail that predates the application is worth far more than a retroactive one.
• Attributable — the account that did it is provably yours, verified by the platform itself, not a name-matched guess.

The three properties work together: a post that is public, dated, and attributable carries a reputation cost. Faking a year of public technical writing is harder than doing the work — which is the entire point.

Why is proof of work better than a résumé?

A résumé is cheap to fake; proof of work is expensive to fake. Résumés measure what you claim. Interviews measure how you perform under pressure on one day. Proof of work measures what you did in public over time. The person who explains queueing systems in public posts probably understands queueing systems. The person with merged pull requests on an open-source project the team already uses has effectively been reviewed by that project's maintainers.

It also solves the AI problem from the other direction. Generative AI can write any résumé, but it cannot backdate your public presence. When every document is suspect, the dated public record is the only input the tooling cannot rewrite. For the numbers behind why this matters, see why your résumé is lying about you.

What does a proof-of-work profile look like?

FeedCred collects this signal into one profile, verified by platform OAuth before anything is read. The result is a dated, source-linked record: a verified bio backed by the posts it came from, plus the links you chose to share. Here is the shape of it:

fig. 1 — a FeedCred profile (illustrative)

Is proof of work fair to people with private careers?

It is an honest trade-off, not a judgment. Internal impact, soft skills, and confidential work will never appear in a public record. Proof of work is not a complete picture of a person — it is the most trustworthy slice of one. A résumé that says "led the team through the outage" and a public post from that quarter about incident response are compatible; one just costs more to fake.

Some companies discourage public writing, and some people value privacy. That is why FeedCred is opt-in, platform by platform, with deletion available at any time. The consequence is simple: a candidate without public work is evaluated the old way, on claims. The asymmetry is the product.

How do you build proof of work?

Small, regular habits beat big one-off efforts. You probably already have most of what you need:

• Commit in public — push the scripts, notes, and experiments. A repo that shows how you think beats a profile that says you are "passionate."
• Write a short post after shipping — explain one decision you made and why. Two paragraphs. Dated proof, zero editing effort.
• Answer questions in public — a Stack Overflow answer, an HN comment, a GitHub issue reply. Attribution plus a date.
• Do not write for recruiters — proof of work works because it is unselfconscious. The unpolished post is worth more than the polished one.

How should recruiters read proof of work?

Look for density, specificity, and consistency — not keywords. Density: does the trail go back years, or two weeks? Specificity: does the person explain decisions, or retweet them? Consistency: does the GitHub match the X account match the claimed job history? A burst of posts right before applications went out is itself a signal, and a useful one. If you are a recruiter looking for the platforms where this signal exists, start with our LinkedIn alternatives guide.

FAQ