Full-stack React jobs
A growing share of React roles now reach past the browser, because the frameworks made it easy and product teams noticed how much time was lost handing requirements to somebody else. These are the React listings on this board that are not marked backend-only, which in practice means the interface and the data behind it belong to the same person.
- Open roles
- 176
- Companies hiring
- 157
- Countries
- 25
- Fully remote
- 61
- Pay published by the employer
- 49 of 176
- Member of Technical Staff, Full-Stack (Senior)
- Fullstack Java Developer
- Senior Full Stack Java Developer
- Front End Engineer- Web Experience
- Sr. Software Engineer, Fullstack (UK)
- Senior Full-Stack Engineer, Internal Tools
- Frontend Developer (React)
- Senior Full-Stack Engineer (Web)
- Senior Software Engineer (Full Stack)
- Frontend Engineer - Growth team
- Senior Full Stack Engineer
- Senior Fullstack Engineer, GTM
- Full-Stack Developer
- Senior FrontEnd Engineer
- Frontend Engineer
- Senior Full Stack Engineer
- Senior Frontend Developer
- Frontend React Native Engineer
- Nearshore Sector | Mid Fullstack Java/React Developer
- Senior FullStack Engineer (Frontend-focused), Retail Media/AdTech Solutions (m/f/d)
- (Senior) Full-Stack Engineer (TypeScript + Kotlin/Java) (m/f/x)
- Full Stack Developer (React.js / Next.js / Nest.js)
- [KHOME] - Senior Software Engineer Full Stack
- Software Engineer (Frontend-Focused Full Stack)
- Fullstack Developer (Ruby on Rails & React)
Owning the data changes the interview
Once the same engineer writes the query and the component, questions about caching, invalidation and what happens on a slow network stop being frontend trivia and become the job. Expect to be asked what you do when data arrives late, arrives twice, or fails halfway through a mutation — and to be judged on whether the interface tells the user the truth about it.
Read how far the server side goes
The spread is wide. Some of these roles stop at a rendering framework's own server layer; others include the database schema, the background jobs and the deploy. The tags on each listing are the quickest signal, and the description usually settles it in a paragraph. Filtering the board by the specific stacks named in a posting is faster than reading them all.