Teach Node.js online in English

Node.js takes JavaScript out of the browser and runs it on the server. The language stays the same, but nearly everything around it changes: there is a file system, a network, environment variables, a process that has to keep running, and a single thread that serves every request. That last part is where most learners get stuck. Node.js does not wait for a database query or a file read to finish. It hands the work off, carries on, and comes back when the result is ready. Code that looks as if it runs from top to bottom often doesn't, and one loop that spends two seconds crunching numbers can freeze a whole server.

People usually come to a Node.js tutor in the middle of something: a React app that needs a back end, a university project with an API and a database, a team at work that has moved to Node while they still think in PHP or Java. They can follow a tutorial. What they need is someone who knows what the runtime is doing when their own route hangs without an error.

Why we are looking for Node.js tutors who teach in English

Clasora shows students the tutors who teach in the language they use the site in. A student reading Clasora in English sees tutors who teach in English, so if English is the language you teach in, those are the students who find you.

The Node.js documentation and its error messages are in English, but reading them is not the same as understanding them. A student who sees “Cannot set headers after they are sent to the client” needs someone to say, in plain words, that the response already went out two lines earlier and the second res.json() has nowhere to go. The event loop and non-blocking I/O are far easier to grasp through a well-chosen comparison than through the reference pages.

Clasora does not employ tutors, and this page is an opening, not a job advert. You teach independently: you set your own prices and hours and decide how much you teach. Some tutors fit a few evening sessions around their development work as a side income. Others teach enough for it to take the place of a job.

What teaching Node.js online on Clasora looks like

The opening is fully remote. Every lesson takes place online, and you teach from wherever you live.

Students book from your calendar and see only the hours you have left free, shown in their own time zone. You decide how much notice you need before a lesson and how far ahead people can book.

The video call runs in the browser, so neither of you installs anything to join it. In a Node.js lesson the shared screen does most of the work. It usually shows an editor such as VS Code, a terminal with the server running, and something to send requests with, whether that is curl, Postman or a browser tab. You add a route, restart the server, send a request and read the response together. Just as often the student shares, and you see the real stack trace in their terminal instead of their memory of it. Step through a request handler in the debugger and the student watches a function return before the promise it started has settled. The in-call chat is handy for passing across a command or a snippet, and background blur keeps your room out of the picture.

Between lessons, each student has a conversation with you. They can send last night's error log or a link to their repository, and you can reply with a hint, an exercise or a corrected file. Messages, files and shared links sit next to the sessions they belong to, so the authentication middleware you wrote together a month ago is easy to find. Starter projects can live in your personal file area, and documents can come across from Google Drive. If you plan your week in Google Calendar, it can sync with your Clasora calendar.

What students usually want help with

How Node.js runs code: the event loop, non-blocking I/O, and why a synchronous call in a request handler slows down every user.

Asynchronous code: error-first callbacks, promises, async/await, Promise.all, and the unhandled rejection that brings the process down.

Modules and npm: require against import, package.json and its scripts, dependencies and devDependencies, version ranges and the lock file.

The built-in modules: fs and path, EventEmitter, streams, Buffer and process.env.

Building an API with Express: routes, middleware and the order it runs in, error handling, status codes, and validating what the client sends.

Other frameworks: Fastify or NestJS, and how they differ from Express.

Databases: PostgreSQL, MySQL or MongoDB, parameterised queries against SQL injection, connection pools, migrations, and ORMs such as Prisma.

Authentication and security: hashing passwords, sessions and cookies, JSON Web Tokens, CORS, and keeping secrets out of the code.

Testing: the built-in node:test runner, Jest or Vitest, and testing endpoints with Supertest.

Deployment basics: environment variables, logging, PM2 or a Docker container, and a reverse proxy in front.

Coursework and interviews: finishing a back-end project on time, or explaining the event loop clearly in a technical interview.

Who we are looking for

You build server-side applications with Node.js and understand what happens beneath the framework: the event loop, promises, streams and the module system.

You explain those ideas clearly in English, and when one explanation does not land, you try a smaller example.

You read other people's code patiently, nested callbacks included, and you hold back when a student is one step away from finding the bug.

You might work as a back-end or full-stack developer, teach programming already, study computer science, or have learnt Node.js by building your own projects.

You have a computer with a camera, a microphone and a steady internet connection.

You are 18 or older.

Teaching experience helps, but it is not required.

What you get

No commission. Clasora takes nothing from the price you set.

Free to join and to publish. There is no subscription and no listing fee.

Your own prices. You set a price for each session length, and you can offer a free first session.

Your own hours. You choose your weekly hours and days off, the notice you need and how far ahead students can book.

A public listing page. Your listing is a page of its own that search engines can find, shown in the language each visitor reads, with your photo, an intro video, what you teach, the languages you speak and your price for each session length.

Reviews that mean something. Students rate you on knowledge, clarity and engagement.

Checked qualifications. You can add your degree or other qualifications to your profile, and a moderator checks them.

Lessons in the browser. Video with screen sharing, background blur and in-call chat, with nothing to install.

How to start

Create an account with the button on this page.

Publish a listing for Node.js.

Open your calendar and mark the hours you are free.

It takes a few minutes. You accept the terms when you become a tutor, and a moderator checks your listing before it goes live.

Questions tutors ask

Do I need a computer science degree?

No. You need a solid command of the Node.js topics you offer and the ability to explain them, whether you learnt them at work or on your own projects. If you have a degree or other qualifications, add them to your profile and a moderator will check them.

Can I teach someone who only knows front-end JavaScript?

Yes, that is a common way into Node.js. The syntax is familiar, so lessons can go straight to what is new on the server: the terminal, npm, requests and responses, and code that waits for a database. Your listing can also say that you take complete beginners.

Does the student need to install anything?

Not for the call, which runs in the browser. To write and run code they need Node.js and an editor on their own computer, and setting those up together is a good start to a first lesson.

How do I get paid?

Card payments are not switched on yet. For now a booking is confirmed without a card, and you and the student settle payment directly. Clasora takes no commission on what you charge.