How to become a web developer without a degree

The short answer

The route that works without a degree: learn HTML and CSS properly, then JavaScript, build four real projects that live on the internet, and apply with those.

Expect six to twelve months part time. Nobody can promise you a job at the end, and anyone who does is selling something. What is true is that this field hires on evidence more readily than most, and evidence is something you can create without permission.

Stage 1: HTML and CSS (4 to 8 weeks)

Not a weekend skim. Properly:

• Semantic HTML, so your pages are readable by browsers, screen readers and search engines.
• The box model, until it is boring.
• Flexbox and grid for layout.
• Responsive design with media queries, mobile first.
• Accessibility basics: alt text, labels tied to inputs, keyboard navigation, real color contrast.

Accessibility is the part beginners skip and interviewers notice. It is also the right thing to do, which makes it an easy sell. The MDN web docs are the best free reference there is, and there is a starter guide to HTML and CSS here.

Stage 2: JavaScript (8 to 12 weeks)

Variables, functions, arrays and objects, then the DOM: finding elements, responding to clicks, changing content. Then fetching data from an API and rendering it.

This is the stage where "I made a page" becomes "I made a thing that does something", and it is also where most people slow down. Push through by building rather than reading.

Stage 3: one framework (4 to 8 weeks)

React is the most common in job listings, so it is the default choice. Learn it after plain JavaScript, not instead of it, because a framework built on shaky fundamentals gets shaky fast.

Do not learn three. One, properly, with a project you finished.

Stage 4: the four projects

Your portfolio matters more than everything above. Aim for four, each finished and live:

1. A responsive marketing page, built from a design you did not make. Shows you can match a spec.
2. An interactive app that uses an API: weather, movies, transport, whatever interests you.
3. Something with real data, ideally with a small back end or a database behind it.
4. A rebuild of something that annoys you. A local business site, a broken booking form. This one interviews well because you can explain the decisions.

Host them so they open in a browser, and put the code somewhere public with a README explaining what it does and what you would improve. That last line demonstrates judgment, which is what separates a junior worth hiring from one who has only followed tutorials.

A live link a hiring manager can click beats a certificate they have to take your word for. Both is better than either.

The honest state of junior hiring

Junior web roles are competitive. There are more entry-level candidates than entry-level jobs in most markets, and that has been true for a while. The US Bureau of Labor Statistics profile for web developers gives a broad outlook, and your local market matters far more than any national figure.

What this means practically:

• The portfolio bar is higher than it was. Four good projects, not two.
• Adjacent roles are a real route in. Support, QA, content management and internal tooling all sit next to development, and moving across from inside a company is often easier than getting hired from outside.
• Freelance work counts as experience. Small business sites, theme customization, landing pages. It pays badly at first and it puts real work on your CV.
• Specific beats general. "I build fast, accessible marketing sites" gets more responses than "junior developer looking for opportunities".

What a degree does and does not do

It opens doors at some large employers and graduate schemes, and it is genuinely irrelevant at many product companies and agencies. It teaches computer science, which is not the same thing as web development, and which matters more in some roles than others.

If you already have a degree in something else, that is fine and occasionally an advantage: a developer who understands accounting, healthcare or logistics is more useful in those industries than one who does not.

When this is not the right path

If you like the idea of building websites but find debugging maddening rather than satisfying, notice that early. Debugging is the job. There is no version of this where it is not.

If your real goal is design rather than code, UX/UI design is a different and shorter path to a similar-looking outcome.

Where to learn it

Start with the HTML and CSS certificate, then add Python or SQL when you reach back-end work. One subscription opens the whole Programming & Web Development school, so the path can change without a new purchase.

Learn, build four things, put them online. That is the entire route, and the middle step is the one that decides it.