Skip to content

LTTS Interview Experiences

These LTTS interview notes are rewritten from public student posts and prep-site summaries. Your panel can still look different.

Usual flow: Online test (COCUBES - aptitude + domain MCQs + coding) → Technical interview → HR

Engineering R&D services hiring - role-specific technical depth, but core CS/OOPs/DBMS basics are still tested even for non-software role families.

Resume/project discussion, OOPs (polymorphism, encapsulation, overloading vs overriding), DBMS (normalization, functional dependency), C++ fundamentals, and a coding problem (e.g. merge two sorted linked lists, array-sorting time complexity).

Personal-background conversation - hobbies, hometown, 5-year career outlook, location preference; runs about 20-30 minutes and is generally low-pressure.

3 rounds: OA on COCUBES (3 sections, coding portion had “merge two sorted linked lists” + a searching problem) → Technical interview (30 min: OOPs, DBMS normalization/functional dependency, ML topics from resume, C++, array-sorting-in-minimum-time-complexity problem) → HR (20 min: hobbies, hometown, 5-year plan). Selected; results in 2 days, 6 students selected for a 1-year internship track.

3 rounds: OA (90 questions - 30 logical, 30 quantitative, 30 domain - plus 2 coding questions; 57 candidates advanced) → Technical interview (resume, OOPs, SQL, basic C++) → HR (5-year career plan, location preference for assignments). Candidate received an offer.

These notes come from public reports and can differ by campus, year, and role. If your college placement email or the official careers/notification PDF says something different, follow that.

After technical rounds, LTTS usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

L&T · Persistent Systems · Bosch · Siemens · Birlasoft