Do you need a degree to work in IT?

The short answer

For most developer roles, no. What's assessed is what you can do and what you've built. But there are places where it's harder without one, and there are things it genuinely provides.

Where a degree is required

Government bodies and companies tied to them. Formal requirements are common there and hard to get around.

Some large companies' internships. Not always a hard condition, but when hundreds of applications are screened, a degree helps past the first filter.

Working abroad. Many countries weigh education for a work visa.

Theory-heavy fields. Machine learning, computer vision, signal processing — the mathematics matters there, and universities teach it systematically.

What a degree actually gives you

Not knowledge of a programming language. Universities teach that indifferently, and any self-taught learner will outpace them on specific technologies.

Foundations that are hard to acquire alone. How algorithms and data structures work, networks, operating systems, database theory. Self-taught people usually pick these up piecemeal and later.

The ability to grind at something uninteresting. An underrated skill: a lot of work is tedious, and tolerance for that is valued.

A network. Coursemates who in five years will have vacancies and referrals.

How people manage without one

They substitute evidence. Employers want confidence you'll cope; a degree is one way to provide it, not the only one.

What works instead:

• Finished projects anyone can open and inspect.
• Contributions to open source — a public record of how you work.
• Team experience confirmed by the people you worked with.
• Adjacent experience from a previous profession, if you have it.

In practice, someone without a degree but with three finished pieces of work and team experience gets through screening more easily than a graduate with no project of their own.

Is it worth enrolling for this

If you're already working and want to close a formality, sometimes yes, part-time.

If you're choosing between four years at university and a year of self-study followed by a job, the second usually reaches income faster. But you'll have to acquire the theory yourself, or you'll hit a ceiling in a couple of years.

A reasonable compromise: go to work and read the missing theory as the need arises. Once you're writing code, a book on algorithms reads very differently than it did in your second year.

What matters more than a degree

Anything checkable: a working link, a commit history, a confirmed contribution to a team project. All of it answers the employer's question better than a certificate — because it describes what you did, not what you were taught.