Skip to content

The job market is moving from credentials to skills ​

By Oleg Sidorkin, CTO and Co-Founder of Cinevva

I watched my cousin graduate with honors in 2023. Computer science degree from a good state school, solid GPA. He spent fourteen months applying to jobs before landing one. Meanwhile, a friend who dropped out sophomore year to build indie games had three offers within a month of deciding to look.

That's no longer an anomaly. It's the pattern.

The numbers caught up with what we'd been seeing ​

By 2025, 90% of HR leaders reported hiring outside traditional four-year degrees (Fortune). A quarter of U.S. companies dropped bachelor's requirements entirely (HR Dive). And if you just finished paying off loans, the next number stings: 94% of employers say skills-based hires outperform those hired on credentials (Forbes).

Verizon now says 99% of its roles don't require a degree. Sergey Brin admitted Google hires "tons" of people without bachelor's degrees. IBM made half its U.S. openings degree-optional through its "New Collar" program.

This isn't companies being charitable. They found that degrees weren't predicting who'd be good at the job.

Why the old system broke ​

Degrees became a lazy filter.

When you're hiring and you've got 400 applications, requiring a bachelor's degree cuts the pile in half. It doesn't tell you who can do the work. It tells you who had the money, the time, and the family stability to sit in classrooms for four years. That correlation with ability was always weaker than we pretended.

Then three things happened at once.

The skills moved too fast. Game engines, AI tools, web frameworks. By the time a curriculum committee approves a course on something, that thing is already outdated. A four-year degree teaches you theory from four years ago, and in tech that's ancient history.

Portfolios became undeniable. There's no need to guess whether someone can code when you can look at their GitHub, or whether they can ship a game when their itch.io page has five finished projects with player reviews.

Companies got desperate. The talent shortage is real. Excluding everyone without a degree means excluding people who might be exactly what you need. Some hiring managers learned this the hard way, after watching self-taught developers outperform their credentialed hires.

The game industry saw this coming ​

I think games have been ahead of the curve here, and the reason is worth understanding.

Studios never cared much where you went to school. They cared what you shipped. A polished 48-hour jam game tells a hiring manager more than a four-year game design degree ever could. It proves you can finish things under pressure, that you made hard decisions about scope, and that the game is playable rather than theoretical.

If you're trying to break into games in 2026, what matters is this (Dice, CombineGR): two or three polished, playable demos, case studies explaining what you did and why, evidence that you finish things, and fluency with at least one major engine, shown through real projects.

Hiring managers are looking for proof rather than potential.

The uncomfortable part ​

One finding frustrated me when I dug into the research.

A Harvard/Burning Glass study found that companies dropping degree requirements often didn't hire more non-degreed candidates. The increase was only about 3.5 percentage points (Forbes). The policy changed and the hiring practices lagged.

That means if you're going the non-traditional route, you still have to work harder. The door is more open than it used to be, but you're not walking through on equal footing yet. Your portfolio needs to be undeniable, and your projects need to speak louder than someone else's credential.

It isn't fair, but knowing it helps you prepare.

What I'd tell someone starting out right now ​

If you're in school, don't stop. But understand that the degree alone isn't enough anymore. Build things on the side. Do game jams. Get a Google Career Certificate or Unity certification. Treat the degree as one credential among several rather than the credential.

If you're not pursuing a degree, you have a different path, and it isn't necessarily a harder one. Build aggressively. Ship things. Document everything. Your GitHub, your itch.io page and your personal site are your credential now.

Either way, practice explaining your work: what you built, why you made the choices you made, what you'd do differently, and what you learned. Interviewers remember people who can articulate their thinking.

This is bigger than hiring ​

The shift in how companies fill roles is also a shift in what we collectively value.

For decades, credentials served as a filter. Expensive and time-consuming, but legible. If someone had a degree, you could assume certain things. It was a signal rather than a direct measure, and it was good enough.

That signal is breaking now. Technology makes it possible to see what someone can do. Remote work proved that outputs matter more than where you sat. AI is making theoretical knowledge less valuable than practical application.

I find this hopeful, even if the transition is messy. The question used to be "where did you study?" Now it's "what can you build?", and that's a better question.

Sources ​

Related: