How to Build a Scannable Developer CV for Norwegian Tech Jobs

Developers eyeing tech roles in Norway quickly discover that the first thing recruiters look for is not a polished narrative but a clear, scan-ready list of technologies. Whether you are applying through Finn.no, LinkedIn, or a consultancy’s internal portal, the “Tech Stack” section determines whether your CV makes it past the initial filter. Below is a step-by-step guide that shows you how to structure a developer CV so the stack is instantly visible, and how to adapt that structure for product-focused companies versus consultancy-driven firms.

Why Norwegian recruiters scan the tech stack first

Finn.no and LinkedIn both offer keyword-based search functions that pull up CVs containing exact technology names. Recruiters in Oslo-area product teams often have only a few seconds to glance at a profile before deciding whether to open the full document. Because the job ad will list the required tools verbatim—e.g., React, Node.js, Docker, Kubernetes—the same wording must appear in your CV’s stack block.

Consultancies operate on a different timeline. They receive client briefs that specify a technology mix for each project. Their internal databases compare candidate stacks against those briefs automatically. If your stack list is buried inside a paragraph, the parsing algorithm will miss it, and you will be excluded before a human even sees your experience.

In practice, this means the stack list carries more weight than the prose that follows it. A well-formatted stack can push your CV to the top of a search result, while a vague “experience with web technologies” will likely be ignored.

Do this: Open the job posting, copy the exact technology names, and paste them into a dedicated “Tech Stack” section at the top of your CV.
Avoid this: Using synonyms or generic terms like “frontend frameworks” when the ad specifies “React, Vue.js, Angular.”

Layout tricks to make your stack instantly visible

1. Place a dedicated “Tech Stack” block at the very top

Position the stack right under your contact details and headline. Use a bold heading such as Technical Skills or Tech Stack and separate the block from the rest of the document with a thin line or extra spacing. Recruiters can then scroll directly to the list without hunting through work history.

2. Use bullet-point or inline list with exact naming

• Frontend: React, Vue.js, TypeScript, HTML5, CSS3
• Backend: Node.js, Express, Java (Spring Boot), Python (FastAPI)
• Cloud & DevOps: AWS, Azure, Docker, Kubernetes, Terraform

If you prefer an inline format, keep it concise: React, Vue.js, TypeScript | Node.js, Java, Python | AWS, Docker, Kubernetes. Whichever style you choose, maintain consistent punctuation and capitalization.

3. Limit each line to 3–4 technologies and group by category

Overloading a single line makes it hard to read. Grouping by category not only improves readability but also aligns with how hiring managers think about skill sets. For example, a product team may focus on “Frontend” and “Backend” separately, while a consultancy may scan the “Cloud & DevOps” column to match client infrastructure requirements.

4. Mirror the order of the job ad

If the posting lists “React, Node.js, Docker” in that sequence, arrange your stack in the same order. Recruiters often skim for the first few items, so matching the order signals that you have paid attention to the specific needs of the role.

5. Keep the rest of the CV clean and factual

After the stack, follow the Norwegian baseline: a reverse-chronological work history limited to 1–2 pages, concise bullet points, and GDPR-compliant personal details (no national ID, no marital status). A photo is optional and increasingly omitted in tech roles.

Internal resource: For a full overview of the Norwegian CV baseline, see our guide on Master the Norwegian CV: 1-2 Pages, GDPR Details & Jobbsøknad Pairing.

Tailoring the CV for product companies vs consultancies

Product-focused firms (e.g., Oslo-based SaaS startups)

• Depth over breadth: Highlight the technologies you have used extensively and tie them to measurable outcomes.
• Project results next to each tech: Example – “React (3 years): Led a redesign that reduced page load time by 40 %.”
• Emphasize impact: Show how your work contributed to product metrics such as user growth, retention, or revenue.

Do this: Include a short “Key Projects” subsection under each role, with a bullet that starts with the tech name and ends with a concrete result.

Avoid this: Listing every peripheral tool you touched for a month; product teams prefer evidence of mastery rather than a laundry list.

Consultancy-driven firms (e.g., digital agencies, system integrators)

• Breadth is essential: Clients may request a wide range of technologies across projects, so list all relevant tools, even if you used them briefly.
• Client scope matters: Mention the industry or client type to show versatility (e.g., “Implemented Docker-based CI/CD pipelines for a maritime logistics client”).
• Separate “Consultancy Experience” section: This can include short bullets that focus on client objectives, technology stack, and delivery timeline.

Do this: Add a “Consultancy Projects” bullet list that follows the standard work-history format, but keep each entry to two lines: technology + client + outcome.

Avoid this: Mixing deep product impact statements with consultancy breadth; the two audiences evaluate success differently.

Internal resource: If you are unsure whether to write your CV in English or Norwegian, read our comparison at Choosing Between English or Norwegian CVs for Norway Jobs.

Common mistakes and how to avoid them

• Embedding the stack inside long paragraphs – Recruiters miss it, and ATS parsers may not extract it. Keep the stack as a standalone block.

• Outdated tech names – Replace legacy terms like “jQuery” (unless the role explicitly requires it) with current equivalents such as “React” or “Vue.js”.

• Overloading the CV with every language ever touched – Aim for relevance. A concise list of 15–20 items is typical; anything beyond that dilutes focus and pushes you over the 2-page limit.

• Inconsistent naming – Use the exact spelling and capitalization from the job ad. “Node.js” and “NodeJS” are treated differently by keyword filters.

• Missing GDPR-compliant personal details – Include only name, phone, email, and optionally a LinkedIn URL. Omit personal numbers, birthdate, or marital status.

Quick checklist:

By following these guidelines, your developer CV will align with the expectations of Norwegian recruiters, whether they are hiring for a product team in Oslo’s tech hub or assembling a versatile consultancy squad for client projects across the country.

---

This article is part of a series on building effective CVs for the Norwegian market. Explore more templates and examples at our Browse CV templates page, or see real-world samples in the Resume examples by profession section.

---

Ready to put this into practice? Build your CV with CV Pro Maker using ATS-friendly templates that put these principles to work. Building, editing and previewing are free — no credit card to start. To download a polished PDF or DOCX, grab a one-time pack: pay once, no subscription.

New to the site? See what's free and what you pay for.