React is the default. 409 companies on Remoet use it, more than four times the next-closest frontend framework on the platform. If you write React, you are not in a special pool. You are in the main pool, and the main pool is the problem.
That is a different problem from the one Python has. Python is too broad and you disappear inside it. React is worse, because React is what every frontend developer already knows. "React developer" tells a recruiter approximately nothing. You write components. So does everyone they have ever talked to.
Numbers first, then the part that is actually useful.
Four times the surface area of anything else
Company counts are the May 19, 2026 snapshot. The job figures were re-measured on September 16, 2026, in distinct open roles: one count per company per unique posting, the same unit the job numbers on Remoet use.
409 companies use React in their stack
9,468 open roles at those companies, more than any other frontend cohort
337 of 409 (82%) also use TypeScript. If you do not, you are competing with one hand tied
109 of 409 (27%) also use Next.js in production
67 companies specifically list React Native (mobile, different career path)
Compared to everything else, company counts from May 19, 2026 and open roles as of September 16, 2026:
| Framework | Companies | Open roles |
|---|---|---|
| React | 409 | 9,468 |
| Next.js | 113 | 4,200 |
| Vue | 85 | 2,871 |
| Angular | 81 | 3,319 |
| React Native | 67 | 2,027 |
| Remix | 7 | 775 |
| Svelte | 6 | 340 |
Roughly five times the company surface area of Vue and Angular. There is no contest, and there is also no signal in saying you write it. Every frontend candidate they screen this week writes it.
So: more React jobs than any other kind of frontend job, and you still cannot get an interview. Not because the jobs do not exist. Because "React developer" is the noisiest label in tech.
The signal is what is sitting next to React
Stop telling recruiters you are a React developer. They know. Tell them what you ship React next to.
You are a React plus TypeScript plus Next.js person. Or a React plus Rails plus Postgres person. Or a React plus Go plus Kubernetes person. Or a React Native plus Swift plus Kotlin person. Different humans, competing in pools much smaller than 409. Often 30 to 60. Inside those pools you are not interchangeable. You are a specific shape.
And because the argument is that small pools are where you become visible, it is worth walking them in that order, smallest first. Every company named here is on the platform today, with its full stack in the appendix at the bottom.
React Native, which is not really the same job
67 companies, and a career that diverges from web React early. Roughly half of them also build for native iOS and Android, so you will end up in Swift or Kotlin at some point whether you planned to or not.
MapBox, Distribusion and Reactiv are all hiring into this shape. If you are a React Native person, the worst thing you can do is let a recruiter file you with the React generalists. The mobile pool is yours and it is small. Say "React Native" before you say "React."
React plus Rails
48 companies. Smaller pool, different dynamics from JS-centric shops: Rails teams are looking for frontend people who can read Ruby and not visibly wince at it.
Stripe, Toptal, Aha! and Ably all fit here. If you have Rails on your resume and you also do frontend, you are a specific shape competing with maybe 50 people in the world. That is an absurdly good position and most people in it undersell it.
React plus Go plus Kubernetes
217 React companies use Go. 267 use Kubernetes. Where those overlap, the frontend is usually small relative to the backend, and the team quietly values someone who can read a Helm chart without escalating.
Cloudflare, 1Password and Supabase are the clean examples. For these shops "React developer" is the wrong label entirely. "Frontend engineer who reads backend code" is the right one, and it is worth rewriting your headline for.
React plus Python, the pairing nobody expects
Here is the number that surprises most React developers: 327 of the 409 React companies also use Python. Eighty percent. It is the single most common pairing on the platform, well ahead of anything the discourse talks about.
It does not mean those shops want a Python person. It means the team you join probably has Python services next door and you will read them whether you write them or not. The signal is comfort with a Python-shaped backend, not Python expertise, and that distinction is worth understanding before an interview rather than during one.
PostHog, Cursor, Anthropic, Khan Academy, Distribusion and Attio are all in this overlap. If you are a frontend dev who is happy in a polyglot stack, there are more doors here than you would guess from the job titles.
React plus Node plus Postgres
The classic JavaScript-everywhere shape, frontend and backend in one language. 218 of the 409 React companies also use Node.js, and 244 use Postgres. The overlap is the spine of mid-sized SaaS: Linear, Ably, Aha!, Ghost, Strapi.
Not a small pool, but a comfortable one. If your resume is React plus Node plus Postgres, these are the shops where you never have to justify your stack.
React plus Next.js plus TypeScript
Last, because it is the most crowded. This is the default modern web cohort: App Router, server components, edge runtimes, the toolchain that ships marketing sites and product surfaces in 2026. Vercel, Mintlify, Resend, Basement, Buffer, Whitespectre.
One thing saves you here, and it is narrow: these shops want production Next.js specifically. Knowing React without Next.js is a different conversation, and they can tell inside two questions which one you are having.
The part that breaks people
You can agree with every word above and still not get hired, because finding your cluster by hand is where the plan dies. There are 409 React companies. Reading 409 careers pages is not a job-search strategy, it is a way to give up on a Sunday afternoon.
This is the boring, unglamorous thing agents are genuinely good at. Connect one to Remoet over MCP, give it your specific stack, and ask for the 30 to 60 that match. Not "React companies." Something like "remote companies running React with Next.js and TypeScript that have Python or Go on the backend." It reads the data, returns the slice, and the 409 stops being your problem.
Star the ones that fit, and their new roles come to you in a roundup email on whatever cadence you choose. The whole flow is free.
The floor and the climb
React being the default is not the good news it sounds like. It is the floor, and every applicant is standing on it. The climbing happens in the cluster.
So pick the specific React shape you actually are, build your profile around that combination, get visible to the 30 to 60 companies whose stack is your stack, and forget the other 350. Not because they are bad companies. Because they cannot see you and you cannot see yourself in them.
If you try this and your cluster turns out to be something we have not listed here, we would like to know what it was. That is how the next version of this post gets better.
The full data
Every company referenced above with its current Remoet stack, pulled today. Useful for grepping or for handing to your agent so it can find overlap with your own stack.
React + Next.js + TypeScript
Vercel. React, Next.js, TypeScript, Node.js, Python, Go, Kubernetes, AWS, GCP.
Mintlify. React, Next.js, TypeScript, Node.js, MDX, Storybook, Vitest.
Resend. React, Next.js, TypeScript, Go, PostgreSQL, Clickhouse, Kafka, AWS, Terraform.
Basement. React, Next.js, TypeScript, GSAP, Three.js, WebGL, React Server Components, Tailwind CSS.
Buffer. React, Next.js, TypeScript, Express, BigQuery, Radix UI, Segment.
Whitespectre. React, Next.js, TypeScript, Node.js, NestJS, GraphQL, AWS.
React + Node.js + PostgreSQL
Linear. React, TypeScript, Node.js, PostgreSQL, GraphQL, Redis, Kubernetes, ProseMirror, MobX.
Ably. React, TypeScript, Node.js, JavaScript, Rails.
Aha!. React, Node.js, PostgreSQL, Rails, Kafka, Redis, Memcached, Terraform.
Ghost. React, TypeScript, Node.js, Express, MySQL, Ember.js, Handlebars.
Strapi. React, Node.js, PostgreSQL, GraphQL, MySQL, Apollo.
React + Python
PostHog. React, TypeScript, Python, Django.
Cursor. React, TypeScript, Python, Go, Rust, Kafka, Kubernetes, Clickhouse, PostgreSQL.
Anthropic. React, TypeScript, Next.js, Python, Go, Rust, Kubernetes, PyTorch, JAX, FastAPI.
Khan Academy. React, TypeScript, Python, Go, Vue.
Distribusion. React, Python, FastAPI, PostgreSQL, Kafka, Kubernetes, Elixir, GCP, AWS.
Attio. React, TypeScript, Node.js, Python, Go.
React + Go + Kubernetes
Cloudflare. React, TypeScript, Go, Rust, Python, Lua, JavaScript, Cloudflare Workers.
1Password. React, TypeScript, Go, Rust, Java, Kotlin, Next.js, Node.js, Kubernetes, AWS, GCP.
Supabase. React, TypeScript, Next.js, Go, Elixir, Phoenix, PostgreSQL, Kotlin, Rust, WebAssembly.
React Native
MapBox. React, React Native, TypeScript, Swift, Kotlin, C++, Rust, Go, Java, Vulkan, WebGL.
Distribusion. React, React Native, Python, FastAPI, Kubernetes, Elixir.
Reactiv. React, React Native, Next.js, Node.js, AWS, GraphQL, iOS, Swift, Xcode.
React + Rails
Stripe. React, TypeScript, Ruby, Rails, Python, Java, Go, Scala, Kafka, GraphQL.
Toptal. React, TypeScript, Ruby, Rails, Node.js, Python, Next.js, Tailwind CSS.
Aha!. React, Node.js, PostgreSQL, Rails, Kafka, AWS, ECS, Terraform.
Ably. React, TypeScript, Node.js, Rails.
