My interview process for the LTIMindtree drive began with an Online Assessment. This round evaluated my Logical Ability, Quantitative Aptitude, Technical/Programming skills, and Communication Skills. The questions ranged from easy to medium, primarily testing my speed, accuracy, and fundamental understanding of concepts.

Following the assessment, I proceeded to the Technical Interview, which lasted approximately an hour. Contrary to my initial expectation of immediate coding, this round started with my introduction, followed by an in-depth discussion about my final-year project. We covered various aspects like the backend and frontend technologies used, the challenges I encountered, and how I resolved them.

The technical discussion then expanded into several core areas. As I had mentioned Java as my strongest language, many coding and concept-based questions revolved around it. SQL and DBMS were extensively covered, including topics like joins, subqueries, normalization, triggers, indexing, aggregate functions, correlated subqueries, and specific queries such as finding the “third highest salary.” OOPS concepts like encapsulation, abstraction, inheritance, polymorphism, interfaces, abstract classes, constructor types, exception handling, threading basics, and shallow vs. deep copy were also discussed. Furthermore, questions on Computer Fundamentals and OS (deadlocks, memory allocation, process vs. thread, static vs. dynamic binding, copy constructor) and other technical topics like GitHub basics, version control, debugging, differences between delete/drop/truncate, string handling, and method overloading/overriding were asked.

I managed to answer almost all questions with clarity and confidence, missing only one. A key strategy that helped me was to actively steer the conversation. Whenever possible, I linked my answers back to my resume, skills, or projects, which kept the discussion focused on my strengths and allowed the interview to flow smoothly.

The final stage was a friendly HR Interview, lasting about 15 minutes. This round focused on assessing my communication skills and adaptability. Common HR questions included a short self-introduction, willingness to relocate, comfort with working in shifts, location preferences, and "Why LTIMindtree?". It was a much lighter discussion compared to the technical round, and the interviewer made me feel comfortable throughout.

I recently had an on-campus interview opportunity with LTIMindtree. The interview process consisted of two main rounds: a Technical Interview and an HR Interview.

Technical Interview:

The technical round started with some general introductory questions about my location, family, and favorite programming languages (Python and Java), where I was asked to rate my proficiency. Then, I was given three coding questions: 'Reverse the digits of a number', a star pattern printing problem (a diamond shape), and a string manipulation problem to count word frequencies in a given string. After the coding questions, the interviewer delved into conceptual differences like 'program vs. process', 'list vs. array', and 'list vs. tuple'. They also probed into Python's immutability with tuples and file handling. Some questions touched upon Machine Learning, its differences from traditional programming, and its main use cases. Towards the end of the technical round, I was asked about my favorite subject, DBMS, and then presented with an SQL query to identify students who had left school based on two tables. The round concluded with a question about future learning and an opportunity for me to ask questions.

HR Interview:

The HR interview focused on my personal profile and career aspirations. I was asked to introduce myself without mentioning projects, explain my college choice, and talk about my hobbies. Since I mentioned watching movies, the discussion moved to my recent watch and details about it. Other common HR questions included facing challenging situations, defining myself in three words, and my flexibility regarding relocation. Finally, I was given a chance to ask any questions I had for the HR representative.