Software Engineer applicants have rated the interview process at Mphasis with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 80% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Mphasis as a Software Engineer according to 1 Glassdoor interviews include:
Presentation: 33%
Drug test: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
The interview process at Mphasis typically involves multiple stages, including an initial HR screening, followed by one or more technical interviews focused on skills like DevOps, cloud, scripting, and problem-solving. These are often followed by a managerial or client round to assess communication, team fit, and project experience. The final step usually includes salary negotiation and offer discussion. The entire process emphasizes both technical expertise and alignment with organizational values and client requirements.
Interview questions [1]
Question 1
Can you explain how you implemented a CI/CD pipeline from scratch and integrated security tools like SonarQube or Veracode?”
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