Module 0 ¡ What JavaScript Is, Where It Runs, and How an Engine Runs It
The Job Market, Honestly: What JavaScript Gets You and What It Does Not
In this lesson
- Read three named numbers about JavaScript and hiring, each with its source and its date.
- Describe what a junior frontend, a junior backend and a junior full-stack role usually ask for.
- List what JavaScript alone does not get you, and which of those this track covers.
Maria's cousin did a twelve-week JavaScript bootcamp and got a job as a frontend developer. Now the whole family says "just learn JavaScript". Maria asks the question nobody at the table asked: is that the whole story?
It is not, and it is not a lie either. JavaScript is the most used language among working developers, and that is measured, not guessed. But a language is one line of a job post, and her cousin's post had six more.
This lesson gives you three numbers with their sources, so you can check them yourself. Then it reads job posts the way a hiring manager writes them. It ends with an honest list of what JavaScript alone does not get you.
Number one: the Stack Overflow Developer Survey 2026
Every year Stack Overflow, a question-and-answer site millions of programmers use, runs a large public survey. One question asks which languages you did extensive development work in over the past year. In the 2026 survey, 14,099 people answered it.
JavaScript came first, with 62.0% of them. The survey notes it has been at the top of that list for twelve years in a row. Here are the top eight, drawn to scale.
Read it carefully, because it is easy to over-read. These are people who chose to answer a survey, mostly people who already use Stack Overflow. A percentage here says how many of them used JavaScript. It does not say how many jobs ask for it.
Notice also what sits next to JavaScript. HTML/CSS is third and TypeScript is sixth, and both are things a JavaScript developer is expected to know. So the chart says JavaScript is everywhere, and it quietly says JavaScript rarely comes alone.
Number two: GitHub Octoverse 2025
GitHub, the site that hosts much of the world's open-source code, publishes a yearly report called Octoverse. The 2025 report, published on 28 October 2025, counted how many people contributed code in each language.
Its headline: in August 2025 TypeScript passed both Python and JavaScript and became the most used language on GitHub. Python was second and JavaScript third.
That sounds like bad news for JavaScript until you remember lesson 01. TypeScript is JavaScript with types written in, and it turns into plain JavaScript before it runs. Every TypeScript developer writes JavaScript all day. So for a learner the two rows point the same way: learn JavaScript first, and TypeScript is a short step after it.
So the second number says the JavaScript family is growing, and the typed branch is growing fastest.
Number three: one morning on bdjobs.com
Global surveys say little about your city. So here is one local signal, with its limits stated.
On the morning of 7 October 2026 (Bangladesh time), a keyword search for "javascript" on bdjobs.com, one of Bangladesh's largest job boards, showed 31 job posts for 75 or more vacancies. The same search for "python" showed 34 posts for 79 or more vacancies.
Four honest warnings come with those two numbers.
- It is one board on one morning. The counts change every day.
- A keyword search finds posts that contain the word. A post that asks for "React" or "Node.js" and never writes "JavaScript" is missed, so the real number is higher.
- Many good jobs are never posted on a board; they are filled through people and referrals.
- Remote jobs for foreign companies are not in this count at all.
So the local number is small, real and incomplete. Exercise 2 asks you to measure it yourself on the day you read this.
Three junior roles, three job descriptions
"Junior" means a first or second job, usually with under two years of experience. The three descriptions below are written from the shape that real junior posts share. They are not copied from any one company.
Junior frontend developer. Builds the part of a website or web app that people see and click. The post asks for HTML, CSS and JavaScript, one framework (React most often) and Git. It also asks for fetching data from an API, a server's list of things a program can ask for. TypeScript is "a plus".
Junior backend developer (Node.js). Builds the server side: the API the frontend calls, the database work, the logins. The post asks for JavaScript and Node.js, a server framework such as Express, one database (SQL or MongoDB), Git, and an understanding of how HTTP requests work. Writing tests is "a plus".
Junior full-stack developer. Does some of both, usually at a small company or an agency. The post lists most of the two lists above, and expects less depth in each. It is the role Maria's cousin got.
Look at the three posts again and count. JavaScript is one requirement in each, and never the only one. So the language is the entry ticket, not the whole job.
Here are three small programs that work with this lesson's numbers. Each one is under ten lines.
Four lines of output, straight from the survey.
console.log("Stack Overflow Developer Survey 2026");
console.log("1. JavaScript 62.0%");
console.log("2. SQL 58.4%");
console.log("3. HTML/CSS 58.2%");
Stack Overflow Developer Survey 2026
1. JavaScript 62.0%
2. SQL 58.4%
3. HTML/CSS 58.2%
Each console.log prints one line, in the order they are written.
The survey also publishes counts. Of the 14,099 people who answered, 8,742 ticked JavaScript. Does that really make 62.0%?
const usedJavaScript = 8742;
const answered = 14099;
const percent = (usedJavaScript / answered) * 100;
console.log(percent.toFixed(1) + "%");
62.0%
toFixed(1) rounds to one digit after the point. So the published number checks out, and you just checked a claim with code, which is a habit worth keeping.
The chart in Figure 1, printed as text. One # stands for two percent.
const bar = (percent) => "#".repeat(Math.round(percent / 2));
console.log("JavaScript " + bar(62.0) + " 62.0%");
console.log("SQL " + bar(58.4) + " 58.4%");
console.log("Python " + bar(58.0) + " 58.0%");
console.log("Java " + bar(27.6) + " 27.6%");
JavaScript ############################### 62.0%
SQL ############################# 58.4%
Python ############################# 58.0%
Java ############## 27.6%
The first line makes a small helper called bar that turns a percentage into a row of # signs. Module 5 teaches that kind of line properly. For now, notice that Java's bar is less than half of JavaScript's, exactly as in the figure.
What JavaScript alone does not get you
Here is the list no course page prints. Each item appears in most junior posts, and each one says whether this track teaches it.
| Skill the job asks for | Does this track teach it? |
|---|---|
| JavaScript itself, ES2023, from zero | Yes, Modules 0 to 17 |
| Reading an error message and fixing the cause | Yes, in every lesson's Common mistakes block |
| The browser's page: the DOM and events | Yes, Modules 14 and 15 |
| Building a finished project | Yes, three projects in Module 18 |
| HTML and CSS | No; named where needed, learn them alongside |
| A framework: React, Vue or Angular | No; the track teaches what all three are built on |
| Git, for saving and sharing code | No; learn its basics in your first month |
| A database and SQL | No |
Why no framework? React, Vue and Angular each change every year or two, and each is written in JavaScript. A developer who knows the language learns a framework in weeks. A developer who learned only a framework is stuck the day it changes. So this track teaches the part that lasts, and you add the framework your first job uses.
So the honest summary is: JavaScript is the core skill, and four other skills sit around it.
AI tools and junior roles, honestly
You have heard that AI assistants write code now. They do. An assistant can produce a first draft of a small JavaScript program in seconds.
Here is what that changes and what it does not. The draft still has to be read by someone who can tell a correct program from a confident wrong one. The error it throws at 2 a.m. still has to be understood. And most interviews still ask you to reason about code with no assistant beside you.
Nobody knows exactly how junior hiring will look in five years, and anyone who says they do is selling something. What is clear today is this: the people an assistant helps most are the ones who can already read its output. That is the skill this track builds, one lesson at a time.
Where this is used
- A frontend developer at a product company writes the JavaScript that runs in customers' browsers: forms, search boxes, dashboards.
- A backend developer on a Node.js team writes the API a mobile app and a website both call, with JavaScript on the server.
- A full-stack developer at a startup or an agency builds a whole small product, page and server, often alone or in a team of three.
- A QA automation engineer writes JavaScript tests that click through a website by themselves, with tools such as Playwright or Cypress.
Common mistakes
1. Reading "62% of developers use it" as "62% of jobs want it".
The survey counts people who answered, not job posts. The two are related, but they are not the same number. When you quote a number, quote what it measured.
2. Learning a framework before the language.
Kenji wanted to know which framework to learn before he knew what a variable was. A React tutorial assumes you can read JavaScript, so he would copy code he cannot fix. Learn the language first; the framework takes weeks after that.
3. Treating one success story as the market.
Maria's cousin's job is real. So are the people from the same bootcamp who are still looking, and nobody tells their story at dinner. Use numbers with sources, not the loudest example.
4. Skipping HTML and CSS because "the course is JavaScript".
Every frontend post in this lesson asks for them. They are smaller than JavaScript, and a few weeks of practice covers a junior's needs. Start them early, beside this track.
In Example 2, 8,184 of the 14,099 people ticked Python. Change usedJavaScript to 8184 and run it.
Check yourself. It prints 58.0%, the number in Figure 1. The variable's name is now wrong, so rename it to usedPython in both places it appears, and run it again.
Measure your own local signal. On the job board you trust most, search for "javascript", then for "react", then for "node".
Rules. Write down the board, the date, the time and the three counts. Say in one sentence why the three counts overlap.
Check yourself. A good note has all four facts and admits at least one limit from this lesson's list of warnings. A number without a date is not a measurement.
Find one real junior JavaScript post. Split every requirement into three lists: taught in this track, named here but not taught, and not mentioned in this lesson at all.
Rules. Use the table above for the first two lists. For the third list, write one sentence per item on how you would find out what it is.
Check yourself. If your third list is empty, look again: real posts usually carry one or two names this lesson never mentions. Finding out what they are is part of the job.
Common doubts
Is the JavaScript market too crowded for beginners?
Many beginners learn it, so a certificate alone does not stand out. What stands out is being able to read an error, fix it and show a finished project. This track is built around those three things.
Should I learn TypeScript instead of JavaScript?
Learn JavaScript first. TypeScript is JavaScript plus types, so every lesson here is also a TypeScript lesson. After Module 8 you can pick up the types in a short course.
Do I need a computer science degree?
It depends on the employer. Many junior posts say "or equivalent experience", and many do not. This lesson cannot promise either way, and nobody honest can.
Is Python better than JavaScript for getting a job?
They open different doors. Python leads in data and machine learning, JavaScript in anything that runs on a web page. Both sit near the top of the survey, at 58.0% and 62.0%.
Will AI tools remove junior jobs?
Nobody knows, and the honest answer is to say so. What is known is that someone has to read and fix what the tools write. Being that someone is a skill, and it is learnable.
Key takeaways
- Stack Overflow Developer Survey 2026: JavaScript is the most used language, 62.0% of 14,099 answers, first for twelve years running.
- GitHub Octoverse 2025: TypeScript, which is JavaScript with types, became the most used language on GitHub in August 2025.
- One local signal, bdjobs.com on 7 October 2026: 31 posts for "javascript", with stated limits.
- Junior frontend, backend and full-stack posts all ask for JavaScript plus four or five other skills.
- This track teaches the language, errors, the browser and projects; HTML, CSS, a framework, Git and SQL you add beside it.
Next you open the engine itself, and watch one line of code turn into something a processor can run.
End of lesson 3
Mark it done, and your progress moves with you.
Next: How the Engine Runs Your Code: Parse, Bytecode, JIT