Mphasis Interview Questions
& Process

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.

First up was the HR screening to check if I'm a good fit, covering my background and how I communicate. They asked about my experience, when I can start, what salary I'm looking for, and why I applied. Then, there were two tech rounds focusing on my software testing skills and experience. The questions were mainly about the testing process itself – things like test planning, creating test cases, the defect lifecycle, SDLC, different kinds of testing, and methodologies like Agile/Scrum. I also had to talk about my past projects, my part in them, any hurdles I came across, and how I made sure the work was good quality. The very last bit was a chat about salary and benefits, where they sorted out the pay and other employment details.

I've been through a lot of interviews with big companies, and it's all been pretty much the same: messy interviews, bad behavior, and tests that don't actually check if you can do the job. The Mphasis interview for React Developer was especially weird. I just finished the fourth try at the first stage because the system kept messing up in the earlier tries, not my fault. The questions were all theoretical and about abstract situations. I even told the interviewer that these questions aren't good for figuring out skills in just 45 minutes. It seemed like the interviewer agreed with me based on their body language. So, it makes you wonder why they ask these questions if they know they're not realistic, and who even makes them up and what they're supposed to prove. The questions were way too broad and deep for a 45-minute chat. It felt more like they wanted to trip you up and find mistakes under pressure rather than see what you can actually do. Honestly, it was one of the strangest and most useless interviews ever. Sometimes companies just lose control of their own process. I had an interview at a bank recently, the second stage, and it wasn't about tech skills but totally about professionalism. The interviewer left the screen and put on their jacket while we were still talking on Teams. This shows how they treat candidates. Another really unsettling experience was at a famous tech company. The interviewer was super positive and engaged the whole time. I used the STAR method and talked about my projects, giving detailed answers and actually enjoying it. But then, during the interview, the interviewer started getting messages from their manager on Teams. Right after that, their whole attitude changed. They stopped being positive and said, 'I shouldn't have commented.' So, basically, the evaluation changed on the spot because of internal messages, not my answers. I told the recruiter the interview went great, but the manager quickly marked me as 'not suitable for the client.' It was all just a formality to fill their candidate pool. I'd worked with the same company's clients before and met their expectations, so I don't get why I didn't fit this time. The process was rigid and focused on stressing the candidate, not on testing skills. These experiences show big companies really need to rethink how they treat candidates and structure their interviews.

So Mphasis interview usually kicks off with an online test checking your aptitude, logical thinking, verbal skills, and some basic tech stuff like programming, OOPS, DBMS, and computer basics, with a few easy coding questions sometimes. If you pass that, you go into a technical interview. They grill you on your core subjects, your favorite programming language, data structures, SQL, and really dig into your college projects or internships. After that, there's a managerial or techno-managerial round to see how you handle problems, work in a team, communicate, adapt, and understand real-world stuff. Finally, an HR interview checks your background, what you want career-wise, your strong and weak points, if you can move or do shifts, and if you're a good fit for the company culture.