Ericsson India Global Services PVT. Ltd Interview Experience
Question Details
Round 1(Written): The first round comprised of 40 MCQ questions including Quantitative Aptitude, Verbal, and Reasoning.Quantitative aptitude and Logical section was not so...
Full Details
Round 1(Written): The first round comprised of 40 MCQ questions including Quantitative Aptitude, Verbal, and Reasoning. Quantitative aptitude and Logical section was not so tough but you need to brush up your memory because questions were little tricky. Give proper time to each section coz we need to qualify cutoff of all the given section. There is no -ve marking so attempt as much as possible from each section. Suggestion: I would like to suggest that keep practicing such question before giving the main exam. It will boost problem solving confidence. Round 2(Technical Interview): They asked questions from all of my college projects which was a website for bank. So the question was, why you created ?, what technology used ?, write command for database connection, SQL query for fetching data for all the clients who use band within 30 days etc.. They asked me to create list in PHP, next question was about advance java and i was not sure about it still i tried to attempt as much as I know. I choose to say something instead of saying "I don't know" throughout the interview. Tips:- Explain each question with example if possible and It is totally fine if you don't know the answer of any question, just don't lose your confidence. :) Round 3(HR): On another day Discussion on my all projects. Discussion over Ericsson's work culture. Then general HR question. Tips :- You should know each and every word of your Resume and about the company.
About This Question
This is a reported interview question from a ericsson interview for a data science role during the phone screen round reported in 2023.
It covers the following topics: Sql .
Difficulty rating: Hard
Topics
About Ericsson Interview Reports
This question was reported by a candidate who interviewed at Ericsson. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Ericsson are the higher-signal extractions to take from this report.
For broader preparation context, the Ericsson interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Ericsson reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Ericsson Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Ericsson reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.