React jobs in the United States
React in the US is increasingly hired under the label product engineer, and the change is not cosmetic. The expectation attached to that title is that you will argue about what the feature should be, not only build the version handed to you — which suits some people enormously and makes others miserable in month three.
- Open roles
- 228
- Companies hiring
- 185
- Fully remote
- 88
- Pay published by the employer
- 113 of 228
- Senior Java Developer
- Senior Full Stack Java Developer
- Senior Java Developer
- Senior Java Engineer
- Design Engineering Intern
- Senior Software Engineer, Product
- Senior Software Engineer - Saga / Voice OS
- Senior Full-Stack Engineer, Internal Tools
- Software Engineer, Agents
- Engineering Manager
- Product Engineer
- Software Engineer, CDN
- Senior Full-Stack Engineer (Web)
- Software Engineer, Deployment Infrastructure
- Staff Product Engineer (Brand)
- Full Stack Engineer (Vue + Nest)Remote — RemoteBrasília, Federal District, Brazil / São Paulo / Rio de Janeiro / Mexico City / Buenos Aires Province / Bogota,D.C., Capital District / Recife, Pernambuco, Brazil
- Full stack Engineer
- Lead Software Engineer
- Senior Fullstack Engineer
- Senior Frontend Engineer
- Forward Deployed Engineer
- Site Engineer
- Frontend Developer (Marketing)
- Principal React Engineer, New York
- DAC AI engineer
Product engineer is a real change in the job
It usually means fewer specifications, more direct contact with users or with the data about them, and being held to the outcome rather than the ticket. The upside is autonomy and a shorter path from idea to shipped. The cost is ambiguity, and a fair amount of work that is not writing components. Listings that mean it tend to say so in the first paragraph; listings that use the title as decoration read like a normal frontend brief.
What gets tested
The take-home is smaller than it was and the live pairing session is back — usually extending an unfamiliar component rather than starting from nothing, which is a much better proxy for the job. Expect at least one conversation about performance that is really about measurement: what you looked at, in which tool, before you changed anything.