Becoming a full-stack developer after high school

The question I get most on YouTube is some version of this one. I have finished 12th, there is no money for an engineering college, can I still get paid to write software. The answer is yes, and the reason people distrust that answer is that it usually arrives with something being sold at the end of it.

So here is mine with nothing attached to it. I did a BCA at a college in Indore you have not heard of, between 2022 and 2024, and I was building the whole time I was enrolled. Since then, across client projects and my own products, nobody has asked to see that degree. Several people have asked for a URL.

That gap is the thing to understand before you pick a route. What follows is the order I would learn this in if I were starting again the week my results came out, and the places where it takes longer than the roadmaps suggest.

What the numbers say and what they do not

Stack Overflow runs the largest annual survey in this industry. The 2025 edition was open from 29 May to 23 June 2025 and used 49,009 responses from 177 countries.

In it, 42.1 percent of respondents gave a bachelor's degree as their highest qualification and 26.2 percent gave a master's. Around a quarter hold neither: 12.8 percent went to college without finishing a degree, 7.5 percent stopped at secondary school, 3.3 percent hold an associate degree.

There are two readings of that. The one bootcamp advertising prefers is that a quarter of working developers got there without a degree, which is true. The one it skips is that roughly three quarters did have one. What I would take from both is the thing I did without planning it: get whatever degree you can afford, treat it as the cheapest years of time anybody will ever hand you, and spend those years building. The BCA did not teach me the stack. It bought me the hours to learn it.

The survey is also self-selecting. Respondents were recruited mostly through Stack Overflow's own channels, so it counts people who read Stack Overflow rather than a clean sample of everyone employed. I still use it, because it is the largest thing anyone has, and a number with a known bias tells you more than an anecdote with an unknown one.

Full-stack is the most common job on the survey

Among the same respondents, 27 percent described their job as full-stack developer. Back-end came second at 14.2 percent and front-end at 4.3 percent. In India the full-stack figure was 25.3 percent.

Beginners tend to read full-stack as a rank you get promoted into after some years on one side. It is closer to the opposite. Full-stack is the ordinary shape of a job at a company small enough that one person has to cover the form, the endpoint it posts to and the table the data lands in. Those are also the companies willing to hire someone with no degree and two years of public work, which makes it the easiest door to get through and the one that asks you to cover the most ground.

The order I would learn it in

One language first, until you can hold a small program in your head without reading it back. JavaScript, because it is the one that runs on both sides of the stack and you are going to need both sides. Loops, functions, arrays, objects, and what asynchronous means, before you touch any framework.

Then HTML and CSS until you can rebuild a screenshot without a component library. Flexbox, grid, and the fact that a page has to work at 360 pixels wide before it works at 1440, because in this market most of the people using your work arrive on a phone.

Then the browser as a machine rather than a canvas. What a request is. What the network tab is telling you. How to send a fetch and handle the case where it comes back wrong, which is the case tutorials leave out.

// The version in the tutorial
const data = await fetch(url).then((r) => r.json());

// The version that survives a stranger using it
const res = await fetch(url);
if (!res.ok) return showError(res.status);
const data = await res.json();

Then one server framework and one database, in the same project, at the same time. Express with MongoDB or Postgres, either is fine. Doing them together matters because the thing you are learning is not the framework. It is what has to happen between a form submission and a row existing.

Then React, and not before. A library whose whole job is managing state is hard to see the point of if you have never had state get away from you.

Deploy before you learn the next thing

The rule that changed my first year more than any course did: nothing counts until it is on the internet at an address a stranger can open. A project on localhost has not been finished. It has been written.

Deploying is where you meet environment variables, build failures that do not reproduce locally, a database that wants a connection string you cannot commit, and CORS. Employers assume you have hit all four. None of them appear in a tutorial that ends at npm run dev.

Nobody can check whether you understand React. Anybody can check whether the URL loads.

This is the same reason I send clients a working demo every week instead of a progress update. A thing you can click is the only claim about software that cannot be made optimistically, and that holds whether the person reading it is paying you or deciding whether to.

What a portfolio has to prove

When somebody sends me their work, I look for the same few things and it does not take long. Is it live. Does it take input from someone who is not you. Does it do something sensible when that input is wrong. Is there a commit history showing it was built across weeks rather than pasted together in one evening.

Three tutorial clones fail all four, because following along proves you can follow along. One small tool that ten people use passes all four, and its being small does not count against it. An attendance tracker one college society runs on tells me more than a Netflix clone with no data in it.

That is also where the degree stops mattering. It has to be believed. A URL can just be opened.

Where this takes longer than people say

The six-month roadmap is not lying about the syllabus. You can cover that list in six months. It is lying about the distance between having covered something and being able to use it while something is broken and you do not yet know why.

Debugging is most of the job and close to nobody teaches it. There is a separate post on this blog about reading an error message, and that one skill decides whether you can work without somebody sitting next to you.

Plan for eighteen months to two years between your first line of code and being worth hiring, if you are building most days. That is roughly what it took me, and I had the advantage of being enrolled in something that gave me time nobody expected me to spend earning.

One more thing about the plan people usually arrive with, which is to learn this and then work remotely for a company abroad. In the same survey, 30.5 percent of Indian respondents worked fully in person against 25.6 percent fully remote. India was the only country broken out where in person came ahead of remote. Remote is worth wanting. It is not the entry-level offer, and a plan that depends on it in step one has a weak step one.

What I got wrong

For most of my first year the number I was optimising was how many repositories I had. Forty-eight of them are still public. Clones, games, small tools, anything that covered a part of the stack I had not touched yet.

How many of them had a user was zero, and I did not notice that this was the number that mattered. Breadth is easy to count, which is most of why I was counting it. The projects that taught me anything were the few where somebody who was not me opened the thing and then told me what was wrong with it.

Starting again I would build fewer things and put every one of them in front of somebody. Not for the portfolio. Because a stranger finds the case you did not think of on their first try, and that case is the entire lesson.

If you want one starting point

Pick something small that a person near you currently does by hand. A society's attendance sheet, a shop's order list, a form somebody in your family fills in on paper. Build it this month and put it somewhere they can use it badly.

Then do that again. Ten of those, deployed, with commits going back a year, is a portfolio. That is the thing I have been asked for. The degree, so far, has not come up.

The route is not complicated and it is not quick. Those are two different complaints, and people asking me this question usually mean the second one.