Companies

Java board

Full-stack Java jobs

Full-stack in a Java posting usually means the server is Java and the browser is something else, most often a TypeScript framework the team adopted later. Knowing that changes how to read these listings: the question is not whether you write Java, it is how much of the front end the team expects one person to own.

Open roles
30
Companies hiring
19
Countries
8
Fully remote
2
Pay published by the employer
3 of 30

See all 30 on the Java board →

The two shapes this takes

In the first, an older application still renders templates on the server and the front-end work is incremental, adding behaviour to pages that already exist. In the second, a Java service feeds a separate single-page application and the boundary between them is an API somebody has to design. The skills barely overlap, so the tags on each listing are worth reading before the salary.

Why these roles are often the interesting ones

Owning both sides means the person who designs the endpoint is the person who has to consume it, which tends to produce better APIs and fewer meetings. It also means being accountable when data arrives late or twice, and having to decide what the interface tells the user in that moment rather than leaving it to somebody downstream.