Ericsson Software Engineer candidates mostly describe a conversational process: an HR screen, a technical round on fundamentals and resume projects, and a manager conversation, sometimes with an online assessment.
$103K
Avg. Base Comp
$115K
Avg. Total Comp
3-4 rounds
Typical Rounds
1-4 weeks
Process Length
Candidates describe the Ericsson Software Engineer interview as more conversational than algorithm-heavy, and the most repeated theme is resume depth. Several people say interviewers spent much of the time on past projects, previous work experience, and why they fit the role. Be ready to explain what you personally built, the role you played on each project, and the decisions you made along the way.
Technical questions are usually fundamentals. Candidates mention constructors and destructors, struct versus class in C++, Python concepts with short code snippets, data structure differences, Java and OOP basics including memory management, Docker, and design patterns. A senior candidate reports a first round on Java, Spring Boot, Java 8 and reading code snippets on the spot. Check the job posting for the stack and be comfortable talking through it.
Some candidates report online tests before the live interviews. An intern candidate describes a 45-minute C++ assessment with three exercises, including a longest-substring-without-repeating-characters problem. A senior candidate describes multiple-choice technical questions, a coding test and personality tests. Another candidate had a small whiteboard programming exercise. Practice writing clean solutions to classic problems under time pressure.
Behavioral questions are typically straightforward: why Ericsson, handling challenges or conflict on a team, and where you see yourself in five years. One candidate was also asked how they would test a pen, so practice structuring a simple testing scenario out loud. Candidates report mixed experiences with communication, including some silence between steps, so follow up politely.
Synthesized from 35 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Ericsson process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Ericsson
Write a query to forecast each project's budget and label it overbudget or within budget
| Question | |
|---|---|
| Bagging vs Boosting | |
| Hurdles In Data Projects | |
| The Longest Journey | |
| Fixed Length Arrays: Addition | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| k-Means from Scratch | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Prime to N | |
| The Brackets Problem | |
| Cyclic Detection | |
| Size of Joins | |
| Sort Strings | |
| Get Top N Frequent Words | |
| Find Duplicate Numbers in a List | |
| Swapping Nodes | |
| CNNs vs Intensity-Based Features | |
| Append Frequency | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Closed Accounts | |
| Skyscanner Partner ETL | |
| Precision and Recall | |
| Valid Anagram | |
| Check Matching Parentheses | |
| Success Measurement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report an initial HR or recruiter conversation covering background, motivation and basic role fit. One described it as very general, mostly motivation and a walkthrough of their background. Prepare a concise self-introduction and a clear answer to why Ericsson and why this role.
Some candidates report a timed assessment before the interviews. Reports include a 45-minute C++ test with three exercises, including a string problem, and a set of multiple-choice technical, coding and personality tests. Others describe no such step, so it may depend on the team or role.
Candidates report technical rounds that focus on fundamentals and on their past experience. Topics mentioned include OOP, C++, Java, Spring Boot, Python, data structures, Docker and design patterns. Some reports include short code snippets or a small whiteboard exercise, while others report no live coding.
Several candidates describe a conversation with a hiring manager or team members that centers on past experience, team fit, handling conflict and career goals. Depth varies by report. Prepare specific project stories that show your own contribution.
Outcomes in the reports are mixed. Some candidates received offers within about one to four weeks. Others described silence after the interviews. One candidate describes a final offer discussion as a separate step, though the number of rounds varies by team.
