Remote JavaScript and TypeScript jobs

JavaScript is the stack where remote hiring is least remarkable. The tooling assumes a laptop, the deploy target is a CDN, and there is almost never a physical thing to stand next to. The consequence is competition: these roles draw applicants from everywhere, which is exactly why the eligibility line on each listing matters more than the headline word remote.

Open roles: 183
Companies hiring: 151
Countries: 22
Pay published by the employer: 61 of 183

See all 183 on the JavaScript / TypeScript board →

TypeScript is the floor, not the differentiator

Naming TypeScript on a CV stopped being a signal some years ago; what employers screen for now is what you do with it at the edges. How strict is the configuration you are used to. Where do the types come from — hand-written, generated from a schema, inferred from a validator. What happens at the boundary where data arrives untyped. Those answers separate candidates far more reliably than the list of frameworks underneath.

The listings are not interchangeable

This board holds at least four different jobs under one language: owning a Node service and its data access, owning a product surface in a framework, owning a shared component library other teams build on, and owning the build and release tooling. The tags on each listing are the fastest way to tell them apart, and the description usually settles it within two paragraphs. Filter down before applying widely.