Urgent.News

What's breaking now, across thousands of outlets.

Tech

My LTIMindtree Interview Experience (2026 Batch) | GET Role

Last year, I went through the campus placement process for LTIMindtree for the Graduate Engineer Trainee (GET) role (4.05 LPA). Since many students are preparing for upcoming drives, I want to share exactly what the process looked like, from the online test to the interview questions. 1. Timeline and Eligibility The process moved quickly. To be eligible, we needed at least 60% in 10th, 12th, and…

Last year, I underwent the campus recruitment process for LTIMindtree's Graduate Engineer Trainee (GET) position with a starting salary of 4.05 LPA. Given that numerous students will be preparing for similar drives, I would like to share an account of the entire process, from the online assessment to the interviews.

The timeline for the process was quite swift. To be eligible, candidates needed to have at least 60% in their 10th, 12th, and college exams, have no active backlogs, and a maximum 2-year gap in their education. Registration for the process opened on September 16, 2025, with the online test scheduled for September 20, 2025. The technical interview took place on October 5, 2025, followed by the HR interview on October 8, 2025. The final results were announced on November 10, 2025.

The first round of the process was an online assessment conducted on the SHL platform. The test lasted for 110 minutes and was taken using a lockdown browser, which prevented candidates from accessing other tabs or applications. The AI monitored the candidate's webcam and microphone throughout the test. The test comprised three sections: Aptitude, which included Logical, Quantitative, and Analytical questions; Technical, focusing on basic computer programming and computer science concepts; and Verbal, assessing English comprehension and spoken English skills.

Following the successful completion of the online test, I moved on to the technical interview, which was held virtually on October 5. Even though the role was general, the interviewers placed significant emphasis on the projects listed on my resume.

The interview began with a brief introduction and an overview of my projects and portfolio. I chose to elaborate on my Course Marketplace project during the interview. Subsequently, I was asked to explain a specific technical challenge I encountered during the development of this project and how I addressed it. I was then prompted to describe the project's data flow and system architecture, as well as the technologies I used for the frontend.

I was also questioned on user file storage, security measures implemented in the application, and the database schema and tables utilized in the project. Furthermore, I had to explain the relationship between courses and students in the database and discuss potential strategies to scale the application architecture to accommodate a significant increase in users.

Following the technical interview, I proceeded to the HR round on October 8. The interview primarily focused on assessing my communication skills and fit with the company. The interviewer asked about my greatest strengths and weaknesses, a situation where I had to resolve a conflict within a team, my preferred work location, and my willingness to work in afternoon or evening shifts.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

My friend was lost in the internship hunt, so I built him Get A Job.

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend What I Built I wanted to build something a friend could actually use beyond this weekend.

  • "Get A Job" simplifies internship search and applications
  • Open-source AI tool consolidates internship discovery and application process
  • Local AI processing ensures data privacy and flexibility

OpenSearch Under the Hood: How It Actually Works

I have been using OpenSearch for querying and aggregating data at work. Initially, I was just maintaining the code, but after working with it for some time, I started wondering what actually happens…

  • OpenSearch organizes data across a cluster of nodes, each containing multiple shards.
  • Indexes are logical groupings of related documents, similar to tables.
  • Queries are distributed across relevant shards, with results merged by a coordinating node.

Is Manual Testing Dead in 2026, or More Valuable Than Ever?

You've heard the prediction every year for a decade: automation is about to kill manual testing. In 2026, with AI writing test suites on demand and generating code faster than humans can review it…

  • Manual testing's tedious parts automated, leaving critical bug uncovering
  • Mechanical regression testing dies, replaced by AI-generated suites
  • Exploratory testing thrives, humans form hypotheses to find critical bugs

More from Sunday 4 October →