How L&T Technology Services (LTTS) campus and GET hiring usually runs, synthesized from GeeksforGeeks and public GET notes. We reorganized OA → technical → HR patterns, flagged CoCubes vs off-campus variance, and added prep notes - treat this as a prep map, not a script.
Candidate profile: Graduate Engineer Trainee (GET) off-campus applicant; composite from public 2025 GET postings and Faceprep LTTS process notes.
Shortlisting
Academic consistency screen (often 60% or 6.0+ CGPA throughout; no backlogs; age rules on some postings)
Some GET drives skip or shorten written test vs campus CoCubes
Apply via Superset / LTTS careers before published deadlines
Technical interview (30–45 min)
Final-year project: problem statement, your module, one bug, one metric
Branch fundamentals: DS/OS for CSE; circuits/signals for ECE; thermodynamics/CAD for mechanical where listed
Programming: pointer basics, recursion, implement or explain a standard sort
Systems question reported on software track: e.g. what happens when you type a URL (DNS, TCP, HTTP, render - high level)
Result: Pass when explanations stay honest and simple
HR (20–30 min)
Motivation for ER&D services vs pure IT support
Relocation across Mysuru, Vadodara, Chennai, Bengaluru, Pune, Mumbai, Hyderabad, Delhi
Training structure, role after academy, bond terms (some GET postings cite 18-month service commitment - verify letter)
Off-campus GET CTC often cited around ₹4.0 LPA in 2025 job posts - not comparable to campus software bands without your offer
Final result: Selection after HR alignment on bond and location
Key takeaways: GET off-campus is a training + bond + mobility conversation as much as a tech screen - read the PDF offer before celebrating the shortlist.
HR interview experience
HR interview experience
Candidate profile: Final-round campus candidate
HR prompts
5-year plan aligned to ER&D/tech services learning
Location flexibility across LTTS centres
Why LTTS / L&T group
Final result: Offer on successful tracks
Key takeaways: Show mobility and learning mindset without empty ambition slogans.
Sample answers for high-frequency questions
Use these as frames, not scripts.
Q. Where do you see yourself in 5 years? A. Near-term: strong engineer on delivery projects. Medium-term: own a module/domain (embedded/digital/engineering software - pick from PPT). Avoid “manager in 2 years” unless asked about leadership.
Q. Explain polymorphism with C++? A. Compile-time overloading vs runtime virtual dispatch. Sketch a base Shape::area() overridden by Circle.
Q. Write a simple SQL join example? A. Employees ⨝ Departments on dept_id to list names with department names. Mention LEFT JOIN when departments may be missing.
Q. Explain normalization to 3NF with an example? A. Start with a wide table with repeating groups; split into entities so non-key attributes depend on the whole key (2NF) and not transitively on other non-keys (3NF). Example: Student(Course, Instructor, Room) → separate Course and Instructor relations if Instructor depends only on Course.
Q. What happens when you type a URL? (software track) A. DNS resolves host → TCP connection → TLS if HTTPS → HTTP request → server response → browser parse HTML/CSS/JS → layout and paint. Keep one layer you can deep-dive if asked (e.g. DNS cache).
Q. Merge two sorted linked lists - why dummy head? A. Avoid special-casing the result head; tail pointer appends in O(1) per node; total O(m+n) time, O(1) extra space relinking nodes.
HR
Q. Why LTTS and not LTFS / parent L&T civil? A. LTTS is engineering R&D services for global OEMs; LTFS is finance; L&T Ltd campus civil tracks are construction - name the distinction so HR knows you read the JD.
Q. Bond and training? A. Ask for written bond duration, training stipend vs post-training CTC, and location policy; answer willingness honestly.
Common questions checklist
OA
Logical; quant; domain; 2 coding
Technical
Resume; OOP; SQL; C++ basics
HR
5-year plan; location; Why LTTS / ER&D; hobbies; bond/training on GET
LTTS vs LTFS confusion check; mobility across delivery centres
LTTS interview preparation checklist
CoCubes sim: 90 MCQs paced + two coding problems in one sitting
Domain sheet: One-page branch MCQ revision (ECE/ME/CE/CSE - match your registration)
OOP on paper: Tiny C++ class with virtual function; overloading vs overriding spoken aloud
SQL on paper: INNER and LEFT join; one aggregate (COUNT/GROUP BY)
Resume purge: Remove ML, CAD, or tools you only watched tutorials on
HR cards: Hometown + hobby (30 sec); 5-year plan tied to project engineer growth; relocation yes with cities named
Round-wise notes synthesize public campus and GET reports, then add prep takeaways and outcome context. Confirm CoCubes vs offline and bond terms on your drive mail. Citation inputs:
