Software Engineer applicants have rated the interview process at Mphasis with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 69% positive. To compare, the company-average is 64.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 12 days to get hired, when considering 63 user submitted interviews for this role. To compare, the hiring process at Mphasis overall takes an average of 13 days.
Common stages of the interview process at Mphasis as a Software Engineer according to 63 Glassdoor interviews include:
One on one interview: 25%
Phone interview: 19%
Skills test: 13%
Group panel interview: 9%
Presentation: 9%
IQ intelligence test: 8%
Background check: 7%
Personality test: 5%
Drug test: 3%
Other: 2%
Here are the most commonly searched roles for interview reports -
It was easy interview for fresher when mass hiring and Java developer they will ask basic question for fresher . As you are more than two year experience start medium level question of Java topics .
Interview questions [1]
Question 1
What is overloading/ overriding in Java ?
What is final , finnalize?
First round was aptitude which have logical questions and second round was technical interview in which they have asked about sql and introduction.Based on skills they have asked me the questions
round 1 screening.
round 2 cpp concepts all including dsa concepts.
Initial screening over phone and later online interview. Asked all releant questions for cplus plus and had to know all th concepts.
thats all i have to say.
I applied online. I interviewed at Mphasis (Bengaluru)
Interview
The interview process was quite lengthy and somewhat unorganized. Initially, my interview was scheduled but got cancelled at the last minute. After multiple follow-ups, it was finally rescheduled for a 45-minute session.
The interview mainly focused on standard Java topics such as Collections, Streams, JVM Memory, and Spring Boot concepts like Actuator and configuration. The discussion went well, and I was able to answer almost all the questions confidently.
However, despite the interview going well, the final result was negative. What made the experience more frustrating was the delay in communication. The result was shared after nearly three weeks, and even after continuously following up for about two weeks, the HR team mentioned they still hadn’t received feedback from the interview panel. Overall, the process felt quite tedious and slow.
Interview questions [1]
Question 1
Standard Java Questions- OOPs, JVM Memory, Collections, Streams