Real, anonymous reports from people who interviewed for Software Engineer at Ltimindtree, newest first and distilled into what to expect across the loop.
My process followed a pretty standard structure: an online aptitude assessment, then an AI-based interaction, then a technical interview, and finally an HR round. The first step was online and included aptitude-style questions. After that, I did an AI chatbot session where it asked me questions tied to my resume along with some basic computer science fundamentals.
A recruiter called first and asked whether I was looking to change jobs. After my resume was shared internally, I was shortlisted and scheduled for a technical discussion. The round focused heavily on my practical Genesys Cloud experience—everything from architect-level thinking to contact center implementation details and even my migration approach.
The interview process typically begins with an online aptitude assessment followed by an AI-based interaction, a technical interview, and concludes with an HR round. The overall timeline can vary significantly, with some candidates experiencing delays in feedback and offer communication.
Technical interviews often emphasize core programming fundamentals, including data structures, algorithms, and specific language-related concepts like OOP and SQL. Candidates are generally expected to demonstrate their coding skills in real-time, often through screen sharing.
The HR round typically focuses on communication skills, career goals, and cultural fit, with questions often tied back to the candidate's resume and experiences. This round is generally perceived as less stressful compared to technical interviews.
The overall difficulty of the interviews can vary, with some candidates finding the technical rounds challenging due to in-depth questioning, while others report a more manageable experience. The emphasis is often on solidifying foundational knowledge rather than obscure details.
Candidates frequently express a desire for clearer feedback after interviews, as many report receiving generic rejection emails without specific insights on their performance. This lack of communication can lead to frustration and uncertainty.
Candidates recommend focusing on core programming concepts and being ready to discuss projects in detail, as interviewers often tie questions back to the candidate's resume. Practicing clear communication of thought processes during coding challenges is also advised.