For a long time, a computer science degree was the expected way into a software job. Job adverts asked for one even when the work did not need it, and many people without one never got past the first filter. That is changing. A growing number of employers, from large technology firms to some government departments, have removed degree requirements from many roles and say they now hire on skills instead.
How far that shift really goes in practice is still being argued about. But over the next few years, you are likely to work alongside more people who came in through apprenticeships, bootcamps, self teaching or a career in something else entirely. It is worth thinking about what that means for you.
First, be careful with assumptions. Someone without a degree may not have met big O notation or the theory behind databases, and may know far more than you about the customers, the domain or how to learn quickly under pressure. Do not treat gaps as weakness and do not assume they are there.
Second, look at how your team onboards people. Many teams quietly rely on everyone having the same background. Jargon goes unexplained, design discussions assume theory nobody taught, and asking a basic question feels risky. Write down the fundamentals your system depends on and make it normal to ask about them. That helps everyone, including the graduate who has forgotten half of what they studied.
Third, if you interview, focus on the work. A realistic task, a conversation about something they built, a chance to show how they think. Those tell you far more than where they studied, whoever is in front of you.
And if you have a degree yourself, it is still worth having. The foundations it gave you are real. But it is a starting point, not a lasting advantage. What will matter is what you keep learning, and how well you help the people around you learn too.
The teams that get this right will be able to hire from a far wider pool of people than the ones that do not, and they will be better for it.
– Asael Shinder
Top comments (0)