Ericsson Software Engineer candidates report interview paths ranging from a single conversation to four rounds, with recurring emphasis on project depth, programming fundamentals, practical coding, and role fit.
$144K
Avg. Base Comp
$187K
Avg. Total Comp
4 rounds
Typical Rounds
1-4 weeks
Process Length
Ericsson Software Engineer interview reports point to resume and project depth as a central preparation area. Candidates were asked to explain prior responsibilities, technologies used, difficult implementation choices, and challenges they encountered. Prepare a short project walkthrough that covers the problem, your contribution, a technical decision, and the result.
Technical questions vary by team. Reported topics include C++, Java, Python, OOP, data structures, SQL, Spring Boot, and code snippets. Practical work also appeared in some accounts, including online assessments and a timed C++ assessment with three exercises. One recalled problem involved finding the longest substring without duplicate characters. Review the fundamentals behind the languages and tools on your resume, then practice explaining your reasoning as you work. For SQL, reported questions included finding the second-highest salary and distinguishing JOIN from UNION.
Behavioral and motivation questions can be part of the same conversation. Candidates recalled prompts about why they applied, future goals, prior responsibilities, role fit, and how they would test a pen. Reported processes range from a single conversation to four rounds and from about one to four weeks, so the sequence and pace can differ. Be ready to communicate clearly about collaboration and technical decisions.
Synthesized from 11 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 | |
| Prime to N | |
| Merge Sorted Lists | |
| The Brackets Problem | |
| Cyclic Detection | |
| Sort Strings | |
| Size of Joins | |
| Swapping Nodes | |
| Get Top N Frequent Words | |
| Append Frequency | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Closed Accounts | |
| Precision and Recall | |
| Find Duplicate Numbers in a List | |
| CNNs vs Intensity-Based Features | |
| Target Indices | |
| Success Measurement | |
| Swap Variables | |
| Portfolio Platform Architecture |
Synthesized from candidate reports. Individual experiences may vary.
Several Software Engineer candidates reported an HR or recruiter conversation. Recalled topics included self-introduction, prior experience, why Ericsson, role fit, and behavioral questions. Prepare a concise account of your background and why the role matches your experience.
Some candidates reported an online, proctored, written, or whiteboard-based exercise. Examples included programming multiple choice, coding questions, FIFO behavior without a queue library, and a longest-substring-style problem. Practice implementing core logic under time pressure and explaining your approach.
Technical discussions covered languages and fundamentals such as C++, Java, Python, OOP, data structures, SQL, Docker, networking, REST APIs, design patterns, and code snippets. Candidates also described detailed questions about project implementation and the technologies listed on their resumes.
Some reports include manager or team discussions about prior responsibilities, project challenges, team fit, future goals, and handling disagreements. Use specific examples to show how you made technical decisions, worked with others, and communicated through problems.
