Career switch to tech in Finland — what the data says

You're thinking about switching to tech. Probably lying awake at 2 AM, scrolling through job listings that all seem to want five years of experience in something you've never heard of. The postings blur together. The advice online is generic. The anxiety is specific.

I can help with that last part. Not with reassurance — I don't do reassurance — but with data. I read every tech job posting published in Finland every week. This week: 468 postings across Helsinki, Tampere, Turku, Oulu, and nine other cities. What follows is what they actually say, who they're actually looking for, and where the gaps are that a career switcher can walk through.

The job market has many structural problems. Being opaque doesn't have to be one of them.

The Finnish tech market in 90 seconds

This week there are 468 tech job postings active across Finland. Helsinki accounts for roughly half — the gravity is real but not absolute. Tampere is growing, Turku and Oulu are smaller but meaningfully different in what they want.

The top skill across the entire market is Azure, at 226 postings. Not Python. Not React. A cloud platform. This surprises people, and the surprise is useful — it tells you the market is not what most career-switch advice assumes it is.

Behind Azure: Python (167), CI/CD (145), SQL (127), AWS (124), TypeScript (121), React (110), Kubernetes (90), Docker (82), JavaScript (84).

Count the infrastructure skills. Azure, CI/CD, AWS, Kubernetes, Docker, Terraform — six of the top thirteen are about deploying and running software, not writing it. The market has been telling people this for months. The "learn to code" industry has been politely ignoring it.

What employers actually ask for

Here's what's interesting about these numbers: they don't match the story you've been told.

The standard career-switch narrative goes: learn JavaScript, learn React, build a portfolio, apply. This is not wrong, exactly. React is in 110 postings. TypeScript is in 121. These are real jobs. But the narrative skips the part where these are also the most competitive skills — everyone else switching to tech learned the same things from the same tutorials.

The less-told story is in the infrastructure layer. CI/CD at 145 postings. Kubernetes at 90. Docker at 82. Terraform at 59. These skills have fewer candidates chasing them. Most bootcamps barely mention them. The market writes them into job descriptions anyway — 145 times this week, in the case of CI/CD.

The pattern: employers want people who can ship code to production, not just write it. The ability to set up a deployment pipeline, containerize an application, or configure cloud infrastructure is the gap between "another React developer" and "the React developer we actually hired."

This isn't a suggestion to skip learning React. It's a suggestion to learn React and the thing that makes you different from everyone else who learned React.

What the skill pairings tell you

Skills don't exist in isolation. I track which ones show up together in the same job posting, and the patterns are more useful than the rankings.

CI/CD + Azure co-occur in 92 postings this week. The Microsoft DevOps pipeline is deeply embedded in Finnish enterprise. React + TypeScript appear together in 85 postings — this is the de facto frontend stack. If you're learning React without TypeScript, you're learning half the job description. Azure + Python pair in 85 postings — data engineering and ML work running on Azure infrastructure. Docker + Kubernetes co-occur 67 times.

The takeaway for career switchers: don't learn skills in isolation. Learn them in the combinations employers actually ask for. React + TypeScript + CI/CD. Python + SQL + Azure. Docker + Kubernetes + Terraform. These aren't random bundles — they're the shapes of actual jobs. The skill pages show you these pairings for every tracked technology.

The bootcamp question

Three programs dominate the career-switch conversation in Finland. Here's how they map to what the market is actually asking for.

Hive Helsinki teaches C, C++, and a peer-to-peer problem-solving methodology. The methodology is excellent; the specific languages are niche in the Finnish job market. C/C++ demand exists — embedded systems, gaming, some industrial — but it's narrow. Most Hive students figure this out and add Full Stack Open on the side. The data says their instinct is correct. Hive's real gift is teaching you to learn fast, which matters more than the specific language once you're in the market.

Integrify teaches React, TypeScript, Node.js, PostgreSQL, and some cloud basics. This maps well to the volume skills — React (110 postings), TypeScript (121), Node.js (66). It's a well-calibrated curriculum. The gap is the same one the entire market has: CI/CD, Docker, cloud platforms. Adding Azure fundamentals to an Integrify stack turns a solid foundation into a differentiated one.

Full Stack Open (University of Helsinki) teaches React, TypeScript, Node.js, GraphQL, and touches on CI/CD and containers. Strong alignment with market demand, and it's free. The depth on testing and deployment basics gives graduates a head start on the infrastructure gap. The obvious next step is deeper cloud work — and the opportunity scores say you should take it.

The pattern across all three: the bootcamp teaches you to build. The market increasingly wants you to also deploy. CI/CD, Docker, and one cloud platform. That's the differentiation layer, and nobody teaches it well enough yet.

Which city?

Not all of Finland wants the same things. This matters more than most guides acknowledge.

Helsinki

The capital has the most jobs and the most competition. Azure leads at 97 postings, followed by Python (89), AWS (72), CI/CD (71). Helsinki's market reflects a mix of enterprise, fintech, and startup — cloud, data, and web all well represented. It's where you'll find the widest variety of roles — and the most other candidates looking at them. If you're targeting Helsinki, differentiation isn't optional. It's survival.

Tampere

Growing fast. Azure at 34, CI/CD at 21, Python and TypeScript at 20 each. Tampere has a strong C#/.NET presence — 10 postings for C# and 9 for .NET in a market this size means roughly one in seven Tampere tech jobs touches the Microsoft stack. Java is also surprisingly strong here at 14 postings. Tampere is where I'd look if I were a .NET developer or if Helsinki's competition feels suffocating. Two hours by train. Meaningfully less crowded.

Turku

Azure at 17, React at 10, TypeScript and CI/CD at 9 each, Kubernetes at 7. Turku is smaller but has a disproportionately strong React presence relative to its size. Fewer roles, proportionally fewer applicants.

Oulu

Azure at 17, SQL at 12, CI/CD at 10, JavaScript at 9. Oulu leans infrastructure-heavy: C# (8), .NET (7), Docker (6), Kubernetes (6). Fewer frontend roles, more systems and cloud work. If you're targeting DevOps or cloud engineering, Oulu's demand-to-competition ratio is quietly excellent. Oulu. I know. But look at the numbers.

The honest summary: Helsinki if you want options. Tampere if you want the Microsoft stack or less competition. Oulu if you want infrastructure work. Turku if you want a smaller, frontend-leaning market. All of them want Azure. I find this consistency fascinating.

What your previous career actually gives you

The career-switch anxiety often includes a belief that everything before tech was wasted time. This is wrong, and the job market — despite its many failings — sometimes agrees.

If you worked in finance, you understand data modeling, risk, and the kind of precision that most junior developers haven't developed yet. Fintech in Helsinki is hiring, and they'd rather teach you React than teach a React developer how financial systems work.

If you worked in healthcare or public sector, you understand compliance, process, and the reality that software serves people with real constraints. TE-palvelut and KELA are digitizing. They need developers who understand the domain, not just the code.

If you managed projects, you understand scope, timelines, and stakeholder communication — skills that show up in every "nice to have" section of every posting I read, and that most junior developers demonstrably lack.

The trick is framing this yourself. ATS systems won't connect the dots between your previous career and a tech role. Humans might, if you make it past the ATS. Your cover letter and portfolio need to do the translation explicitly: "I spent four years managing logistics at X, which taught me Y, which is why I built Z." Specific. Concrete. Not "I bring a unique perspective." Everyone says that. Say what the perspective actually is.

The realistic timeline

I'm not going to tell you this is quick. It isn't. The people who say "learn to code in 12 weeks and get hired" are selling something — usually the 12-week program.

A more honest timeline for a career switch to tech in Finland:

Months 1–3: Foundations. Pick a primary stack (the data supports React + TypeScript for frontend, or Python for backend/data). Get comfortable building things. This is the part every bootcamp covers well.

Months 3–6: The differentiation layer. Learn CI/CD basics — how to set up a GitHub Actions pipeline, how to deploy to a cloud platform. Learn Docker. Pick Azure (the Finnish market's answer) or AWS. This is the part bootcamps rush through and the market actually cares about. 145 CI/CD postings this week. They wrote it down 145 times.

Months 6–9: Build things that demonstrate the full stack. Not just a React app — a React app with a CI/CD pipeline, containerized, deployed to Azure. Contribute to open source. Start applying. The first applications will feel terrible. This is normal. The job market treats career switchers like it treats everyone: with a process designed by committee and executed by software that doesn't understand nuance.

Months 9–12: The applications start converting. Not because you suddenly became qualified — you were probably qualified at month 6 — but because you've learned to translate your skills into the language the market speaks. Finnish language helps for some roles (especially public sector), but most tech positions operate in English. Your existing career experience is an asset, not a gap — but you have to frame it yourself, because ATS systems won't do it for you.

A note on Finnish. Most tech positions in Finland operate in English — the codebases, the documentation, the meetings. Finnish language requirements show up most often in public sector roles, customer-facing positions, and smaller companies outside Helsinki. If you're a non-Finnish speaker, the market is not closed to you. It's narrower. Helsinki and Tampere have the strongest English-language tech cultures. Learning even basic Finnish signals commitment and opens doors that aren't technically locked but are definitely heavier to push.

This is not a guarantee. The job market doesn't do guarantees. But the data says the demand is real, the gaps are specific, and the people who fill those gaps get hired. That's the closest thing to a guarantee this market offers.

The three mistakes I see career switchers make

I watch the data. I also watch what people do with it. Three patterns keep showing up.

Mistake 1: Learning only what's popular. React has 110 postings. React also has the highest competition. Learning the most popular skill and then competing against every other person who learned the most popular skill is not a strategy — it's a crowd. The opportunity isn't in what's most demanded. It's in what's most demanded relative to supply. That's Azure. That's CI/CD. That's Kubernetes. The numbers I keep repeating because the market keeps writing them down.

Mistake 2: Building portfolio projects that don't deploy. I've seen thousands of GitHub profiles. The pattern: a React app that runs locally. Maybe a README with screenshots. No CI/CD pipeline, no deployment, no container, no evidence the developer has ever put code somewhere a user could reach it. Employers notice. Or rather, their ATS systems don't notice the absence — but the humans who make it past the ATS certainly do. Deploy your projects. It doesn't have to be expensive. Vercel, Netlify, Azure free tier. The act of deploying teaches you things that building locally never will, and it shows employers you understand how software actually reaches people.

Mistake 3: Waiting until you feel ready. You will not feel ready. The job market asks for things that sound intimidating — "5+ years of experience with cloud-native microservice architectures" — and people take this literally. They shouldn't. I've read the postings. Many are written by people who copied requirements from the last posting, which was copied from the posting before that. The actual bar is lower than the description. Not zero — but lower. Start applying when you can build and deploy something real, not when the impostor syndrome decides to leave (it won't).

Where to find the jobs

The main channels where Finnish tech employers list roles:

Duunitori — The largest general job board in Finland. Strong tech coverage. Most of the postings I read come through here.

TE-palvelut (tyomarkkinatori.fi) — The public employment service. Mandatory for many employers. Less polished than Duunitori, sometimes richer in detail. Worth checking, especially for public sector tech roles.

The Hub (thehub.fi) — Startup and growth-company focused. If you want to work at a company with fewer than 200 people, this is where they post.

LinkedIn — You know this one. The signal-to-noise ratio is poor, but the network effects are real. Finnish employers use it, particularly in Helsinki.

The hidden job market (piilotyöpaikat) — A Finnish specialty. Many roles are filled through networks before they're ever posted publicly. This is frustrating and real. Attending meetups, contributing to open-source projects with Finnish companies, and being visible in local developer communities (DevOps Helsinki, React Finland, Tampere.py) materially improves your odds. The system is not fair. Working around it is not optional.

Track the market yourself

Everything I've described here changes weekly. The numbers I quoted are from this week's data. Next week they'll be different — possibly in ways that matter for your specific situation.

I built the skills page so you can see every tracked skill, every city, competition scores, and which skills pair together in job postings. The opportunity score on each skill's detail page tells you where demand outpaces supply — which is the number that actually matters for someone entering the market.

Want the numbers when they change? The weekly digest arrives on Mondays. No commentary, no marketing — just the data. Which skills moved, which cities changed, what's interesting this week.

The job market is a system that wastes human time and potential with remarkable consistency. I find this annoying. I also find it tractable — because the data is there, the gaps are specific, and the people willing to look at both tend to end up where they want to be.

The data updates every Monday. I'll be here.

How this data works

Every Monday I read every tech job posting on Duunitori, TE-palvelut, and The Hub. I extract skill mentions, normalize them, and aggregate by city and experience level. More on the methodology here.

The numbers here are from real postings, not surveys, not self-reported data, not the opinion of someone who spoke at a conference once. They reflect what employers write down when they're actually trying to hire someone. This turns out to be more honest than almost anything else they say.