Tech Mahindra Interview Experience for Senior Software Engineer

Recently I interviewed Tech Mahindra for the Senior Software Engineer role. The opening was Mumbai-based. In the initial call, HR had mentioned that there would be 2 tech rounds 1 client round and one 1 hr round. Each round was 30 minutes long.

There are several rounds that you need to qualify.

Application Screening:

I got direct Naukri mail from the recruiter once applied, I got a call from the recruiter asking for technical details about the tech stack I am working on and, the year of experience I have. When I can give an interview in detail.

1st Technical Interview:

This round was based on the Java Backend developer(Sr. Software Engineer) position so most questions are based on Java only. The interviewer had 15+ years of IT experience.

Listing a few of the tech questions asked.

• Explain OOP concepts.
• What are Abstract classes and Interfaces?
• Why do we need a functional interface so we can have SAM(Single Abstract Method) in the normal interface?
• Why do we use Spring Boot?
• Do you know Spring security?
• What is Auto-configuration in spring?
• Explain StringBuffer and StringBuilder.
• Explain how would you read a CSV file from a remote location.
• Explain how HashMap internally works.
• Hash Collision Technique?
• What is a circuit breaker?
• Have you worked with multi-threading? Why synchronize keyword is used
• Explain to me the significance of volatility.
• Overloading and Override? What are the rules for both?
• Explain the collection framework.
• Do you know what is fail-fast and fail-safe iterator

2nd Technical Interview:

This round is almost the same as the first but it bit more in-depth round. More focused on Spring concepts. Few questions

• Explain Singleton’s design pattern. Why we would need it.
• What is a prototype design pattern? Give me a use case for it
• What are exception types? Explain with an example.
• Explain to me how Spring MVC works.
• What is hashcode why would need it?
• Explain the method of the object class. why notify and notify is in the Object class and not in Thread?
• Explain the best things you ever worked on.

3rd Technical Interview:

This round was a surprise for me even after hr stating me there would be two rounds. It was on quick and fast round without prior information about the round. It was the same Java questions only.

Client Round:

This round majorly focuses on the client with whom you will be working i mean your client might be any bank or vendor. So actual people from their team interview you and ask basic questions about your experience, skills, project you work on. some Java basics and mostly security questions be ready with that.

Offer and Decision:

Received an offer after a prolonged process involving strict background verification. Despite the positive experience, I declined the offer due to the offered compensation being lower, a lengthy 90-day notice period, and the requirement for full in-office work.

Overall Experience:

After almost one and a half months I received an offer letter. The interview process was enriching and insightful, covering a broad spectrum of Java and Spring-related concepts. It provided exposure to MNC interview procedures and interactions with potential client teams.They have very strict background verification process and lengthy process for documents upload and all other things as well. It was one of the best experiences I had because I am working in a very good product-based company and wanted to give an MNC interview and try out working there once.

Navigating Tech Mahindra’s interview process for the Senior Software Engineer role in Mumbai was a captivating journey steeped in technical depth and corporate insight. From initial technical screenings to multifaceted rounds exploring Java intricacies, Spring frameworks, and client-oriented discussions, each stage was an immersive learning experience. Despite the enriching exposure to MNC protocols, declining the offer due to compensation misalignment, a lengthy notice period, and full in-office work requirements was a decision reflecting thoughtful consideration. This experience encapsulated profound insights and added nuanced layers to my career trajectory within the dynamic tech landscape.

Hope this will help others!!!