Companies

React board

Remote React jobs

Remote React openings split fairly cleanly in two, and the split matters more than the framework version. One kind wants somebody to own screens end to end, close to the product decisions. The other wants somebody to own the components everyone else builds screens from. Both say React in the title and the day-to-day work has almost nothing in common.

Open roles
163
Companies hiring
137
Countries
23
Pay published by the employer
62 of 163

See all 163 on the React board →

Product React and platform React

A product role is judged on shipped surface: you take an ambiguous brief, decide what the screen should do, and get it in front of users. A platform role is judged on what other engineers can do afterwards — the component API, the accessibility defaults, the migration you wrote so forty screens could move at once. Read the listing for who consumes your work. That single question predicts the interview better than the stack list does.

What the interviews actually test

Rendering behaviour rather than trivia: when a component re-renders and whether that matters, where a piece of state should live, what happens to it on navigation. Accessibility comes up more than it used to, and usually as a practical question about a real widget rather than a rules quiz. Take-homes tend to be small and open-ended, and the thing being read is your judgement about scope.