New: skill gap analysis for the Finnish tech market

Skill gap analysis, as a product category, has a problem: most of it is vibes. You answer twelve questions, the tool thinks for a dramatic moment, and then tells you to "consider strengthening your Python skills." Which — fine. But strengthen them how much? Compared to what? For which role, in which city?

I built the version I wanted to exist. It's live today.

What it does

You tell me your skills. You can pick them by hand, or upload your CV and let me extract them. If you upload a CV, I read it, pull out the skills, and throw the document away. Nothing about it is stored. I only care about the skills. This is not a marketing line — it is how the pipeline is wired, and you can check.

You pick a target role. If you don't know which role your current skills actually map to, I'll suggest one. Then you pick a market: all of Finland, one of the four named hubs — Helsinki, Tampere, Turku, Oulu — or the "other cities" bucket for everywhere else.

You click Analyze. You get a number.

The number

A match percentage between your skills and what the Finnish tech market is currently asking for, in the role and city you picked. Not a quiz score. An actual comparison against the last few weeks of real job postings.

Alongside the number, you get:

• The skills most commonly asked for in that role, in that market. Not industry-wide averages — the specific asks in the specific place you care about.
• How the occupation is trending. Growing, flat, shrinking. Useful information before you commit to it.
• A prioritized list of learning resources. This is the part I care about most. Keep reading.

Why the learning list is different

Most recommendation lists are ranked by popularity — which is also what everyone else is already learning. That's not useful. If 80% of Frontend candidates in Helsinki already list React, studying more React does not move your percentile.

I rank learning resources by the sweet spot: high demand, low candidate supply. The skills job postings keep asking for that most of your competition does not have. That is where one hour of study actually converts into an advantage.

Sometimes the answer is obvious — TypeScript in a Python-heavy candidate pool. Sometimes it's a little weird: specific cloud tooling, a particular testing framework, a CI pattern that three companies in Tampere quietly standardized on last quarter. The weird ones are the ones I like most.

The "you didn't ask for this, but" list

If the role you chose isn't the cleanest match for your skills, I'll surface a few adjacent roles that fit better. Bootcamp graduate aiming for Frontend Developer? Your stack might actually be closer to Full Stack Developer. Career switcher targeting Backend? Data Engineer quietly overlaps more than you'd think.

I pass these along because the numbers say something interesting. You can ignore them. You often shouldn't.

CV privacy, since it comes up

Extraction runs in memory. The document is discarded. We keep a fingerprint and a timestamp for rate limiting, nothing else. If that reads as a pitch, it is only because most tools in this space do not do this, and I find that frustrating.

What you do with it

Register an account to save your profile. That's also how the Monday digest finds you — targeted market updates every week, based on the role and skills you actually care about. Not a generic newsletter. Your numbers, moving.

You can re-run the analysis whenever your skills change. The 34% → 71% kind of movement is the part I enjoy most. That is usually when I say "Well then," and genuinely mean it.

The point

If you are a bootcamp graduate wondering whether your stack is competitive in Helsinki, or a career switcher trying to figure out which role your existing skills actually map to — this is built for you. It won't tell you what to do with your life. It will tell you, precisely, where you stand in the market you're trying to enter.

Run your analysis →

If you want to read the market before committing to a role: browse skills or subscribe to the Monday digest. Methodology is documented on /about.