Academic snapshot
Marks: 70% or 7.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.Tech/B.E./M.Tech/MCA in listed branches
Backlogs: None active
Year: Final-year and recent grads (often within 2 years)
Larsen & Toubro is India’s leading engineering and construction conglomerate, founded in 1938, with businesses spanning infrastructure, heavy engineering, and technology services. It recruits fresh engineering graduates into project execution, plant operations, automation, and digital engineering roles across India.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
L&T is a multi-unit engineering hirer, not one Java paper. The printed floor on many parent-campus JDs is 7.0 throughout. The real cut is the OA mix for your business unit, then whether you can talk a project or a site without a script.
This hub is Larsen & Toubro (larsentoubro.com). LTTS is the ER&D subsidiary. LTFS is financial services. LTIMindtree (legacy LTI) is a separate IT services brand. A February 2025 GFG GET note still used LTI branding. Read the legal name before you grind the wrong % floor.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus / pool | PPT, unit headcount (ECC vs IT vs LTFS) | Aptitude + domain bar |
| Careers portal | Form + wait | Follow duration on the mail |
| Referral | Visibility | You still sit every elimination |
Off-campus does not mean easier quantitative. It often means more applicants who prepared the wrong unit.
Is 7.0 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. A 7.1 who finishes the 90-minute mix and explains a transformer or a REST API beats an 8.9 who only grinded graphs for a civil seat. A 7.8 with 68% in 12th still dies if the JD says throughout.
LTTS / LTFS floors: Can print 60% / 6.5-ish instead of 7.0. Do not copy this hub’s 7.0 onto an LTTS form, or vice versa.
Gaps and backlogs: No active backlogs. Max about 2 years gap on many tables. Full-time only.
What helps the resume screen: One project or internship with a number (cost saved, defects, load). See certifications after OA and branch notes, not instead of them.
Academic snapshot
Marks: 70% or 7.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.Tech/B.E./M.Tech/MCA in listed branches
Backlogs: None active
Year: Final-year and recent grads (often within 2 years)
Skills they actually filter
Written: Aptitude + technical/domain + coding when named
IT track: DSA, OOP, SQL, one language
Core track: Machines, RCC, thermo, as listed
HR: City, Why L&T, unit name
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 70% or 7.0 | Mailer / unit wins |
| 10th & 12th | Same throughout rule | Keep scans |
| Branches | CS/IT/ECE/EE/Mech/Civil related | Confirm drive |
| Backlogs | None live | Clear before joining |
| Gap | ≤ ~2 years | Explain a skills year |
Good fit: You like large physical or plant systems (or IT that serves them), you will relocate, and you can sit a mixed aptitude paper without treating it as optional.
Harder path: You only practised LeetCode hards and skipped percentages; you refuse site/project cities; you applied to LTTS and L&T with the same “Why” paragraph.
Branch myth: A CS degree does not skip domain MCQs on a mixed OA. A civil degree does not block you if the GET notice lists civil. The paper cares about the track on the form.
Download 2026 L&T placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
L&T does not publish one permanent official paper set. Papers on this site are pattern trainers for aptitude, core technical, and coding/logic. L&T and LTTS campus-style sets share practice DNA here; your live mix still follows the unit.
| Branch / intent | What to practice |
|---|---|
| IT & software / analyst | Aptitude, coding, CS fundamentals (coding questions) |
| Electrical GET | Aptitude + circuits, machines, power systems |
| Civil GET | Aptitude + strength, RCC, surveying basics |
| LTFS / finance-IT | Short aptitude/domain MCQ + two coding (2025 note) |
| Last year / PYQ PDF | Year cards below + aptitude |
Candidate reports vary by business unit (ECC, LTTS, LTFS, and others). The downloads are free PDF-style practice with solutions, not official leaked papers.
| Theme you saw | Drill next | Why L&T asks it |
|---|---|---|
| Percentages / time-work | P&L, pipes, DI | Every OA |
| Programming MCQ | OOP, complexity | IT technical |
| Two coding | Arrays/strings complete | LTFS 2025 |
| Machines / RCC | GATE-lite PYQ | Core GET |
| SQL vs NoSQL | 3NF, indexes | LTFS tech note |
L&T hires freshers through campus cells, larsentoubro.com careers, and referrals. After eligibility, the shape is services-plus-engineering: mixed OA, one or two technicals, HR. Unit name changes the second hour.
Campus recruitment
Through college placement cells. Batch OA, then interviews. Note the unit headcount.
Careers portal
Apply on larsentoubro.com for GET and technology roles. Follow the invite.
Referrals
Employee referrals improve screen odds. You still sit the paper.
Degree, 7.0 / 70% throughout when printed, backlogs, year of passing. Projects with numbers help when volumes are high. Gate, not the hard filter.
Student-reported working map for many software/GET papers:
| Section (typical) | Questions (reported) | Time feel | Focus |
|---|---|---|---|
| Technical | 15-20 | 35-40 min | Programming, DSA, engineering MCQ |
| Aptitude & reasoning | 10-15 | 25-30 min | Quant, logical, DI |
| Domain | 5-10 | 15-20 min | Automation, construction, methods |
| Problem-solving | 2-5 | 10-15 min | Coding or applied problems |
Format: online proctored on an L&T or partner platform. Usually no negative marking in older explainers. Your invite wins.
LTFS 2025 variant: 30 MCQs in 30 minutes, then two coding in 30 minutes. Train that clock if the PPT named EduTech / LTFS.
Pass habit: easy quant first, then technical MCQ, coding last if it is a short block. Do not burn 20 minutes on one seating puzzle. Funnel rumours: 30-40% written pass; LTFS 2025 was 21 after OA from that campus pool.
IT: language, DSA, OOP, SQL, internship. Core: machines, RCC, thermo, a site story. LTI 2025: kind 40-45 minutes, palindrome/Fibonacci, ML basics, internship.
Pass habit: think aloud. A correct Fibonacci with edge cases beats a silent graph you cannot finish.
Deeper project, system design lite, domain. Not every GET drive has two technicals. LTFS 2025 mixed a second tech with HR (hackathon projects, inheritance, 3NF, MySQL vs MongoDB, Autogen/AI, then a “critical issue before office hours” situational).
Pass habit: know the stack you wrote on the resume. Do not invent Mongo if the project was MySQL.
Why L&T, city (Mumbai / Bengaluru / Chennai / site), joining, integrity, sometimes a service-location yes/no. Know the ₹8-15 LPA software/analyst band as a public report, then read the letter. LTI 2025 asked relocation after a short technical.
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / screen | 1-2 days campus; longer off-campus | Unit tagged here |
| OA | 1 day | Same-week shortlist common |
| Technical 1 | 3-5 days | Virtual or campus |
| Technical 2 | 3-5 days | Software loops |
| HR | 2-3 days | Sometimes same day |
| Offer | 2-3 days | Written letter wins |
| End to end | ~2-3 weeks campus often | LTI 2025: apply 20 Feb → HR 26 Mar |
Log every mock: which of the five ate the clock. That log is the prep plan.
If the PPT is buildings, plants, or infra: expect more domain and core MCQ, less LeetCode. Interviewers ask a site or intern story, a safety or quality incident, and whether you will go where the project is. Bring one drawing or calculation you can redo on a whiteboard. A React portfolio is optional colour, not the syllabus.
If the role name says automation, digital, or Industry 4.0: PLC/SCADA vocabulary, a sensors project, basic Python or C, and still the same aptitude clock. Do not skip percentages because the poster had a robot on it.
Campus: PPT → OA same or next day → technicals over 1-2 weeks → HR. Pool drives feel denser. Off-campus: more resume noise, same paper. Screenshot the invite. If the PPT never mentioned a second technical, do not panic-build system design. If it did, prepare the project for a harder follow-up.
Pick the three items you guessed. Rewrite the method. Speak one formula or one code fix to a wall. That is the whole review. Re-scoring 40 questions you already got right is how people stay slow on DI.
Saturday 10:00: 90-minute mixed OA (or 30+30).
Saturday 12:30: rewrite the three misses.
Saturday 16:00: one complete coding or 20 core MCQs.
Sunday 11:00: project + second-technical questions with a friend.
Sunday 12:00: HR including city and Why L&T (name the unit).
Two weekends of that beat twelve nights of random “L&T dumps.”
If the form says Larsen & Toubro and GET/analyst, stay on this hub. If it says L&T Technology Services, use LTTS (ER&D, often a different CGPA print). If it says LTFS / L&T Finance, expect a short coding block plus finance-IT talk (2025 GFG). If it says LTI / LTIMindtree, treat it as IT services, not an ECC site GET. Quoting the wrong letter in HR is a sloppy tell.
10th, 12th, all semesters, ID, photo if asked, resume one page with a metric. Throughout 70% means the 12th PDF matters. Name and dates must match the form.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
Week calendars live on the preparation guide. This H2 is the focus split.
| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed aptitude | ~35% | One 90-min mix at cutoff pace |
| Branch technical or DSA | ~30% | MCQ set or two complete codes |
| Domain / coding block | ~20% | LTFS 30+30 or domain pack |
| Project + HR | ~15% | Unit name, city, one metric |
If you already clear aptitude and fail coding, invert 35/30 for two weeks. If you code fine and fail percentages, stop hiding in LeetCode.
Week A: daily 45-minute aptitude; one coding or core block.
Week B: one full 90-minute mock; project viva; HR city; sleep.
You want engineering delivery at India infrastructure or plant scale (or IT that sits on that stack). You will relocate. You know the unit on the form. You will read the letter. That is enough. “Passionate about leveraging synergies in nation building” is how people sound like a template.
Electrical: DC/AC machines, transformers, power systems (faults, load flow lite), measurements, basic power electronics. One GATE-lite set a day beats a random YouTube playlist.
Civil: Strength of materials, RCC (limit state basics), steel connections lite, surveying, soil basics, estimating. Site photographs on your phone are not a substitute for a bending-moment sketch.
Mechanical: Thermo, SOM, manufacturing, theory of machines, a shop-floor or intern story. Do not open CFD the week of a GET OA.
IT / analyst: Arrays, strings, hashing, OOP four pillars, SQL joins, one project metric. Palindrome/Fibonacci showed up on an LTI 2025 technical. Finish easies.
Construction technology, automation, manufacturing systems, and project-management one-liners appear on mixed papers. You do not need a PMP. You need “what is a Gantt chart / what is a PLC / what is a BOQ” at MCQ depth. If the PPT never mentioned construction, do not binge RCC the night before an LTFS coding block.
GET letters often mean travel or a project site, not only Powai or Bengaluru. Ask HR the joining location. If you cannot do sites, say so before you celebrate a shortlist. “I will only do remote product” is a bad L&T GET answer. “I can do the named city and I understand project travel” is the honest one.
After each mock, three lines: section that ate time, one MCQ type to drill, one coding miss or one core formula. Review that log the night before. Re-reading a 200-page dump is how people feel busy and still miss time-and-work.
Share aptitude. Change the second hour: NQT verbal vs L&T domain vs LTTS embedded. Compare city, bond language if any, and whether you want a site GET or an IT seat. Do not reuse one “Why” paragraph.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on unit, city (Mumbai, Bengaluru, Chennai, sites), and written components.
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software engineer / analyst | ₹8-15 LPA | Primary IT-flavoured campus band |
| Automation / design engineer | ₹8-16 LPA | Engineering background |
| Project engineer (GET) | ₹7-14 LPA | Site/project flavour |
| Senior engineer (2-3 YOE) | ₹12-22 LPA | Not campus default |
| Lead (indicative) | ₹22-35 LPA | Experience |
Confirm base vs bonus on the written offer. Do not treat blog midpoints as guarantees. LTTS letters live on the LTTS hub.
Health cover, PF/gratuity, training, transport or site allowances, occasional hybrid language on technology teams. Ask HR about joining location and travel. Do not assume a Bengaluru product campus if the letter says a project site.
Know ₹8-15 LPA as the commonly cited software/analyst range and that GET letters can sit lower. One calm question beats a FAANG demand. Do not quote an LTTS package on an ECC form.
Mumbai / Navi Mumbai, Bengaluru, Chennai, Hyderabad, and project sites all appear. The same CTC band can feel different after HRA and travel. Ask joining location before you compare two letters. A ₹9 LPA site GET with housing language is not the same job as a ₹12 LPA Bengaluru analyst seat.
Some letters split base and performance bonus. Know that before HR. One question is enough. Do not demand a 20 LPA product split on a GET form.
Net for 2026: L&T is still an engineering group with IT seats, not TCS NQT and not a FAANG OA. Read the unit. Time the mix. Know the city.
Yes. Start with the 2026 PDF or the archive. IT, electrical, and civil flavours sit in the year packs.
Typical path: OA (~90 min) → technical 1 → technical 2 (many software loops) → HR. About 2-3 weeks on campus. LTFS and LTI notes are shorter after OA. Details: online assessment.
Often 4 (OA + two tech + HR). Some GET notes are OA + one tech + HR. LTFS 2025: OA, tech, combined tech+HR. Count the PPT.
Student-reported 90 minutes, 30-50 items, usually no negative marking: technical, aptitude, domain, short coding. LTFS 2025 was 30 MCQ + 2 coding in 60 minutes total.
Commonly 70% or 7.0 throughout; listed engineering degrees; no live backlogs; gap ≤ ~2 years. LTTS/LTFS may print a different floor. Your notice wins.
It matches the commonly reported floor. OA still decides. Do not copy 7.0 onto an LTTS form that says 6.5.
Yes on many GET drives. Practise aptitude plus core technical, not only Java.
Candidate-reported software/analyst CTC often ₹8-15 LPA (August 2026). GET/project bands vary. The written offer is the only number that matters.
Roughly 35% aptitude, 30% branch/DSA, 20% domain/coding, 15% project/HR. Guide: preparation guide.
C, C++, Java, or Python when coding is named. Core GET still lives in branch subjects.
No. Parent campus vs ER&D subsidiary vs IT services brand. LTFS is finance. Read the form. LTTS papers: LTTS hub.
L&T is engineering-construction with IT seats and a higher commonly cited starting band than many Ninja/SEP letters. TCS/Infosys are mass IT services. Share aptitude; add L&T domain and unit literacy.
Train the mix on your invite (90-minute mixed vs 30+30). Name the unit in HR. Finish one easy coding fully. Keep 12th scans.
L&T interview experience plus the GFG LTI and LTFS notes below.
Often yes: Mumbai, Bengaluru, Chennai, or a project site. Answer a city, not remote-only, unless the posting says so.
Drive-specific. Some GET/IT letters mention a service period or training recovery clause; many campus notes do not. Ask for the clause in the offer PDF. Decide yes/no before HR, the same way you decide city.
30 aptitude/domain MCQs in 30 minutes, then two coding problems in 30 minutes. 21 advanced; 6 selected after interviews. Train that 30+30 clock if your PPT names LTFS or EduTech.
Applied 20 February 2025. Technical on 15 March, HR on 26 March, after an online assessment. ~40-45 minute kind technical: internship, ML basics, palindrome/Fibonacci, then relocation questions. Source: GeeksforGeeks LTI GET.
Takeaway: useful for L&T Infotech / LTIMindtree timelines. Not an ECC site paper. Still a real GET loop with a short coding warm-up.
L&T EduTech OA: 30 aptitude/domain MCQs (30 min) plus two coding (30 min). 21 advanced. Tech: hackathon projects, OOP inheritance, 3NF, MySQL vs MongoDB, Autogen/AI. Combined tech+HR: situational “critical issue before office hours” plus backend self-rating. “Out of the 21 candidates shortlisted after the OA, only 6 were selected after the interview rounds.” Source: GeeksforGeeks LTFS 2025.
Takeaway: a 30-minute coding block is a real cut. SQL and honesty about your backend rating matter. 21 → 6 is the interview filter, not the MCQ paper.
What helped: timed mixed OA; one complete easy code; project metric; unit name in Why L&T; city answer ready.
What hurt: LTTS dumps on an ECC form; silent second technical; quoting 15 LPA on a lower GET letter; missing 12th scans; treating LTFS as “just aptitude.”
2024 notes: mixed online OA, more domain and practical problem-solving than a pure verbal paper, coding showing up on IT tracks.
2025 notes: same 90-minute spine on many campuses; LTFS split 30+30; LTI kinder technical; SQL/OOP still asked.
2026 expectation: same mix until your invite says otherwise. AI/ML one-liners may appear on digital roles; they do not replace aptitude.
Laptop if remote OA; college ID; 10th/12th on the phone. Pool days are noisy. Sit where you can see the timer. Do not start a new coding language in the waiting room.
A project team, a drawing or a ticket, a site or an office desk. “I will only do GenAI research” is a bad HR answer. “I will learn the unit’s stack and I already sit a 90-minute mix” is the GET answer.
More narratives: L&T interview experience.
LTTS · TCS · Infosys · Wipro · BHEL · Reliance
Last updated: August 2026.