Senior developer interview questions (Norway)

Senior developer interviews are a different genre

If you have been through interviews as a junior and mid-level developer, you know what you went through: coding tests, FizzBuzz-style tasks, maybe an algorithm in focus. Senior interviews are fundamentally different. Companies aren't buying a good coder, they are buying someone who can make technical decisions and influence a team.

This guide is for developers with 7+ years of experience applying for senior, lead or staff roles at Norwegian companies. Many of the tips also apply to equivalent roles outside development: senior data engineer, senior PM, lead UX.

Which companies actually recruit seniors

In Norwegian tech there are a few different categories:

Established tech companies (over 200 employees)

Schibsted, Cognite, Telenor, FINN, Vipps, Storebrand, DNB digital. They have structured interview processes, often 3 to 5 rounds, and they look for people who can become a technical lead or architect over time.

Scale-ups (50 to 200 employees)

Otovo, Tise, Boost, Findable, Foreldre.no. The senior role is often more hands-on and practical. You are expected to write code while also making technical decisions and mentoring juniors.

Consulting firms

Bekk, Knowit, Bouvet, Kantega, Sopra Steria. The senior role often focuses on client delivery and advisory work. Less deep technical architecture, more pragmatic problem solving.

The public sector and digitalisation teams

Skatteetaten, NAV, Digdir (the Norwegian Digitalisation Agency, formerly Difi), the Norwegian Directorate of Health. The senior role often focuses on architecture, security, and working with case officers and business owners.

Each category has its own interview patterns. Adapt your preparation.

The four most common rounds

Round 1: Introductory phone call with a recruiter

15 to 30 minutes. They talk about your background, why you are applying, and what you expect in pay (trying to filter). No technical depth here.

Preparation: a 30-second pitch about your career, a ready salary expectation or range, and questions about the company culture.

Round 2: Technical depth with a developer or tech lead

60 to 90 minutes. This is the technically heavy round. Expect a combination of:

• A deep dive into earlier projects: "Explain the architecture of the X system you built."
• System design: "How would you design a search engine?", "How would you build a payment module that handles 10,000 transactions per minute?"
• Trade-off discussion: "Why did you choose Postgres over MongoDB?", "How do you weigh synchronous against asynchronous communication?"

Preparation: have two or three projects ready where you can draw the architecture on the whiteboard (or a shared screen) and explain which trade-offs you made.

Round 3: A practical coding task

Often a take-home task, sometimes live. For a senior role they rarely test algorithms (you have proved that with experience), but more often:

• Pair programming on a realistic task: Fixing a bug in an existing codebase, or adding a feature.
• Code review: You read a pull request and comment on it.
• Live debugging: A system that doesn't work, and you have to find out why.

Preparation: be comfortable commenting on code you haven't written, and thinking out loud while you work.

Round 4: Leadership and collaboration

Often with a tech lead or engineering manager. They test:

• Mentoring experience: "Tell me about a time you helped a less senior developer."
• Conflict handling: "How do you handle disagreement over technical choices?"
• Influencing: "How do you get others on board with a change?"

Preparation: have three concrete examples of mentoring, one of conflict, and one of driving change.

A possible round 5: A meeting with a manager or stakeholder

20 to 30 minutes. More about cultural fit than technical. Questions about what you want to achieve, how you work with non-technical people, and whether you fit together.

The 12 most likely questions

After many interviews for senior roles in Norwegian tech, these questions keep coming up. Prepare honest answers with concrete examples.

1. Tell me about a complicated technical problem you solved. Choose something where you had to balance several concerns. Not only technical, but also team dynamics or stakeholder pressure.

2. What is the worst technical decision you have been part of? Honesty counts. Show that you learned, not just that you were wrong.

3. How would you design X? Learn Boris Cherny's SDS framework: "Functional, Non-functional, Architecture, Trade-offs". Spend 5 minutes understanding the problem before you start drawing.

4. Why did you choose technology X? Never answer "because it's modern". Trade-offs, context, the alternatives you considered.

5. How do you handle disagreement with other developers? A concrete example. Ideally one where you lost the argument and learned something.

6. How have you mentored junior developers? Concrete. Two or three examples. What they learned, where they are now.

7. How do you influence technical decisions when you have no formal authority? The senior role is often about this. RFC documents, code reviews, pairing, demos.

8. What do you do if non-technical people demand something you think is a bad idea? Explain the trade-offs. Suggest alternatives. Accept the decision if it is theirs to make, but document it.

9. How do you keep yourself technically up to date? Concrete sources. Books, podcasts, communities, experiments.

10. Tell me about a project that didn't go as planned. Show maturity. Don't blame others. Explain what you did differently afterwards.

11. What level of code quality are you comfortable with? Be realistic. A perfectionist answer is a red flag. "Works in production with reasonable maintenance" is better than "100 percent test coverage".

12. Where do you see yourself in 3 years? Honesty, but tied to what the company can offer. If you say "starting my own company", you rarely get an offer.

What they don't say explicitly

There are things senior developers easily fail on, but which aren't always said out loud:

You should be pragmatic, not ideological

If you say "I will never work with JavaScript again, only TypeScript", you close doors. If you say "We tried TypeScript on project X, but dropped it because the team was too small to justify the transition", you sound senior.

Test coverage isn't always the answer

An aggressive "everything must have 95 percent test coverage" is a junior attitude. A senior answer: "We test where it matters most, core business logic and the APIs out of the service. UI tests selectively where bugs are costly."

You should be able to choose not to build

"Not everything needs a microservice. We solved it with a cron job and a Slack integration in two days." A senior answer.

You should be able to admit what you don't know

"I haven't worked with Kafka in production, but I can mention which trade-offs I would consider" is better than bluffing.

Salary negotiation for seniors

Senior roles in Norway usually have 100,000 to 250,000 kroner of negotiating room above the ad's starting point. To negotiate well:

Get a number first

When they ask "what do you expect?", answer "what is the range you have for the position?". If they give a number, let them have the first move.

Use market data

LinkedIn salary insights, Glassdoor (less accurate in Norway), and conversations with former colleagues give a reference. Statistics Norway's (SSB) salary statistics are conservative, but valid as a baseline.

Negotiate the package, not just base salary

Pension, shares, working from home, flexible hours, a course budget, holiday. Senior roles often have more variables than juniors.

Know which buttons you can press

If the company is publicly funded, or a scale-up with limited cash flow, base salary may be locked. Negotiate shares, options or bonus.

Give them a way out

No ultimatums. "I'd like to look at this and will get back to you" is better than "I need 1.1 million or I'm walking".

After the offer

When you get an offer:

1. Ask for 2 to 3 days to consider. Never accept on the phone immediately.
2. Check whether you have other processes going and rank them honestly.
3. Consider more than pay, also the team, the project, growth opportunities.
4. Negotiate the package once, not iteratively over several weeks.
5. Get it in writing before you resign from your existing job.

The hardest thing is saying no

If the offer doesn't feel right, the pay is too low, or the team dynamic felt off in the interview, say no. Senior developers have better alternatives than most, and a wrong hire costs you 1 to 2 years.

Keep track of all your parallel processes in a pipeline, so you actually know what you are comparing.