A 12-Week Free Plan to Become a Junior Web Developer in 2026

Let us be upfront about two things. First, twelve weeks is an aggressive timeline. It assumes 4 to 6 hours a day, and many people will need longer, which is fine. Second, the junior developer market in 2026 is competitive, and AI coding assistants have raised the bar for what "junior" means. Employers now expect juniors to ship working features, read unfamiliar code and use AI tools sensibly, not just write a to-do app.

That said, a focused 12 weeks can get you to a portfolio that is genuinely job-ready to apply with. Here is the plan, using free resources only.

The stack

Keep it simple and mainstream: HTML, CSS, JavaScript, TypeScript, React, Node.js with Express, PostgreSQL, Git. It is the most widely used combination in job listings and the one with the most free learning material. Resist adding extra frameworks until you have shipped projects with these.

Weeks 1 to 2: HTML, CSS and Git

• Learn:** semantic HTML, the box model, Flexbox, Grid, responsive design, accessibility basics.
• Resources:** freeCodeCamp's responsive web design curriculum; Kevin Powell's YouTube channel for CSS layout; MDN Web Docs as your reference.
• Git:** basic commits, branches and pushing to GitHub from day one.
• Build:** a responsive personal site and a clone of a landing page you like. Deploy both to GitHub Pages or Netlify.

Weeks 3 to 5: JavaScript properly

• Learn:** variables, functions, arrays and objects, DOM manipulation, events, array methods, modules, fetch, promises and async/await.
• Resources:** a beginner JavaScript course (freeCodeCamp's YouTube courses, or Chai aur Code in Hindi), then Namaste JavaScript for how the language works underneath: scope, closures, the event loop.
• Build:** a quiz app, a weather app using a public API, and a small game such as tic-tac-toe or a memory game.

This is the most important stage. If your JavaScript is shaky, React will feel like magic and debugging will be painful. If week 5 ends and you are not comfortable, take another week.

Week 6: TypeScript basics

• Learn:** types, interfaces, generics at a basic level, typing functions and API responses.
• Resources:** the official TypeScript Handbook; free TypeScript courses on YouTube.
• Build:** convert your weather app to TypeScript.

Many companies now default to TypeScript, and it makes your code easier to read in interviews.

Weeks 7 to 8: React

• Learn:** components, props, state, effects, lists, forms, routing, fetching data.
• Resources:** the official React docs at react.dev, which are excellent and free, with a YouTube course alongside if you prefer video.
• Build:** a React app with routing and an external API, such as a movie search, recipe finder or job board front end.

Weeks 9 to 10: Backend and database

• Learn:** Node.js, Express, REST API design, PostgreSQL, SQL basics, authentication (sessions or JWT), environment variables.
• Resources:** freeCodeCamp backend courses on YouTube; a free SQL course such as Alex The Analyst's playlists for the query basics.
• Build:** an API with user accounts and CRUD operations on a PostgreSQL database.

Weeks 11 to 12: The portfolio project

Build one full-stack app that solves a real problem, ideally for someone you know: a booking page for a local tutor, an inventory tracker for a small shop, a study group planner. Include:

• Authentication.
• A database with at least two related tables.
• A clean, responsive React front end.
• Error handling and loading states.
• Basic tests for the most important logic.
• Deployment to a free tier, with a live URL.
• A README with screenshots, the stack, and what you would improve next.

One real, polished project is worth more than five tutorial clones.

Using AI assistants without hurting yourself

You should use AI coding tools; employers expect it. But during these 12 weeks, use them as a tutor and reviewer, not an author. Write the code first, then ask for a review. Ask for hints when stuck, not complete solutions. Never commit code you could not explain line by line. In interviews you will be asked to explain your projects, and "the assistant wrote it" is not a good answer.

Tracking it all

Twelve weeks across a dozen playlists and docs is a lot to keep straight. Keep a simple weekly log: what you learned, what you built, what you got stuck on. For the YouTube portions, pasting each playlist into Filow gives you progress tracking per video, timestamped notes and quick quizzes, which helps when you need to revisit something from week 3 during week 10.

After week 12

• Apply** while continuing to build. Do not wait until you feel ready; nobody does.
• Practice interviews:** JavaScript fundamentals, small coding problems, explaining your projects.
• Contribute** small fixes to an open-source project, which shows you can work in someone else's codebase.
• Keep shipping:** a small feature or project every couple of weeks keeps your GitHub active and your skills sharp.

If it takes you 20 weeks instead of 12, that is completely normal. The plan is the order and the emphasis on building. The timeline is just a target.