What questions are asked in Larsen & Toubro interviews?

Larsen & Toubro interviews commonly cover DSA coding (Basic coding (arrays / strings); OOPs or domain MCQ follow-ups), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as core engineering, project sites, technical + HR. Behavioural questions check ownership, teamwork, and why Larsen & Toubro.

How many rounds are there in the Larsen & Toubro interview?

Larsen & Toubro typically has 3 stages: Online / Written Test (90–120 min), Technical Interview (30–45 min), HR (20–30 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for Larsen & Toubro interviews?

For Larsen & Toubro, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on core engineering and project sites. Use STAR for behavioural answers and ask one thoughtful question at the end.

Larsen & Toubro Interview Experience 2025–2026 — Real Candidate Stories

Larsen & Toubro interview experience

These write-ups reflect how Larsen & Toubro fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

L&T placement process in 2026 (candidate-reported) includes: 1. Online Assessment (90 minutes) - 30-50 questions covering technical concepts, aptitude, reasoning, and domain-specific knowledge. 2. Technical Interview Round 1 (60 minutes) - Technical concepts, problem-solving, coding problems, and project discussions. 3. Technical Interview Round 2 (60 minutes) - Advanced technical concepts, deep dive into projects,…

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: L&T eligibility criteria for freshers 2026 (candidate-reported) include: Degree required: B.Tech/B.E./M.Tech/MCA in Computer Science, IT, ECE, EE, Mechanical, Civil, or related engineering fields. Batch: Final year…

Fresher offers (candidate-reported) often land around -reported): Software Engineer/Analyst: ₹8-15 LPA (CTC, including base salary, bonus, and benefits). Senior E. Treat numbers as directional — confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online / Written Test	90–120 min	Aptitude + domain / basic coding
Technical Interview	30–45 min	Core subjects or IT fundamentals
HR	20–30 min	Location, shifts, motivation

Real interview experiences

Experience 1: Graduate Engineer Trainee (2025)

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

Focus stayed on problem-solving speed and clean code, not trick questions.
Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

Coding: Basic coding (arrays / strings) — approach used: clear logic over fancy algo. Interviewer cared about complexity and edge cases.
Follow-up coding: OOPs or domain MCQ follow-ups — fundamentals.
Domain discussion around core engineering and project sites — they wanted practical trade-offs, not buzzwords.
Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

Why this company / plant / BU?
Location flexibility
Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to Larsen & Toubro’s domain (core engineering).

Experience 2: Graduate Engineer Trainee (2024–2025)

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
Second technical leaned more into technical + HR and system design basics (APIs, DB choice, failure modes).
Coding warm-up: Explain a project end-to-end — ownership and clarity.

Mistakes to avoid

Jumping into code without clarifying constraints
Treating HR as a formality — Larsen & Toubro still filters on communication and intent
Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For Larsen & Toubro, consistent DSA plus a clear story on core engineering beats a perfect CGPA with weak explanation.

Questions that come up often

Coding / technical

Basic coding (arrays / strings) — typically expects clear logic over fancy algo
OOPs or domain MCQ follow-ups — typically expects fundamentals
Explain a project end-to-end — typically expects ownership and clarity
Discussion on core engineering and project sites — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why this company / plant / BU?
Location flexibility
Internship / project relevance
Long-term plans

Practical tips for Larsen & Toubro

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about core engineering in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many Larsen & Toubro panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Larsen & Toubro HR Interview Questions — common HR questions and how to answer them
Larsen & Toubro Preparation Guide — round-wise prep plan
Larsen & Toubro Coding Questions — practice problems with approaches
Larsen & Toubro Previous Year Papers — past papers and patterns
Larsen & Toubro Placement Papers — company overview, eligibility, and process

Last updated: August 2026