Senior React jobs
A senior React role is usually one where you will decide something other engineers then have to live with: a component API, a state boundary, a rendering strategy, a migration path off the last person's decision. The code is the easy part of that; the hard part is that it has to survive contact with a team.
- Open roles
- 325
- Companies hiring
- 256
- Countries
- 30
- Fully remote
- 94
- Pay published by the employer
- 97 of 325
- Senior Java Developer
- Principal Java Developer - Distributed Systems, Serverless - Elasticsearch
- [Job - 31575] Senior /Master Data Developer, BrazilRemote — HomeofficeBrazil
- Senior Java Engineer
- Senior Java Engineer - Core/Infra - Elasticsearch
- Senior Software Engineer, Java
- Java Developer (medior - senior) | FinTech | Spring
- Java Developer II - AutoOps Services - Platform Applications
- Java Software Engineer - Payments
- Expert Java Developer TEST
- Senior Java Developer - Core/Infra - Elasticsearch
- Java Developer
- Java Software Engineer / Kubernetes (TS/SCI Clearance Required)
- Member of Technical Staff, Full-Stack (Senior)
- Java Software Engineer
- Java Software Engineer (Power/Gas)
- Senior Java Developer
- Lead Backend Java Developer
- Senior Java Software Engineer 759
- Fullstack Java Developer
- Senior Java Developer
- Senior Java Developer
- Senior Full Stack Java Developer
- Senior Java Developer
- Senior Java Engineer
You will be asked what you deprecated
Adding a component is junior work. Removing one that forty screens depend on, without freezing the roadmap for a quarter, is the thing being hired for. Interviewers at this level ask about the migration you ran, how you kept both versions alive, how you convinced people, and what you left behind unfinished. Honest answers about the unfinished part land better than tidy ones.
Performance means measurement
Expect at least one conversation that starts with a slow page. The weak version of the answer is a list of optimisations. The strong version starts with what was measured, in which tool, on whose device, and why the first suspect turned out to be wrong. Accessibility gets the same treatment at senior level — a specific widget, a specific fix, not a policy statement.