Skip to content

How to Prepare for L&T

L&T hiring spans construction, engineering, and tech arms. Confirm whether you are in LTTS-style software or core engineering - prep differs completely.

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
  1. One timed block that matches Larsen & Toubro’s first round (aptitude + domain)
  2. Log misses: topic + why you failed (speed, concept, carelessness)
  3. Re-solve yesterday’s misses cold
  4. 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

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.

Common mistakes for Larsen & Toubro aspirants

Section titled “Common mistakes for Larsen & Toubro aspirants”
  1. Generic software prep for a core engineering posting - fix this first
  2. Preparing only interviews while failing Larsen & Toubro’s first round
  3. Collecting notes without timed mocks
  4. Listing five frameworks on the resume and defending none
  5. Changing language/stack one week before the drive
  6. 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.