How to become a full stack developer in Nepal, the first four weeks

To become a full stack developer in Nepal, do not start by choosing MERN or Django. Spend the first four weeks on four things in order: how the web works, reading JavaScript with Git, putting one app online, and one database with a login.

That order works for every stack. It is also what full stack job posts in Nepal ask for, under the stack names.

What do full stack jobs in Nepal actually ask for?

Look at two full stack developer posts on Semesteria, one in Kathmandu and one in Pokhara. The Pokhara post is for a junior. Its must-have skills are HTML, CSS, JavaScript and problem solving. React and Node.js are only nice to have.

The Kathmandu post asks for JavaScript, HTML, CSS, Node.js and React. Both posts list Git as a tool. Both want some database knowledge, PostgreSQL in one and MySQL in the other.

So the stack name changes from post to post. The base under it stays the same. Your first month should build that base.

Week 1: How does a web page actually load?

Start with what happens when you type an address and press Enter. The browser asks DNS for the server's real address. Then it sends an HTTP request, and the server sends back a response with a status code like 200 or 404.

MDN's free page How the web works explains this in plain words. Read it, then open any site, press F12 and watch the Network tab while the page loads. Every line there is one request.

In the same week, learn the three parts of any web app. The frontend is what the user sees. The backend is the server side. The database keeps the data. Write one plain HTML page with a little CSS, so these words have something real behind them.

Why this comes first: most bugs you meet later are a request that went wrong. If you can read a request and its status code, you can find where it broke.

Week 2: Read JavaScript, and save every step with Git

Learn to read JavaScript before you try to write a lot of it. Variables, functions, imports, and async and await are enough at first. When an AI tool writes code for you, reading it is the skill that matters. A missing await is a common bug, and you only catch it if you can read the line.

Learn Git in the same week. A commit is a snapshot of your project at one moment, so you can always go back to it. Make one repository, commit your HTML page, and push it to GitHub. Both job posts above list Git, and your GitHub profile becomes the place where your work is seen.

Git also suits slow or patchy internet. The free Pro Git book explains that most Git work happens on your own computer. You can keep committing when the connection drops, and push when it comes back.

Week 3: Put one small app online

Our pick: get something live on the internet in your first month, not after six months of tutorials. A live link is something you can send to anyone. Putting an app online also teaches you early about settings and secret keys, before a mistake with them costs you.

The free Next.js course starts from a starter app and builds a full dashboard, step by step. Next.js lets one app hold both the frontend and the backend, so a beginner manages one project, not two. Vercel's Hobby plan is free, so a learning project can live there at no cost.

You do not need a new laptop for this. On 8 GB of RAM, run one app at a time and close the rest.

Week 4: One database, and a login

Now add data. Learn what a table is, how two tables relate, and how a form saves one row. PostgreSQL is a good first database, and it is the one named in the Kathmandu post.

Then add signup and login. The key rule is that each user sees only their own data, and the server checks this on every request. An app that skips this rule can show one user's records to another user.

By the end of week 4 you have a small app with real data and real users. That is not a job yet. It is the base that every stack builds on.

When should you pick MERN, PERN or Django?

Pick after week 4. By then you know what a frontend, a backend and a database each do. A stack is then only a choice of tools for each part.

Choose the stack that shows up most in the posts you would apply to, and learn it deeply. Four weeks gives you the base, not a job. After it, keep building small apps and keep reading real job posts.

How Saarathi Academy teaches these weeks

At Saarathi Academy in Old Baneshwor, Kathmandu, our Full Stack Development with Vibe Coding course follows this order. It runs six weeks, two hours a day, Monday to Friday. Week 1 covers how the web, data and apps work, including DNS, HTTP, the frontend, the backend and the database.

Our course moves a little faster than the plan above. Week 2 spends about three hours on reading JavaScript and TypeScript, sets up Git and GitHub, and puts a Next.js starter app live on Vercel by Day 5. Week 3 adds Supabase with PostgreSQL through Prisma, plus real signup and login. Week 4 builds the full features and a Flutter app on your phone that uses the same backend.

Classes run in person and online. There are up to 10 students in the classroom per batch, and mentors still do the job they teach. The course page also says plainly that a junior developer job needs more practice after the course, or our Backend Engineering course. The whole syllabus is public before anyone pays.

Start tonight

Read MDN's How the web works page. Then open the Network tab on any site, and find one request with a 200 status and one with a different code. When that makes sense, start chapter 1 of the free Next.js course.

When you want a mentor to check your work every week, read the course page and the full syllabus.