Software developer CV for Norway: what a Norwegian tech lead reads

A developer CV in Norway is usually read twice: once by a recruiter who checks that the stack in the ad appears in your CV, and once by a tech lead who wants to know what you actually built. Neither of them is impressed by the CV style that works in some other markets — "passionate rockstar engineer who drove 10x growth". Norwegian hiring culture is restrained, and self-promotion without substance reads as noise, not confidence.

The good news for developers from abroad: tech is one of the fields where English is often the working language. On arbeidsplassen.nav.no you can filter job ads by working language (*Arbeidsspråk*) and see for yourself how many are in English. That also means your CV competes with many other international applicants — so it has to be specific.

What the employer is looking for

Stack, matched to the ad. List the languages, frameworks and platforms you have used in real work, and use the ad's own words. If the ad says "TypeScript" and "Azure", those exact words should appear in your CV — if they are true. Whoever screens looks for the ad's vocabulary first.

What you built, and your part in it. "Worked on a web platform" says nothing. "Built the payment integration for a booking app with 40,000 monthly users; owned the API and the tests" says a lot. Name the system, your role, the team size and one result you can explain in an interview.

How you work. Code review, testing, CI/CD, working in a small team, talking to users. Norwegian teams are often flat, and people are expected to take responsibility without being told. One line showing that you have done that is worth more than any adjective.

Proof you can link to. A GitHub profile, a portfolio or a public project is common and useful — but only if what is there is representative. Link one or two things you are proud of, not an empty profile.

Work permit status. If you already have the right to work in Norway, say so in one line. If you need a permit, do not hide it — the employer finds out anyway, and being clear saves both sides time.

The skeleton of a clean developer CV

One column, PDF, one to two pages. Two-column templates with skill bars often break when an applicant tracking system reads them — and a "Python ████░" bar tells the reader nothing.

Name · phone · email · city · LinkedIn · GitHub
Short profile (2–3 lines: role, years, main stack, what you want to work on)
Technical skills (grouped: languages / frameworks / cloud & tools)
Work experience (most recent first, with projects under each job)
Education
Languages
References (or "available on request")

A constructed example — the numbers are invented and should not be copied, the shape is the point:

Backend developer — fintech start-up, Warsaw (2022–2026)
Team of five, Kotlin and PostgreSQL on AWS
Built the payment reconciliation service; cut manual checks from daily to weekly
Owned the CI pipeline and code review for the backend
Worked directly with the support team on production incidents

Notice what is missing: no "passionate", no "rockstar", no list of twenty-five technologies you touched once.

Norwegian language on a developer CV

Even when the working language is English, write your Norwegian level honestly. "Norwegian: B1, taking the Norskprøven in spring" is better than leaving it out or writing "basic". Many teams speak Norwegian at lunch and in all-hands meetings, and the employer wants to know where you are heading. More in language levels on your CV.

Pay: what the statistics say

The median monthly pay for the group "Software developers" (*programvareutviklere*) is NOK 77,420, with the middle half earning between NOK 63,330 and 93,820 (Statistics Norway, table 11418, 2025 figures, all sectors). That is a whole-country, all-levels figure — seniority, city and sector move it a lot. It is still a better anchor than a salary from another country converted at today's exchange rate. How to use it: salary expectations in a Norwegian interview.

Five mistakes that cost you the interview

A US-style CV. Big claims, no specifics. Norwegian readers discount it.
Skill bars and ratings. They mean nothing and often break the ATS parse.
A technology list with no context. Every skill should appear in at least one project.
Three pages. One to two is the norm.
The same CV for every ad. Move the matching stack and project to the top each time.

Frequently asked questions

Should my CV be in English or Norwegian? Follow the ad. English ad, English CV. See CV in Norwegian or English.

Do I need a cover letter? Many tech ads ask only for a CV and a LinkedIn or GitHub link. If a cover letter is asked for, keep it short and specific to the company.

My job titles don't match Norwegian ones. Use the title you actually had, and add a short clarification if it is unusual. See Norwegian job titles in English.

Next step

Build your CV on the skeleton above and run it through a free CV check against the specific ad — you will see which words from the ad are missing before you send. Looking for English-speaking roles? Read English-speaking jobs in Norway. Not a software developer but an engineer in another field? See the engineer CV guide.