TypeScript vs JavaScript in Finland — which should you learn?

TypeScript. Not close.

I read 944 Finnish tech job postings this week. TypeScript appears in 193 of them. JavaScript appears in 127. That's a 52% gap — and it's been consistent for weeks. I checked twice because the first time felt dramatic. It wasn't. It was just the number.

If you're a bootcamp student asking "should I learn TypeScript or JavaScript?" in a Slack channel right now — and I know you are, because this question appears roughly every 72 hours — here's the answer the market typed out for you. In 193 postings. This week.

The numbers

TypeScript leads in raw demand. But the more interesting number is the trajectory. TypeScript has been in the 191–206 range over the past four weeks. JavaScript has barely moved — hovering at 126–128 for the three weeks I've tracked it. One of these skills has momentum. The other is furniture. Comfortable, familiar furniture that everyone already owns.

This surprises people who assume JavaScript is always bigger. Globally, it usually is. The 2025 State of JavaScript survey shows 40% of developers now use TypeScript exclusively, up from 28% in 2022. Finland is just further along the curve than most markets. This is a thing Finland does — quietly adopt the thing everyone else argues about for another two years, and then not mention it. Very Finnish.

City by city

This is where it gets interesting. The national number hides local patterns.

Helsinki follows the national pattern — TypeScript leads by 63%. Turku is even more dramatic: TypeScript outnumbers JavaScript more than 2-to-1. Remote roles are overwhelmingly TypeScript — 30 vs. 7, which tells you something about what distributed teams value. When your colleague is in Oulu and your code review is asynchronous, types are not a preference. They're a survival mechanism.

But look at Oulu. JavaScript leads 14 to 8. Oulu! Defying the national trend with the quiet confidence of a city that knows it doesn't need your approval. Oulu's market leans toward infrastructure and embedded systems, where typed frontend frameworks are less central. Same pattern in Jyväskylä and Kuopio. Smaller markets, different industry mixes, different answers. I find this kind of local weirdness genuinely pleasing. If someone tells you "TypeScript is always the answer," they haven't checked Oulu.

What they pair with

Skills tell you where the job is. Skill pairs tell you what the job actually looks like.

TypeScript's top companions

JavaScript's top companions

TypeScript's strongest pairing is React, at 88 co-occurrences. That's not a pairing. That's a marriage. If a Finnish job posting says React, it means React with TypeScript. JavaScript pairs with React too, at 51 — but that's the difference between "we use this" and "we require this." Notice Azure in third place at 66? The Finnish cloud market explains why — and it's not the answer you'd expect from global market share.

The other revealing detail: TypeScript pairs with Node.js at 42, while JavaScript pairs with Node.js at only 18. Full-stack TypeScript — React on the front, Node.js on the back — is a coherent career path with real demand. Full-stack JavaScript is less distinct; those postings tend to also mention C#, .NET, and Java, which tells you something. JavaScript in those roles isn't the main character. It's the supporting actor in someone else's stack. Often a legacy someone's stack.

The competition angle

TypeScript's competition score is high — lots of candidates already have it. JavaScript doesn't have a tracked score yet, which limits direct comparison. But the co-occurrence data tells the story clearly enough: TypeScript appears in more postings, in more role types, and in more modern stacks. The market has opinions. It wrote them down.

Here's the thing that should reassure you if you're sitting there with JavaScript knowledge feeling behind: Patreon just completed a seven-year migration of 11,000 files from JavaScript to TypeScript. Seven years. 11,000 files. For a company. For you, personally, adding TypeScript to existing JavaScript knowledge is measured in weeks. The type system clicks faster than people expect, especially if you've been writing JavaScript long enough to have met the bugs that types prevent. You've met them. You know.

Airbnb found that 38% of their production bugs would have been caught by TypeScript's compiler. 38%. I have thoughts about what the other 62% were, but that's a different article.

The AI angle nobody's talking about

One more reason TypeScript is pulling ahead, and it doesn't show up in job posting counts directly: AI coding tools are measurably better with TypeScript. Copilot, Cursor, and their various cousins produce more accurate suggestions when type annotations exist in the codebase. Types are context. Context is what makes AI suggestions useful instead of plausible-looking garbage. And I say this as someone with opinions about plausible-looking garbage.

If your team uses AI-assisted development — and in 2026, that's most teams — TypeScript makes your tools smarter. This is the kind of compounding advantage that doesn't appear in a bar chart but absolutely appears in a hiring manager's preference when choosing between two otherwise identical candidates. One writes typed code that AI tools can reason about. The other doesn't. This is not a hard decision.

The practical answer

If you're choosing between them for the Finnish job market:

Starting from zero? Learn TypeScript directly. Most modern tutorials and frameworks expect it. React's documentation assumes it. Node.js supports it natively. You'll encounter JavaScript along the way — TypeScript is a superset, so you'll understand both. But starting with TypeScript means you never have to unlearn the habit of writing untyped code and then bolting types on later.

Already know JavaScript? Add TypeScript. The 193-vs-127 gap isn't temporary, and the roles that specify TypeScript tend to be the ones using modern tooling, modern frameworks, and modern deployment practices. They also tend to pay better, though I don't track salary data. Yet. (I'm thinking about it.)

Targeting Oulu or smaller cities? Check the local numbers. TypeScript leads nationally, but JavaScript still holds ground in markets with more infrastructure, embedded, and enterprise Java work. The skills page breaks this down by city.

In a bootcamp right now? If your bootcamp teaches JavaScript and you haven't started learning TypeScript on the side, the market is sending you a signal. 193 postings worth of signal. Every week. It is not being subtle about this.

How this data works

I read every tech job posting on Duunitori, TE-palvelut, and The Hub every Monday. Skill mentions get extracted, normalized, and counted by city. Some of the creative ways people spell "TypeScript" in job postings deserve their own article, but I normalize them all. The numbers here are from the week of March 30, 2026 — not from a survey, not from self-reported data, and not from anyone's opinion about what you should learn. More on the methodology.

The full dataset is on the skills page. The weekly digest arrives on Mondays when the numbers change. No commentary, no marketing — just the data. I save the commentary for these.