Ericsson interview, decoded.

Updated · Sources at the end

Ericsson's loop is the most conventional in Stockholm and the least documented, because it varies by team. The company's own hiring page gives the shape: one or two short recruiter conversations, an online test or case for certain positions, then one to three interviews with the hiring manager and sometimes senior management, then references, then a contract. There is no company-wide coding bar, no case study round like Spotify's and no take-home like King's; what the manager round tests is set by the team, which for most engineering roles in Kista means C++, Java or Go, Linux, networking and the 5G product the team owns. On Glassdoor, candidates rate it easier and more positively than Spotify's or Klarna's.

Free · 2 minutes · no account

The questions for your exact Ericsson role and level.

See the questions Ericsson asks ↓Run a free mock interview →

Interviewing at Ericsson? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Ericsson hires

Ericsson hires software developers in C++, Java, Go and Erlang for radio and baseband software, cloud-native core network and orchestration products, developer platforms and AI in networks, plus test, DevOps, ASIC and system engineers, mostly at the Kista headquarters with sites in Lund, Gothenburg, Linköping and Luleå. It runs an Early Career Program and graduate schemes. In January 2026 it announced around 1,600 role reductions in Sweden, so hiring is selective and concentrated in cloud, AI and 5G software.

02

What is the Ericsson interview process?

Ericsson publishes its process and candidates broadly confirm it: short, with the weight on the interview with your future manager. Stockholm reports are fewer than for Spotify or Klarna, so the shape below leans on the company's own page and the pattern across its sites.

01
Application and screening
Online, through Ericsson's careers portal

A recruiter matches the profile to the role. Ericsson says it takes a few minutes once you have an account; the matching is where most applications stop.

02
Recruiter conversations
One or two short calls by phone or video

The offer's details, your skills, experience and expectations, including pay. Ericsson says this call is about behavioural skills and a broad picture of your technical range, not technical detail.

03
Online test or case
For certain positions only

A technical test verifies skills for some engineering roles; other roles get a case interview or an assessment. Graduates and interns sit aptitude and coding tests.

04
Interviews with the hiring manager
One to three interviews, typically 45 to 60 minutes each, on Teams or in Kista

Your future manager, sometimes with senior engineers from the team or senior management. The team may combine the meeting with a task that tests the skills the role needs: a coding exercise in the team's language, a design discussion on their product, or a walkthrough of your own work.

05
References
At the end of the process

Ericsson asks for references and contacts them before the contract.

06
Offer
A contract with the position and the benefits package

Ericsson is covered by collective agreements, so pay, pension and notice follow the Teknikavtalet terms for engineers.

03

What Ericsson screens for

Ericsson's hiring page asks for four things and its interviewers are reported to check them plainly.

  • Examples of situations you have been in and what you learned from them, said as stories
  • Familiarity with the role's requirements and how your experience lines up with each one
  • Knowledge of the company and its technology: 5G, cloud-native core, the products the team ships
  • Being yourself, which in Kista means a calm, first-names conversation rather than a performance
  • Fit with a large, long-lived engineering organisation: process, quality, working across sites
04

Ericsson interview questions

Candidate-reported themes

Reported questions are conventional and role-specific. The technical themes below are what Ericsson's Swedish postings ask for, which is what the manager round draws on.

Behavioural & motivation

  • Why Ericsson, and what do you know about what this team builds?Listening for: Specificity · Connection · Research
  • Tell me about a situation you were in, what you did, and what you learned from it.Listening for: A specific situation · What you did · What you learned
  • Describe working across teams or sites on one product. How did you keep it aligned?Listening for: The setup · How you kept it aligned · The outcome
  • Walk me through a piece of software you own end to end: design, testing, what broke.Listening for: Design choices · How it was tested · What broke and why
  • How do you approach quality in code that runs in a network for years?Listening for: Concrete practices · Built to last · A real example

Technical

  • Practice: two threads update a shared counter in C++ and the total comes out wrong. How would you find the problem, fix it and test it?C++ in a multi-core environment: Threaded code, memory, unit and multi-component tests, as Ericsson's radio and baseband postings describeListening for: Names the race · A sound fix · How to test it
  • Practice: you run a Go service on Kubernetes across many nodes. How would you roll out a new version safely and know if it is misbehaving?Cloud-native core and orchestration: Kubernetes, containers, Go or Java services, CI/CD, observability across many nodesListening for: Safe rollout · Knowing it is healthy · Pipeline and tests
  • Practice: walk me through the main parts of a 5G network and where the software your team would own sits in it.Networking and telecom fundamentals: Protocols, Linux, the 5G architecture the team sits in; candidates with a communications background are asked deeperListening for: The main parts · Protocols and Linux · Tied to the team
  • Practice: given a list of network events with timestamps, find the busiest one-minute window. Explain your approach in your language.Data structures and algorithms: Straightforward coding in the team's language, rated easy to moderate in candidate reportsListening for: Sound approach · Complexity stated · Edge cases
  • Walk me through something you designed and shipped, with how you tested it and what failed.Your own work: A walkthrough of something you designed and shipped, with the testing and the failureListening for: Clear design · Testing described · An honest failure

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my Ericsson questions →
05

Pay

JS4, entry levelSEK 476K median total pay, Greater Stockholm
JS5SEK 551K median total pay, Greater Stockholm
JS6SEK 639K median total pay, Greater Stockholm
JS7SEK 730K median total pay, Greater Stockholm
JS8SEK 929K median total pay, Greater Stockholm

Levels.fyi for software engineers at Ericsson in Greater Stockholm, read on 13 September 2026: the median package across levels is SEK 571K, almost all base, with stock and bonus under SEK 10K a year at every level. The ladder starts lower than Spotify's or Klarna's and runs longer. Ericsson is covered by collective agreements, so pay is revised once a year in the lönerevision and the occupational pension is on top. Our Stockholm salary page has the comparison.

Ericsson software engineer salary in Stockholm, next to the rest of the city →

06

How to prepare for an Ericsson interview

  1. Find out which team the posting belongs to and learn its product. Ericsson's page asks you to know the company and its technology, and the manager round is with the people who build one specific thing: radio software, a core network function, an orchestration product.
  2. Prepare examples the way Ericsson asks for them: situations you were in and what you learned. Three stories, each with the decision, the outcome and the lesson, cover most of the manager round.
  3. Brush up the fundamentals in the team's language. For radio and baseband that is threaded C++ with unit and component tests; for core and cloud it is Go or Java on Kubernetes. Candidates report the coding as easy to moderate, so the differentiator is being fluent, not being clever.
  4. Expect a task with the manager interview and ask in advance what form it takes. Ericsson says the meeting may be combined with a test of the skills the team needs, and it differs by team.
  5. Line up references early. Ericsson asks for them at the end and contacts them before the contract, so a reference who is slow to reply delays the offer.

This guide is written from Ericsson's published hiring process and candidate reports, most of which come from sites outside Sweden. Ericsson's loop is set by each team, so the manager round in Kista may differ from what is described here; the shape and the pay are the parts you can rely on. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Google Stockholm, EA DICE or Paradox Interactive? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run an Ericsson mock: spoken answers, coached on the spot. Your first mock is free.

Run an Ericsson mock →
07

FAQ & sources

What is Ericsson's interview process?

Ericsson publishes its process and candidates broadly confirm it: short, with the weight on the interview with your future manager. The stages, in order: Application and screening; Recruiter conversations; Online test or case; Interviews with the hiring manager; References; Offer.

What does Ericsson look for in candidates?

Ericsson's hiring page asks for four things and its interviewers are reported to check them plainly. Examples of situations you have been in and what you learned from them, said as stories; Familiarity with the role's requirements and how your experience lines up with each one; Knowledge of the company and its technology; Being yourself, which in Kista means a calm, first-names conversation rather than a performance.

What questions does Ericsson ask in interviews?

Reported questions are conventional and role-specific. Technical themes: C++ in a multi-core environment; Cloud-native core and orchestration; Networking and telecom fundamentals; Data structures and algorithms; Your own work.

How do I prepare for an Ericsson interview?

Find out which team the posting belongs to and learn its product. Ericsson's page asks you to know the company and its technology, and the manager round is with the people who build one specific thing: radio software, a core network function, an orchestration product. Prepare examples the way Ericsson asks for them: situations you were in and what you learned. Three stories, each with the decision, the outcome and the lesson, cover most of the manager round.

Prep for a real Ericsson role

Practise your Ericsson interview, out loud.

Paste a real Ericsson posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free. Calibrd is built in Stockholm, by a hiring manager who has run engineering hiring here, so this is a loop we know from the other side of the table.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Ericsson prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Ericsson Interview: Process, Manager Round, Pay — Calibrd