KPIT Technologies Interview Questions
& Process

It usually starts with a chat with HR about your background, experience, when you can start, and what you're looking for salary-wise. Then there's a technical interview where they check your understanding of testing concepts, methods, tools, and your past projects. If it's an automation role, expect a deeper technical test, maybe involving some coding, writing test cases, looking at scenarios, or tackling real testing issues. After that, you might talk with a manager or project lead about your projects, how you work with others, communicate, and deal with tough timelines. If all goes well, there's a final HR chat to sort out the offer details, pay, and when you'd start.

So, for a Java Developer role, it usually kicks off with them looking at your resume to see your education, what tech skills you've got, and your project background. Then there's an HR or initial chat to check how you communicate, what your career plans are, and if you have a basic grasp of tech stuff. After that, they hit you with a technical interview to quiz you on core Java like OOPs, collections, handling exceptions, multithreading, and if you know frameworks like Spring or Spring Boot, plus databases and REST APIs. Sometimes you'll get a coding challenge or a practical test to see if you can actually solve problems and code. For more senior positions, they might throw in a system design round or another advanced tech interview. The last step is usually a chat with a manager or HR about fitting into the team, what they expect, salary, and the offer itself.

So at KPIT, the interview process basically involved a technical assessment, then a coding round, and after that, there were technical and HR interviews. The technical assessment part had questions on aptitude, logical reasoning, and core subjects. For the coding round, you might have to write some code. The final interview, which I remember really clearly, was an AI-based one. In this AI interview, a question pops up on the screen, you get about 20 seconds to prep, and then the video starts recording for 2 minutes. You can either talk the whole time or stop the video early.

I got a referral for an interview in May. The position wasn't explicitly stated, but I suspected it was ML-related. It was a theoretical, one-on-one call with a solutions architect, and I felt I did well. The interviewer mentioned that if an ML position opened up, I'd receive an email, but I haven't heard back yet.