Academic snapshot
Floor: Often 60% / 6.5-6.75
Degrees: B.E./B.Tech (M.Tech some posts)
Backlogs: None active
Year: Final year / GET batch
LTTS Placement Papers 2026
L&T Technology Services provides engineering research and development services across transportation, plant engineering, medical devices, and industrial software for global clients. Founded in 2012 as an L&T Group company, it hires engineers for embedded systems, mechanical design, and digital product development roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
LTTS fresher eligibility for campus drives
LTTS does not publish one universal CGPA cutoff for every India fresher drive. Campus JDs, GET off-campus posts, and software vs core tracks differ. Treat numbers below as candidate-reported (as of August 2026).
Who this hub is for
- For: Students targeting Graduate Engineer Trainee / Associate Engineer / campus software-ER&D roles at L&T Technology Services - Bengaluru, Mysuru, Chennai, Vadodara, Pune, and other listed cities.
- Not the same company: LTFS (L&T Financial Services) runs a different GET/digitization process. L&T parent construction/heavy-engineering drives use different papers and branch lists. If your notice says “L&T Technology Services” or “LTTS,” stay on this hub.
- Experienced hires: Deeper domain (automotive, medical, plant, embedded). Use fresher sections as a base, not a senior loop map.
Software campus vs core get
Campus CSE/ECE drives often look like a service-plus-product mix: CoCubes-style aptitude, two coding problems, then a 30-minute CS viva. Core GET notices (Mechanical, EE, Mechatronics, Metallurgical) can be domain-first: thermodynamics, circuits, materials, drawing - coding may be light or absent. A 2026 off-campus GET post listed ~₹4.0 LPA, classroom training stipend, and a service bond. Do not assume the software campus CTC applies to that GET letter, or vice versa.
If your branch is CSE, you still need aptitude accuracy. LTTS is not a LeetCode-hard product OA. Students who only grind graphs and skip sectional quant get surprised. If your branch is Mechanical, do not skip C basics if the notice mentions a coding section - some mixed drives still include it.
Internship vs FTE: one GFG on-campus select reported a 1-year internship for six students after the same three-round ladder. Read the PPT and offer for intern vs GET vs FTE. The technical bar can look identical; the letter is not.
What “engineering R&D services” means on a Monday: you are usually staffed on a client program (OEM automotive, industrial plant, medical device, telecom) rather than a single consumer app. That is why HR cares about relocation and why technical panels mix branch subjects with C/SQL. A “I only want pure product DSA” story is a mismatch; a “I can debug an embedded module and explain a 3NF table” story is the fit. If you want FAANG-style LeetCode-only loops, LTTS is the wrong target. If you want to ship engineering work for real hardware/software programs with a structured GET year, it is a common on-campus path.
Bond reading homework (do this before HR, not after): find the duration, the amount, what counts as a break, and whether training months count. Ask whether the letter is intern, GET, or FTE. Write three numbers on a card: CTC or stipend, city, bond months. If you cannot say those three out loud, you are not ready for HR. Telegram screenshots are not the letter.
Degree, projects, and “is 6.5 enough?”
6.5-6.75 / 60% meets many listed floors. It is not a selection guarantee. A 6.6 who finishes both coding problems and can explain polymorphism beats a 8.4 who blanks sectional quant and cannot narrate their project.
Projects that help: any embedded/C demo, a small automation or CAD-linked tool, a DBMS mini-project you can draw, a plant/auto/medical domain internships. A certificate pile with zero “what I built” talk dies in the 30-minute technical.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA (CoCubes or similar), reserved seats | Aptitude + viva bar |
| Off-campus GET | Portal (Superset-style) shortlist; some skip written | Relocation + bond talk |
| Referral | Visibility | Interviews stay real |
Off-campus does not mean easier engineering questions. It often means more applicants and a clearer bond conversation.
Documents and portal hygiene
- Keep CGPA consistent with 10th / 12th / degree forms.
- Screenshot invite: CoCubes vs other OA, section count, coding languages.
- If you listed ML / C++ / SQL on the resume, you will be asked - one GFG loop did exactly that.
- Mysuru / Vadodara / Chennai relocation is a real filter; be ready to say yes or no.
- Clear active backlogs before offer paperwork.
- First-attempt final exams show up on some GET notices.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | ~60% or 6.5-6.75 throughout | Some campus cells pre-filter higher |
| Degree | B.E./B.Tech; M.Tech on some posts | Full-time only |
| Branch | CSE, ECE, EEE, Mechanical, Mechatronics, Metallurgical | Read the notice |
| Year | Final year + recent grads | GET posts name the batch |
| Backlogs | No active backlogs | Hard filter on many JDs |
| Languages | C, C++, Java, Python | C/C++ for embedded |
| Location | Multi-city India | Client-site possible |
Skills & focus
Primary: Aptitude + easy-medium coding
Secondary: Branch / CS viva
First filter: Timed OA (when present)
Differentiator: Domain + relocation honesty
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| Below 6.5 | Often filtered on-campus | Off-campus only if JD allows |
| 6.5-7.0 | Meets many listed floors | Need strong OA + viva |
| 7.0-8.0 | Common shortlisted chatter | Aptitude still decides |
| 8.0+ | Strong academically | HR still tests location/bond |
LTTS placement papers - last few years
Download 2026 LTTS placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What LTTS previous year papers actually train
LTTS does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers - not leaked live CoCubes tests.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Sectional aptitude + 1-2 easy-medium coding |
| Technical | OOPs, DBMS, OS, C/C++, branch subjects, projects |
| HR | Location, bond, Why LTTS, 5-year plan |
Themes that keep repeating (2024-2026)
- 2024 cycles: Three-round campus loops. One GFG write-up: 90 questions (30 logical, 30 quantitative, 30 domain) plus 2 coding; 57 students advanced to interview. Technical was resume + OOPs + SQL + C++. HR asked 5-year plan and location preference.
- 2025 loops: An on-campus GFG select (full process online) reported CoCubes, three sections, last section two coding problems (merge two sorted linked lists; a searching problem). Technical ~30 min: OOPs (polymorphism, overloading vs overriding), normalization, functional dependency, resume ML, basic C++, array sort complexity. HR ~20 min: hobbies, hometown, 5-year plan. Result in ~2 days; 6 internship selects.
- 2026 prep expectation: Keep sectional aptitude stamina and two clean coding submissions. Core GET notices still list 60% / 6.75, no backlogs, and a bond. Treat PDFs as pattern catalogs. Confirm whether your drive is software-campus or core-GET.
How to use one paper set in a single sitting
- Timed: 60-90 minutes matching your invite (sectional if the mock supports it).
- Untimed review: rewrite the cleaner coding solution; list three aptitude topics you guessed.
- Map each miss to a theme and pull cousins from coding questions or aptitude.
- 15 minutes: explain overloading vs overriding or normalization out loud.
- Log one STAR story (team lab, internship bug, unclear lab spec).
Related problems to practice
| Theme you saw | What to drill next | Why LTTS asks it |
|---|---|---|
| Merge two sorted lists | Linked-list basics | Reported CoCubes coding |
| Searching / arrays | Binary search + edges | Reported searching problem |
| Quant / time-work | Sectional speed | 30-Q quant blocks |
| Logical puzzles | Accuracy under skip rules | 30-Q logical blocks |
| Domain MCQs | Branch 2nd/3rd year core | 30-Q domain blocks |
| OOPs / SQL | Viva cards | Technical 30 min |
2025 sets often drill “merge two sorted lists.” Own the two-pointer list template, then drill a related problem (merge k lists mentally, not on the OA). That transfers; memorising Q1 text does not.
Free practice packs. Full archive: previous year question papers.
From application to offer at LTTS
LTTS hires freshers through campus cells, ltts.com careers, and referrals. After eligibility screen, the common shape is ER&D services: timed OA (when used), one technical, HR.
Application methods
Campus recruitment
Eligibility list → CoCubes/OA → technical → HR. One GFG select finished this fully online and got a 1-year internship.
Online applications
ltts.com careers / GET posts (sometimes Superset). Follow the invite for platform and bond PDF.
Referrals
Better resume visibility. You still need passing OA or a solid domain viva.
1. Resume / eligibility screen
~60% or 6.5-6.75, no active backlogs, listed branches. Projects with C/C++/SQL/embedded help. This is a gate - OA or the portal shortlist is the filter. A referral does not skip CoCubes when the campus uses it.
PPT is still worth attending. Teams mention client industries (auto, aero, medical, plant), Mysuru/Vadodara culture, and training. Skipping it is how people walk into HR with zero company sentence and mix up LTTS with LTFS.
2. Online Assessment
A campus GFG report described:
| Item | Reported detail |
|---|---|
| Platform | CoCubes (that drive) |
| Shape | 3 sections; last section coding |
| Coding | Merge two sorted linked lists; searching problem |
| Other campus report | 90 Q (30 logical / 30 quant / 30 domain) + 2 coding |
Your invite may differ. Languages: C, C++, Java, Python typically.
Pass bar: Sectional accuracy plus two compiling, passing coding solutions beats one clever incomplete graph attempt.
Student tip: Skim coding first if it is last. Bank both coding problems. Do not die on a hard domain MCQ at minute 5 while linked-list merge is unsubmitted.
CoCubes / sectional tactics students forget: many papers have no useful review screen. Submit a compiling linked-list merge even if you did not handle every edge; a blank coding box is a common reject. For aptitude, mark and skip DI sets that need three minutes of table grinding - LTTS is not recruiting you to be a CAT topper. Domain MCQs for CSE are often OS/DBMS/OOPs; for Mechanical they are thermo/SOM/production. Guessing every domain question because you “are a coder” is how CSE students fail a paper they thought was easy. If the invite lists negative marking, skip wild domain guesses; if it does not, use last-minute fills only after coding is in.
Example timing for a 90-question + 2-coding paper
| Block | Move |
|---|---|
| First pass | All easy quant/logical; skip time-sinks |
| Middle | Domain MCQs you actually studied |
| Last 25-35 min | Both coding problems + sample cases |
| Final 5 min | Unanswered guesses if no negative marking (confirm invite) |
Deeper notes: LTTS Online Assessment.
How reported coding maps to templates (related problems, not leaked keys):
- Merge two sorted linked lists → dummy node + two pointers; null handling.
- Searching → binary search on sorted input, or linear if unsorted; ask yourself the constraint.
- Array sort complexity (interview) → know n log n vs n² and when each is fine.
That last sentence is how you still collect interview points when the OA coding was easy and the panel wants complexity talk.
3. Technical interview (~30-45 min)
Projects first, then OOPs, DBMS (normalization, functional dependency), OS if CSE, C++ basics, and one live array/sort problem. Core GET panels swap in branch subjects (thermo, circuits, materials, control). About half of OA qualifiers typically move, drive-dependent.
Worked mini-outline - overloading vs overriding:
- Overloading: same name, different signature, compile-time.
- Overriding: subclass replaces parent method, runtime.
- Give a one-line C++/Java example from your project, not a textbook Animal class you never wrote.
Core GET viva (if your notice is Mechanical/EE/Mechatronics): expect 2-3 questions from 2nd/3rd year core, then a project drawing or lab story. They are not trying to fail you on GATE-level numericals. They want to hear you name assumptions (ideal gas, steady flow, lumped circuit) and admit what you would look up. Bring one project photo or block diagram in your head: sensor → MCU → actuator, or CAD → analysis → prototype. Software-campus candidates should still keep one branch subject warm if their degree is ECE - LTTS panels mix.
How to narrate a project in 90 seconds: (1) what it did, (2) your module, (3) one bug, (4) one metric or test. “We used Arduino and it worked” is not a story. “The UART dropped bytes at 115200 until I added a checksum and halved the rate” is a story. The 2025 GFG panel asked ML only because it was on the resume - if you cannot give a metric, delete the line.
4. HR interview (~20-30 min)
Hometown, hobbies, 5-year plan, location preference, bond willingness, Why LTTS. Communication and honesty matter more than a speech about “L&T brand.” Around most tech-clear candidates get offers if they will relocate and sign what the letter says.
| # | Round | Duration (typical) | What they check |
|---|---|---|---|
| 1 | OA | 60-90 min | Aptitude + 1-2 coding |
| 2 | Technical | 30-45 min | Resume + CS/branch |
| 3 | HR | 20-30 min | Location, bond, fit |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT before or after OA |
| OA → interviews | Same day to a week | One GFG loop was fully online |
| Interview loop | 1-2 days campus | Tech + HR |
| Offer | 2+ days after HR | Written letter wins |
| End to end | ~1-3 weeks campus | Off-campus GET can stretch |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Quant sectional | Accuracy, skip rules | One 30-Q timed set |
| Logical | Puzzles without panic | One 20-min set |
| Domain | Branch 2nd/3rd year | 20 flashcards |
| 2 coding | Linked lists + search | Both from memory |
| Why LTTS | ER&D not finance | 60-second story |
Where to practise for LTTS
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.
Where your LTTS prep time should go
If a LTTS invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for LTTS sits around ₹4-4.5 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): LTTS eligibility for freshers 2026 is candidate-reported and drive-specific. Many campus and GET notices list about 60% or 6.5-6.75 CGPA across 10th, 12th, and graduation, a full-time B.E./B.Tech (sometimes M.Tech), and no active backlogs. Branch lists change: CSE/ECE/EEE plus Mechanical, Mechatronics, or Metallurgical on core GET drives. Always verify the college JD or ltts.com careers post.
What you are training for: Most campus loops report three stages: Online Test (often CoCubes or similar: aptitude + domain + 1-2 coding problems) → Technical interview (30-45 min on resume, OOPs, DBMS, C/C++, branch subjects) → HR (20-30 min on location, bond, Why LTTS). Timeline is often 1-3 weeks for campus batches; off-campus GET can skip or shorten the written test.
Short version of the prep split: Split time roughly: 35% aptitude (quant + logical under sectional timers), 30% coding (easy-medium DSA in C/C++/Java/Python), 25% branch + CS viva (OOPs, DBMS, OS, embedded/C for ECE), 10% HR (relocation, bond, Why LTTS not LTFS). Take weekly timed mocks on this site.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the LTTS previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most LTTS drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at LTTS usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why LTTS?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a LTTS-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the LTTS story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 LTTS PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed LTTS papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many LTTS papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in LTTS-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed LTTS paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why LTTS. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
LTTS compensation & benefits
Figures are candidate-reported (as of August 2026). Role family, city, intern vs GET vs FTE, and written split move the number.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| GET / many core off-campus | ₹4-4.5 LPA | One 2026 GET notice ~₹4.0 LPA + training stipend |
| Campus software / ER&D chatter | ₹5-8 LPA | Drive and role dependent |
| Internship stipends | Monthly, not CTC | One GFG campus select was internship |
Confirm base, training months, and service bond on the written offer. A circulated GET note cited about ₹2 lakh for 2 years 9 months - treat that as a report, not your letter.
Benefits students actually care about
- Health insurance
- Classroom / on-job training (GET)
- Multi-city India mobility
- Client-site exposure (auto, aero, medical, plant)
- Learning support - ask
- Bond terms - read twice
How to talk CTC in HR
Know ₹4-8 LPA depending on track, ask stipend vs CTC, and ask bond duration in writing. Do not negotiate from a blog screenshot.
What’s changed in LTTS hiring lately
- CoCubes + 2 coding is a documented campus pattern - not a guarantee for every 2026 invite.
- GET off-campus 2026 posts still list 60% / 6.75, named core branches, and a bond.
- LTTS ≠ LTFS mix-ups remain the #1 unforced error in prep groups.
- Mysuru / Vadodara joining is still a real HR filter.
- Treat ₹4 LPA GET and ₹5-8 LPA campus software as different tracks, not one promise.
- Internship vs FTE can share the same three rounds - read the PPT.
Common questions about LTTS hiring
Process & papers
What is the LTTS placement process for freshers?
Typical campus path: Online Test → Technical (30-45 min) → HR (20-30 min). One 2025 GFG campus select used CoCubes (3 sections, 2 coding), then OOPs/DBMS/C++ viva, then a calm HR. Off-campus GET may skip or shorten the written test. Campus often 1-3 weeks end to end.
How many interview rounds does LTTS usually have?
Most freshers report 3 stages counting OA. Some GET notices list only Technical + HR after a portal shortlist. Count the mailer.
Can I download LTTS placement papers PDF for free?
Yes. 2024-2026 style practice is on this site. Start with the 2026 PDF or the archive.
What does the LTTS OA look like?
One campus report: CoCubes, three sections, two coding (merge sorted lists; searching). Another: 90 MCQs (logical/quant/domain) + 2 coding. Languages usually C, C++, Java, Python. Trust your invite.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly ~60% or 6.5-6.75 CGPA across 10th, 12th, and graduation, listed branches, no active backlogs. LTTS does not publish one universal cutoff.
What is LTTS fresher salary in India?
Candidate-reported: GET / many core posts ~₹4-4.5 LPA; campus software/ER&D chatter ₹5-8 LPA (as of August 2026). Written offer wins.
Do I have to relocate?
Often yes - Mysuru, Vadodara, Chennai, Bengaluru, Pune, and other listed cities. Client-site work happens. HR will ask. Be honest.
Does LTTS have a service bond?
Many GET letters do. One 2026 note cited ~₹2 lakh for 2 years 9 months. Campus software may differ. Read the PDF; do not guess from Telegram.
Prep & LTTS-specific
How should I prepare?
35% aptitude, 30% coding, 25% branch/CS, 10% HR. Details: preparation guide.
Which programming languages are allowed?
C, C++, Java, Python typically. Embedded tracks lean C/C++. Do not switch the week of the drive.
Is LTTS the same as L&T or LTFS?
No. LTTS = Technology Services (ER&D). L&T parent = different core drives. LTFS = financial services. Different papers. Different HR answers.
Are CSE students eligible?
Yes on many campus software/ER&D drives. Some GET 2026 posts list only Mechanical/EE/Mechatronics/Metallurgical. Read the branch line.
Any pro tip that actually changes outcomes?
Do not prep the wrong L&T company. Bank aptitude + two coding ACs. Know every resume keyword. Decide relocation and bond before HR.
Where can I read real interview experiences?
LTTS interview experience and public GFG campus write-ups (CoCubes + OOPs viva). Maps, not scripts.
Is the OA always on CoCubes?
No. That is one documented campus pattern. Other years may use a different vendor. Screenshot your invite and mock that shape.
Real LTTS interview notes from candidates
On-campus - cocubes + internship select
Process: Online Test → Technical → HR; entire loop online that year. OA: CoCubes, three sections, last section two coding (merge two sorted linked lists; searching). Technical (~30 min): intro + projects; polymorphism, encapsulation; overloading vs overriding; normalization; functional dependency; resume ML; basic C++; array sort in best complexity. HR (~20 min): hobbies, hometown, 5-year plan; “very cool and calm.” Verdict: cleared all three; result in ~2 days; 6 students selected for a 1-year internship. Takeaway: easy-medium coding plus textbook CS viva, not a product-company system-design loop.
On-campus - 90 mcqs + 2 coding
OA: 90 questions (30 logical, 30 quantitative, 30 domain) and 2 coding; 57 advanced. Technical (offline): resume, OOPs, SQL, basic C++. HR: 5-year plan, location preference. Verdict: selected. Takeaway: sectional volume is the filter; interviews stay resume-shaped.
Off-campus get 2026 colour
Public GET notices for 2026 batch listed ~₹4.0 LPA, ₹25,000/month training stipend for early months, 60% or 6.75 CGPA throughout, no active backlogs, named core branches, Pan-India cities (Mysuru, Vadodara, Chennai, Bengaluru, Pune, etc.), and a service bond (₹2 lakh / 2 years 9 months in circulated notes). Some posts described Technical + HR after a portal shortlist rather than a long written paper.
What hurt other candidates: preparing LTFS digitization stories; failing sectional quant; resume ML with zero depth; refusing every non-metro city in HR; not reading the bond.
More notes: LTTS interview experience.
Sample technical follow-ups you should rehearse
- Overloading vs overriding in one minute with your class.
- What is 3NF trying to prevent? Give a bad table.
- Merge two sorted linked lists on a whiteboard.
- Time complexity of the sort you would use for 10⁴ vs 10⁸ n.
- Pointer vs reference in C++.
- Why LTTS and not L&T construction or LTFS.
- Will you join Mysuru / Vadodara if that is the letter?
Answer out loud. The 30-minute technical is mostly this list plus your project.
Offer-stage discipline
If you clear HR:
- Read bond duration and amount
- Confirm intern vs GET vs FTE
- Confirm city vs exams
- Confirm stipend months vs CTC
- Do not resign until the written letter lands
- Background verification expects consistent CGPA
ER&D services still run batch HR. Keep the thread.
One more mock template
| Block | Action |
|---|---|
| 0-10 min | Easy quant/logical sweep |
| 10-35 min | Remaining aptitude; skip sinks |
| 35-55 min | Domain MCQs you know |
| 55-85 min | Coding 1 + coding 2 |
| 85-90 min | Edges + unanswered policy |
Run this on a weekend, then explain normalization from a blank page the same evening.
Why “famous L&T brand” fails
A better 40-second Why LTTS: you want engineering R&D - automotive, plant, medical, embedded software - and you have practised aptitude plus C/C++ enough to survive CoCubes and a 30-minute viva. If you only know the L&T construction logo, you are not ready for HR.
Week-of-drive checklist
- Screenshot the OA mailer (platform, sections, languages, negative marking).
- Re-merge two sorted lists and binary-search on paper once.
- Recite overloading vs overriding and one SQL join without notes.
- Decide city yes/no and bond yes/no; do not invent a third option in the chair.
- Print or save ID; test laptop/network if the loop is online.
- Sleep. Sectional papers punish tired quant more than they punish a missing graph algorithm.
Related companies to compare
L&T · Persistent Systems · Bosch · Siemens · Birlasoft