L&T hiring spans construction, engineering, and tech arms. Confirm whether you are in LTTS-style software or core engineering - prep differs completely.
What actually rejects people
Generic software prep for a core engineering posting.
First round: L&T aptitude + technical interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
Aptitude 35%
Domain/tech 35%
Coding 20%
HR 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA
timed
Aptitude/tech
Interviews
varies
Domain + HR
Core Technical Skills (40% time) - Focus on programming, data structures, algorithms, and engineering concepts relevant to L&T’s domains
Technical Knowledge (30%) - Review domain-specific concepts (automation, construction technology, software development, manufacturing systems)
Aptitude & Reasoning (20%) - Practice quantitative aptitude, logical reasoning, and data interpretation daily
Interview Prep (10%) - Prepare for technical interviews with coding practice, project explanations, and HR interview preparation
One timed block that matches Larsen & Toubro’s first round (aptitude + domain)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
Aptitude
Timed accuracy
3-4
Domain / branch subjects
JD topics covered
5-6
Coding if required + projects
Role-matched mock
7-8
Interviews
Clear domain answers
Confirm software vs core track from the JD - prep differs
Aptitude is usually non-negotiable for campus drives
Answer from your branch fundamentals first
Only add coding depth if the role is software-leaning
Why Larsen & Toubro, unit preference, relocation, long-term fit
Aptitude
Core subject depth OR coding depending on unit
Aptitude
Domain fundamentals for the unit
Communication
Unit-specific technical depth
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Generic software prep for a core engineering posting - fix this first
Preparing only interviews while failing Larsen & Toubro’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
One prep plan for every business unit
Reliance · Adani · BHEL · TCS · Infosys · Wipro
Next step: Run one timed mock this week that matches Larsen & Toubro’s first round (aptitude + domain), then build the weeks around your weakest section - not around what is most fun to study.