Imagine two developers applying for the same role.
The first has a computer science degree from a mid-tier university, three years at a company nobody remembers, and a LinkedIn profile that says "passionate about building scalable solutions."
The second has no degree. But they have five shipped products, two of them with real paying users, an open source library with 800 GitHub stars, and a public record of two years of consistent building.
For most of the last century, the first candidate got the call.
That is starting to change.
The System That Built Itself Around Paper
Degrees became the default hiring filter for a simple reason: they were convenient.
A bachelor's degree was shorthand for "this person can learn, persist, and follow through." It was a signal that required no verification. The hiring manager did not need to think. The filter did the work.
For decades it held up reasonably well. Careers were slow. Skills were stable. The things you learned in a four-year program stayed relevant long enough to matter.
Then technology happened.
The half-life of a technical skill collapsed. A framework taught in year one of a CS program is sometimes deprecated before graduation. The most relevant skills in software today are things universities are still figuring out how to teach.
The degree started measuring the wrong thing.
The Cracks Started With the Giants
The first loud signal that the credential system was breaking came from the companies everyone was trying to get into.
Google acknowledged something remarkable: college transcripts and test scores are, in their words, "worthless predictors of later job performance."
IBM went further. At some of IBM's US centers, as many as one-third of employees have less than a four-year degree. IBM's CEO wrote that the company is creating "new collar" jobs in areas like cybersecurity, data science, and AI where highly specialised training matters more than a rigid four-year curriculum.
Apple, Netflix, Bank of America, Shopify. The list of companies removing degree requirements grew steadily. Between 2014 and 2023, the number of roles eliminating degree requirements surged four times.
The direction was clear. The pace was not.
The Bombshell Finding Nobody Talks About
Here is where it gets complicated.
In early 2024, Harvard Business School and the Burning Glass Institute published a comprehensive analysis of actual hiring patterns across thousands of companies. What they found should be pinned to every hiring manager's wall.
While 85% of companies talk about skills-based hiring, only 0.14% of hires are actually impacted by degree requirement removal.
Read that again.
85% of companies say they have moved to skills-first hiring. But only 1 in every 700 hires is actually affected.
The study found that even among companies that eliminated degree requirements, only 1 in every 700 hires was a non-degree candidate.
The policy changed. The behavior did not.
The press releases went out. The actual recruiters kept defaulting to what they knew.
This is not a small discrepancy. It is a chasm between what the industry says it believes and what it actually does when a stack of resumes lands on a screen.
But the Underlying Science Is Unambiguous
Despite the gap between rhetoric and reality, the research on what actually predicts success at work is not ambiguous.
McKinsey reports that hiring for skills is five times more predictive of job performance than hiring based on education and more than twice as effective as hiring based on work experience. Employees without degrees also stay in their roles 34% longer than those with degrees.
Five times. Not marginally better. Five times.
In companies where skills-based hiring is fully implemented, non-degree hires have a 10 percentage point higher retention rate over two years than their degree-holding counterparts. These employees also experience a 25% increase in salary growth.
The companies that have actually made the shift are not doing it for ideological reasons. They are doing it because the numbers work.
Research from Harvard Business Review shows that skills-hired employees have 25% higher performance ratings and 40% lower turnover rates compared to traditionally hired counterparts.
The degree was never actually measuring what companies thought it was measuring. It was a proxy. Proof of work is a direct measurement.
What Proof-Based Hiring Actually Looks Like
The shift from credential-based to proof-based hiring is not just about dropping degree requirements.
It is about changing what counts as evidence.
In credential-based hiring, evidence is: where you studied, what companies employed you, what titles you held.
In proof-based hiring, evidence is: what you built, what you shipped, what your work produced in the real world.
For developers specifically, this looks like:
A GitHub profile with real commit history. Not a burst of commits last month. A consistent pattern of work over years that shows someone who writes code regularly, not someone who prepared for a job application.
Live products with real users. A link anyone can click. Something that works, deployed, being used. For web developers, a strong portfolio of live projects can land a role without any formal degree at all.
Open source contributions. Code merged into projects you did not build. Issues filed and resolved. Pull requests reviewed. Evidence that you can collaborate in unfamiliar codebases.
Documented milestones. First users, first revenue, product launches, technical decisions with outcomes attached. The building record that tells a story of how someone works over time.
This is the profile that wins in proof-based hiring. Not because it is impressive on paper, but because it is verifiable in reality.
The Developer Advantage Nobody Is Using
Here is the thing that makes this genuinely remarkable for developers specifically.
Developers can prove their work in a way almost no other profession can.
You can deploy a product for free. Put the code on GitHub. Write about what you built and why. Let anyone in the world interact with what you shipped.
Self-taught coders who acquired the same skills while managing full-time employment can build a more convincing case for work ethic and motivation than a recent computer science graduate with no external projects.
The ability to show your work publicly is extraordinary. Most professions cannot do this. Lawyers cannot litigate in public. Doctors cannot practice online. Developers can build something real and put a URL in their application.
Most developers still send plain PDF resumes.
The gap between what is possible and what most developers actually do is enormous. And for anyone paying attention, that gap is an opportunity.
The Real Shift Happening Beneath the Headline Numbers
The Harvard study showing only 1 in 700 hires is discouraging if you read it as "nothing has changed."
Read it differently: the 0.14% who are breaking through without degrees are doing so because their proof of work is undeniable.
When a developer's public record of shipped products, consistent activity, and documented milestones is strong enough, the degree requirement gets set aside regardless of official policy. Not because the policy changed, but because the proof is sitting right there and the hiring manager is not going to ignore it.
This is the version of proof-based hiring that is already happening. Not institutionally. Case by case, developer by developer, wherever the proof is strong enough to override the default.
In 2026, 85% of US employers use skills-based hiring practices. Amazon alone hired 2,468 bootcamp graduates in 2024, up 129% from two years prior.
The infrastructure is building. The momentum is real. The developers who have been building their proof of work record for the last few years are positioned for a hiring environment that is becoming more favourable to them every year.
Where the Record Lives
The bottleneck for most developers is not the work. It is the visibility of the work.
You can have five shipped products, a GitHub with consistent history, and a real record of building in public. But if none of it is findable in a coherent professional profile, a hiring manager looking at your application for ninety seconds will default to what they can read quickly.
This is why the infrastructure for documenting and presenting proof of work matters.
GitHub handles code. A personal portfolio handles selected highlights. But neither captures the full picture: the products built, the milestones hit, the development activity, the ongoing record of consistent output that tells the story of a developer who ships reliably over time.
Platforms like forg.to are built for exactly this gap. A professional profile structured around what you have built rather than where you have worked. Products, milestones, verified metrics, and a living record that updates as you build. Not a static snapshot. The actual trail of work.
When proof-based hiring is the standard, the developer with a coherent public record of real work has an advantage that no resume can manufacture.
The Honest Reality Check
The transition from credential-based to proof-based hiring is real but uneven.
Large legacy companies still have HR systems that screen for degrees automatically. The recruiter might believe in proof of work. The ATS filters before the recruiter sees the application.
Startups, growth-stage tech companies, remote-first companies, and technically sophisticated hiring managers are already operating in a proof-first world. LinkedIn predicts that by 2030, over 75% of entry-level tech roles will prioritise skills over degrees.
The transition is happening faster in some places than others.
The practical implication: the developers who build their proof of work record now are positioning themselves for both the current environment and the one that is coming. The proof is useful today at the companies already operating this way. It becomes essential as the rest of the market catches up.
What to Do With This
The research is clear. The companies making the shift are seeing better hires, higher retention, and stronger performance. The developers breaking through without traditional credentials are the ones with the most compelling proof of work.
The actionable version of all of this is simple.
Build things. Ship them. Document them publicly. Keep building.
A coherent public record of consistent output across your GitHub, your portfolio, and your professional profile on forg.to is not just a career strategy. It is the correct answer to the question every hiring process is trying to answer: can this person actually build?
The developers who have that answer readily visible are the ones who win in proof-based hiring, regardless of what their educational history says.
The credential was always a proxy for capability.
Proof of work is the capability.