427 Remote Companies Using TypeScript in 2026

Every frontend developer puts TypeScript on their resume now. So does every fullstack. So does every backend engineer on a JS team. So do most React Native people, most Next.js people, and a large number of devs who barely write any TS but pattern-matched to "it's expected."

The signal got nuked. "TypeScript developer" tells a hiring manager about as much as "uses a keyboard."

Here is the data, and the one line in it that should actually change how you job hunt.

Everyone has it, so it says nothing

Company counts are the May 28, 2026 snapshot. The job figure was 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.

• 427 companies on Remoet ship TypeScript in production

• 11,008 open roles across those companies, second only to Python among language signals on the platform

• 346 of 427 (81%) pair it with React

• 346 of 427 (81%) pair it with Python. Identical count to React

• 297 of 427 (70%) run it next to Kubernetes

• 255 of 427 (60%) run it on top of PostgreSQL

• 236 of 427 (55%) ship it next to Go

Read those two 81% lines again, because that is the whole post.

The headline most TS devs assume is that TypeScript means JavaScript everywhere. The data does not agree. Python sits next to TypeScript exactly as often as React does, and there are now more open roles carrying a Python signal than a TypeScript one. Half of TypeScript shops on Remoet are running TS as a frontend (or thin backend) layer on top of a stack written in something else entirely. Python. Go. Rust. Even Ruby.

Which means treating "I write TypeScript" as your job-search identity collapses 427 companies into one bucket. Vercel and Anthropic both run TS. Linear and Cloudflare both run TS. Walk into the engineering org at any pair of them and you are inside two different jobs. The companies know that. Your resume should reflect it.

Start with the cluster that surprised us

Most TS devs read that 81% Python number twice. The mental model does not include "Python." The mental model is wrong, so this is where the cluster tour starts rather than where it usually gets buried.

346 companies sit in the TS-plus-Python overlap, and they hire a meaningfully different developer than the JS-everywhere shops do. They are not hiring you to write Python. They are hiring you because their TS frontend talks to an API that came out of a FastAPI service maintained by the ML team. You will sit next to those services in pull request review. You will read enough Python to understand what changed and why. The fluent-in-TS, comfortable-reading-Python developer outperforms the TS-only one at every shop on this list.

• Anthropic. TypeScript, Python, Next.js, Go, Rust, Kubernetes, PyTorch, JAX.

• OpenAI. TypeScript, Python, Next.js, Go, Rust, Kubernetes.

• Cursor. TypeScript, Python, Go, Rust, Ray, Kafka, Kubernetes, Clickhouse.

• PostHog. TypeScript, Python, Django, React, Clickhouse.

• MapBox. TypeScript, Python, C++, Go, Rust, Kotlin, Swift.

• Khan Academy. TypeScript, Python, Go, JavaScript, Vue.

• Attio. TypeScript, Python, Node.js, Go, React.

• Scale AI. TypeScript, Python, Go, Rust, Next.js, PostgreSQL, Ray.

AI labs in particular live here. If you have ever wanted to ship product UX next to people training models, the door is wider open than the discourse around it suggests.

Your real pool is 30 to 60, not 427

Your addressable market is much smaller than 427. For most TS developers it lands somewhere between 30 and 60 companies. Inside that subset you are a specific candidate with specific tradeoffs. Outside it you are a resume submitted to a black hole.

Five more shapes worth placing yourself in.

TS plus Go plus Kubernetes

236 TS companies use Go. 297 use Kubernetes. Many of these places think of frontend as a one-team island inside a much larger platform org. The hire that wins is the engineer who can ship a polished dashboard and then work out why their request is hitting the wrong upstream service in Istio. If kubectl does not scare you, this cluster is wide open.

• Cloudflare. TypeScript, React, Go, Rust, C++, Cloudflare Workers.

• 1Password. TypeScript, React, Go, Rust, Kotlin, Kubernetes.

• Supabase. TypeScript, Go, Elixir, Rust, PostgreSQL, Kubernetes.

• Cursor. TypeScript, Go, Python, Rust, Kubernetes, Ray.

• Grafana Labs. TypeScript, Go, React, Kubernetes, Prometheus, Grafana.

• Vercel. TypeScript, Go, React, Next.js, Kubernetes, AWS.

• Chainlink Labs. TypeScript, Go, Rust, Kubernetes, Solidity, PostgreSQL.

When these shops post a frontend role, the JD lists three React libraries and twelve infrastructure terms. That is not sloppy writing. That is the signal, and you should match it.

TS plus Rust

95 companies. Tight pool. Rust on the backend or in hot paths, TS on the UI side. This is where TS engineers go when they have outgrown gluing libraries together and want to debug something in a profiler.

• Anthropic. TypeScript, Rust, Python, Go, Kubernetes, JAX, PyTorch.

• Cloudflare. TypeScript, Rust, Go, C++, Cloudflare Workers.

• Supabase. TypeScript, Rust, Elixir, Go, PostgreSQL.

• 1Password. TypeScript, Rust, Go, Kotlin, Swift.

• MapBox. TypeScript, Rust, C++, Go, Swift, Kotlin.

• Cursor. TypeScript, Rust, Go, Python, Kubernetes.

Rust next to TS is rare enough that recruiters at these shops will read the rest of your application, which is a privilege most candidates do not have. Spend it well. Tell them which Rust project you shipped and what blew up the first time.

TS plus Node plus Postgres

The workhorse. TS on top, Node.js underneath, Postgres holding state, GraphQL or tRPC in between. 221 of the 427 pair with Node.js, 255 with Postgres. Nothing exotic, nothing to learn before standup, and the interviewer has the same Drizzle tab open as you.

• Linear. TypeScript, Node.js, PostgreSQL, React, GraphQL, Redis.

• Supabase. TypeScript, Node.js, NestJS, PostgreSQL, Deno, Elixir, Go.

• Deel. TypeScript, Node.js, NestJS, PostgreSQL, React, MySQL, Express.

• HE:labs. TypeScript, Node.js, NestJS, PostgreSQL, Prisma, Typeorm.

• Stripe. TypeScript, Node.js, Ruby, Rails, Java, Go, Scala, Kafka.

If you can write this combination in your sleep, these are the shops where your first PR ships in week one.

TS plus React plus Next.js

Where most public-facing TS work lives: App Router, server components, edge runtimes, the toolchain shipping marketing sites and product surfaces in 2026. It is also the most crowded cohort in this post, so the bar is less about knowing it and more about having opinions that survive code review.

• Vercel. TypeScript, React, Next.js, Node.js, Go, Python, Kubernetes, AWS.

• Resend. TypeScript, React, Next.js, Go, PostgreSQL, Clickhouse, Kafka, AWS.

• Linear. TypeScript, React, Node.js, PostgreSQL, GraphQL, Electron, Prosemirror.

• PostHog. TypeScript, React, Next.js, Python, Django, Clickhouse, Kubernetes.

• 1Password. TypeScript, React, Next.js, Node.js, Go, Rust, Kotlin, Swift.

• Toptal. TypeScript, React, Next.js, Node.js, Rails, PostgreSQL.

• Bloomreach. TypeScript, React, Java, Spring Boot, Kafka, Pulsar.

If your last six months have been App Router work, and you have caching opinions that go past "use SWR," you are home here.

TS plus Vue, or TS plus Angular

74 companies pair TS with Vue. 63 with Angular. Smaller pools, often older codebases or enterprise environments, and the upside is straightforward: a senior Vue dev competes with maybe 200 people in the world, a senior Angular TS dev with fewer.

Vue side:

• Supabase. TypeScript, Vue, Node.js, PostgreSQL.

• NearForm. TypeScript, Vue, Node.js, PostgreSQL, Python.

• GitLab. TypeScript, Vue, Ruby, Rails, Go, PostgreSQL.

• Wolt. TypeScript, Vue, Kotlin, Python, Go.

• Khan Academy. TypeScript, Vue, Python, Go, React.

Angular side:

• NearForm. TypeScript, Angular, Node.js, Python.

• Bloomreach. TypeScript, Angular, Java, Spring Boot, Kafka.

• Zscaler. TypeScript, Angular, Java, Go, Kubernetes.

• Databricks. TypeScript, Angular, Scala, Python, Spark.

• Scale AI. TypeScript, Angular, Python, Go, Rust.

The instinct is to hide the unfashionable framework. Do the opposite. The TS-plus-React cohort has 346 companies and hundreds of thousands of candidates chasing it. These two have far less competition per role, and the hiring managers in them know exactly how thin the market is.

The morning-after problem

Every developer who reads a post like this hits the same wall the next day. You agree the cluster framework is right. You sit down with a coffee and try to find the 30 companies in your slice. By company number eight your eyes glaze over. By fifteen you give up and tweak your resume instead, which feels productive and is not.

An agent does not get bored on company eight. Plug Claude, Cursor, or whatever you already pay for into Remoet, describe the exact shape of your stack, and ask for the slice. The queries that work look like:

"Remote companies running TypeScript with React and Next.js that also use Python or Go on the backend, hiring senior engineers."

"Companies that pair TypeScript with Rust in production."

"TS plus Vue shops smaller than 500 people."

It reads the company-level tech stack data, returns the matches, and the careers-page death march does not happen.

Star the ones that hit. New roles from those companies arrive in a roundup email on whatever cadence you set, daily through to monthly. Remoet is free.

The part after the comma

Universal adoption is precisely what nuked TS as a signal. Every applicant has it, which is exactly why nobody is moved when you list it.

So the interesting part of your stack is the part that comes after the comma. Python. Go. Rust. Vue. Whatever your second language is, that is the one your resume is actually about, and it belongs on your top line rather than buried under "Senior Frontend Engineer." "TypeScript plus Go plus Kubernetes" carries information. "TypeScript developer" carries none.

If you run your own stack through this and land somewhere we have not named, tell us what the pairing was. The cluster list here is only as good as the shapes people report back.