Companies

JavaScript / TypeScript board

Full-stack JavaScript and TypeScript jobs

One language on both sides is the oldest argument for a JavaScript stack, and it is still the reason most of these teams are organised this way. The filter is plain: these are the listings on this board that are not marked backend-only, so the role reaches the interface as well as the server.

Open roles
225
Companies hiring
197
Countries
24
Fully remote
65
Pay published by the employer
65 of 225

See all 225 on the JavaScript / TypeScript board →

Shared types are the actual benefit

The real payoff of one language end to end is not reusing code, which happens less than people expect. It is that the contract between server and client can be one definition instead of two that drift. Teams that have set this up well will want to talk about how — generated from a schema, inferred from a validator, published as a package — and teams that have not will want somebody who can do it.

Ask where the boundary is

Full-stack covers a wide spread here: a framework that renders on the server and hydrates, a separate API with its own deployment, or a set of small services with an interface stitched over them. Each implies a different day. It is a reasonable first-call question, and the answer usually also tells you how much of the job is operational.