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.
Get your personalized L&T Technology Services Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My journey started with tests and interview rounds that felt a little more complicated than the “just basics” track. First there was an online/written step, and once I cleared that, I moved into technical interviews that went deep on what I listed—especially core fundamentals and how those ideas worked in real scenarios. I remember having to walk through topics that sounded very specific, like system-level concepts and embedded-style hardware blocks, plus parts of C programming such as storage classes and how the compiling process works.
The difficulty felt like it hovered around moderate-to-hard depending on the topic. In one phase, I got questions that combined electronics or control concepts (things like ECU/MCU, H-bridge style ideas, and Freewheeling diode-related fundamentals) with basic theory that could easily derail you if you weren’t fluent. I also had to tie it back to my final-year project and explain my own contributions clearly, not just recite definitions.
> 1 year
Easy Neutral New Delhi
I went through a pretty streamlined process. It started with a short recruiter-style introduction, then I had a technical screen where the conversation stayed close to my resume and fundamentals. The technical flow felt friendly and fast—often framed as basics moving toward slightly deeper questions—so I ended up talking through my project and my role, plus how things like validation, testing, and design thinking worked.
Across the technical part, I got asked a mix that leaned theoretical and practical. Depending on how the discussion went, I covered things like programming fundamentals and OOP, and deeper topics like algorithms, cost functions, and gradient descent. I was also pulled into domain-adjacent specifics (for example electronics concepts and embedded-style ideas like drivers or microcontroller-related terms, plus how I approached compilation or related mechanics when that came up). The interview structure mostly felt like 1:1 rounds, with clear time expectations (around half an hour to under an hour total per stage), and the later part included either a video-style round or a separate HR discussion.
> 1 year
Average Positive Bengaluru
My interview process had a broader scope than I expected. After the initial screening, I moved into two technical-focused rounds where the discussion …
> 1 year
Easy Positive India
My process kicked off with a group discussion, then moved quickly into a technical round. The questions were mostly geared toward fundamentals for a f…
> 1 year
Average Neutral Bengaluru
I went through a technical-first interview that focused heavily on the exact hardware and programming themes I had mentioned. The questions touched sy…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with an online assessment followed by technical interviews and an HR round, often taking place over a single day for campus recruits, but can stretch over weeks with delays in communication and scheduling.
TimelineStructureCampus recruitment
Technical Interview Focus
Candidates can expect a strong emphasis on core technical fundamentals, including programming concepts, system-level knowledge, and practical applications related to their projects, often requiring them to connect theory to real-world scenarios.
The HR discussions tend to be straightforward, focusing on fit, expectations, and salary, and often serve as a final confirmation step rather than a rigorous evaluation, though the number of HR rounds can vary significantly.
HR discussionBehavioralFit assessment
Communication & Responsiveness
Candidates frequently report issues with communication during the process, including delays in updates and scheduling, which can lead to frustration and uncertainty about their application status.
CommunicationResponsivenessCandidate experience
Difficulty Level & Expectations
The difficulty of technical questions ranges from moderate to hard, with a focus on ensuring candidates truly understand their stated skills and concepts rather than just recalling definitions or surface-level knowledge.
DifficultyUnderstandingConceptual knowledge
Project Relevance
Candidates are often asked to discuss their previous projects in detail, requiring them to articulate their contributions and the technologies used, which helps interviewers gauge practical experience and relevance to the role.