Proof of Work Isn’t a Score

Numbers are convenient.

They make complicated things easy to compare.

• A profile gets a score.
• A candidate gets a percentage.
• A contribution becomes a metric.
• A person becomes a ranking.

The problem is that professional ability rarely works that way.

The temptation of the score

Imagine two engineers.

One has thousands of GitHub stars.

The other has contributed to a small number of critical infrastructure projects that few people outside their teams ever noticed.

Who is the better engineer?

There isn’t enough information to answer.

A single number cannot capture it.

And that is precisely why Merged doesn’t believe Proof of Work should become another scoring system.

Evidence needs context

Proof of Work is not about counting everything someone has ever done.

It is about making meaningful evidence easier to understand.

• A repository can tell you something.
• A contribution can tell you something.
• A project can tell you something.

But each signal needs context.

• What was built?
• How significant was the work?
• How long has someone been working in that area?
• Is the activity recent?
• What technologies are involved?
• Does the work reflect a recurring technical interest?

The goal isn’t to turn those answers into a mysterious number.

The goal is to make the evidence visible.

More activity doesn’t automatically mean more ability

This distinction matters.

Someone can have hundreds of repositories without building anything particularly meaningful.

Someone else can have a small number of repositories containing years of thoughtful engineering work.

Counting activity alone would miss the difference.

The same applies to stars, commits, followers and contribution graphs.

Metrics can provide signals.

They shouldn’t become verdicts.

Show the evidence

Consider the difference between these two profiles.

Profile A

Senior Software Engineer Python AWS Kubernetes 10 years experience

Profile B

Senior Software Engineer Python · Go · Kubernetes Built and maintained distributed backend systems. Featured projects. Open-source contributions. Recent technical activity. Relevant work over time.

The second profile doesn’t claim to be better.

It simply provides more context.

That is the purpose of Proof of Work.

No black box

Professional decisions are too important to hide behind unexplained algorithms.

If a company discovers someone through Merged, the reason should be understandable.

• Maybe their work aligns with a technology stack.
• Maybe their recent projects are relevant.
• Maybe their technical experience overlaps with the company’s needs.

Those signals can help discovery.

But the final judgment should remain human.

Evidence informs. People decide.

Proof of Work also protects developers

There is another side to this.

Developers shouldn’t have to constantly perform professionalism to remain visible.

• They shouldn’t have to publish content every week.
• They shouldn’t have to collect endorsements.
• They shouldn’t have to optimize their profile for an algorithm.

Their work already provides information.

The network should make that information useful without turning professional identity into a popularity contest.

The future isn’t about better scores

As professional networks become more data-driven, it will be tempting to create increasingly sophisticated scores.

• A technical score.
• A reputation score.
• An employability score.
• A culture-fit score.
• A hiring score.

More numbers don’t necessarily mean better decisions.

Sometimes the better product is the one that removes the number and shows you the evidence instead.

Evidence over impression

That’s the principle.

Not:

How impressive does this person look?

But:

What have they actually created, contributed to and demonstrated?

Not:

What score did the system give them?

But:

What evidence can I inspect?

That difference is small in language.

It is significant in product design.

Proof of Work shouldn’t tell you who to choose. It should give you better information with which to make your own decision.