Mphasis Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 1,014 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mphasis.
Mphasis
Software Engineer
Mid Easy Negative experience No offer 1 round
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Technical Behavioral
So the interview process was kinda long and a bit messy. My interview got called off last minute, and after chasing them, it was finally moved to a 45-minute slot. It was mostly about Java stuff like Collections, Streams, JVM Memory, and Spring Boot for Actuator and config. I thought I did pretty well and answered most questions okay. But, even though it seemed to go well, I didn't get the job. It was super annoying waiting for the feedback, which took like three weeks. I kept asking for about two weeks, and HR said they still hadn't heard back from the interviewers. The whole thing felt like such a drag and took forever.
Confirmed questions1 question
- Standard Java Questions about OOPs, JVM Memory, Collections, and Streams
Mphasis
Software Engineer Intern
Intern Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Presentation
The interview process was very much about real projects and practical work. I had to talk through my projects from start to finish, covering the problems they solved, how the databases were set up, what tools I used, why I made certain implementation choices, any difficulties I ran into, and how I made the solutions better or more efficient.
Confirmed questions7 questions
- Can you tell me more about your projects?
- What were the problem statements for your projects?
- How did you design the database for your projects?
Mphasis
Associate Software Engineer
Entry Average Neutral experience Accept offer 5 rounds
Interview process
Technical screen Group Technical screen Technical screen Recruiter call
Interview formats
Technical Group Behavioral
The interview process has five stages to check different skills and if you're a good fit. First, there's an Aptitude Test to see how you solve problems, think logically, and analyze things. Then, we have a Group Discussion (GD) to check your communication, teamwork, and leadership skills. After that, you'll go through two Technical Rounds to assess your technical knowledge, problem-solving abilities, and practical experience. Lastly, the HR Round looks at your personality, career goals, and how you'd fit into the company culture. Each stage usually takes about 30 to 60 minutes, depending on the specifics.
Confirmed questions1 question
- Aptitude, Group Discussion, HR & 2Technical
Mphasis Software Engineer Interview Questions
Quoted word for word from Mphasis interview reports.
“Write a SQL query to find the number of customers who have never placed an order, given the Customers and Orders tables.”
Read reports →“What happens if a try block is followed directly by a finally block, without an intervening catch block?”
Read reports →“Could you write Java 8 code to determine the character that repeats the most times in the string "India"?”
Read reports →“In a Springboot application, if ten users access the same API simultaneously, how many instances would be created?”
Read reports →“How do you find the position of a letter within a string in COBOL?”
Read report →“Could you write a program to determine if a given string is a palindrome?”
Read report →“How would you implement security for a microservice using Spring Security and JWT?”
Read report →“What are outer apply and cross apply, and what does delay validation in SSIS mean?”
Read report →“How would you use a different embedded server instead of the default Tomcat server?”
Read report →Formats, difficulty and experience
Across all 1,014 Mphasis interview reports.