Real, anonymous reports from people who interviewed for Software Engineer at L&T Technology Services, newest first and distilled into what to expect across the loop.
My process started with recruiter screening and then moved into a structured sequence of technical rounds. After the initial call, I had two back-to-back technical interviews where the questions leaned heavily into my C/Linux/networking/WiFi background. The focus wasn’t just surface-level recall; I was expected to explain concepts clearly and connect them to what I had listed on my resume. One of the rounds also pulled in a strong electronics/core-theory flavor (circuits, signals, and communication), plus basic programming-style logic checks and deeper discussion of my projects.
My interview journey ran in a clear four-to-five step flow. It began with a resume-related stage and then progressed through a technical evaluation that mixed concept design with practical checks. After that came a more traditional technical round connected to my field, where I had to go beyond buzzwords and walk through my thinking.
The interview process typically follows a structured flow starting with an online assessment, followed by technical interviews, and concluding with an HR round. Candidates noted a clear progression through aptitude, technical evaluations, and behavioral discussions, often within a couple of weeks.
Candidates faced a variety of technical assessments that included coding challenges, questions on programming fundamentals (C, Java), and domain-specific knowledge, particularly around electronics and systems. The technical rounds emphasized clarity in explanations and connections to prior experience.
The HR rounds were generally conversational, focusing on cultural fit, motivation, and logistical discussions such as salary expectations. Candidates found these sessions to be less intense than technical rounds, often aimed at confirming alignment with the company's values.
Interviewers often referenced candidates' resumes, probing into past projects and experiences to assess depth of understanding and problem-solving abilities. Candidates were encouraged to clearly articulate their contributions and the challenges faced in their projects.
Overall, candidates described the difficulty of the interviews as average, with a focus on foundational knowledge rather than overly complex scenarios. However, the pace and breadth of questions could be demanding, requiring effective time management.
Candidates reported varying experiences with communication and professionalism throughout the process, with some noting delays and lack of follow-up from HR. Clear communication from the outset was appreciated, but inconsistencies in scheduling and feedback were highlighted as areas for improvement.