Larsen & Toubro interview process & guide 2026
Everything we know about interviewing at Larsen & Toubro: the process stage by stage, what each round tests, and reports from candidates who interviewed.
- 1HR Screening / Initial Screening
- 2Technical Assessment and Technical Rounds
- 3Client Round and Final Discussions
- 4Final Onsite / Face-to-Face and Offer
Interviewing at Larsen & Toubro
You will mostly experience an initial screen to validate fit and baseline alignment, then a series of technical evaluations. Across reported experiences, interviewers repeatedly tie questions back to your CV and your stated background, and they go deeper with follow-ups rather than stopping at surface answers.
What the loop tests is strongly technical, with a heavy emphasis on Azure DevOps and DevOps-style engineering topics. The extracted topic data shows Azure DevOps (percentile 100) and Technical interview (percentile 100) as the most prominent topics, and it also highlights DevOps Engineering (percentile 95), Databricks Administration (percentile 91), and Spark Development and Spark big data processing topics (percentiles 82 and 78). Tooling currency or upgrades (percentile 73), CI/CD pipeline concepts (percentile 69), and infrastructure automation (percentile 65) also appear often, so you should be ready to discuss how delivery and data platform operations work, not only how to write code.
After interviews, you should expect a wait for outcomes that can be on the order of weeks in at least some cases. Candidate reports mention no offers in the samples shown, and the aggregated candidate report offer rate is 0.0%, so you should calibrate expectations around very demanding evaluation and focus on process readiness rather than assuming a fast or easy path.
This process appears to be evaluated through multiple technical touchpoints, and the topic distribution is dominated by delivery and platform operations themes: Azure DevOps, CI/CD concepts, tooling upgrades, and Databricks and Spark operations and development.
How hard is the Larsen & Toubro interview?
Aggregated from 478 interview experiencesAbout 1 in 2 candidates with a known outcome convert.
The interview process, end to end
4 rounds · based on 478 candidate reports- 1HR Screening / Initial Screening
You start with an introductory screening conversation. The goal is to assess your qualifications and fit, including basic technical alignment and logistics or availability in some cases.
- 2Technical Assessment and Technical Rounds
You then move into deep technical evaluation. Reports describe technical discussions and evaluations that emphasize fundamentals and problem-solving methodologies, with some experiences including timed coding where the expectation is to produce working solutions.
- 3Client Round and Final Discussions
Some candidates go through a client assessment for technical and cultural fit for the specific project. There may also be a final discussion stage to clarify remaining questions and discuss next steps.
- 4Final Onsite / Face-to-Face and Offer
Depending on the path, you may have an in-person or onsite interview that can include multiple technical and behavioral rounds. If you reach the last step, there is an offer and compensation discussion.
What Larsen & Toubro actually tests for
How prominent each skill is across reported loopsFind the guide for your role
This is your next step: open the guide for the role you are interviewing for. Each one carries the questions Larsen & Toubro interviewers actually ask that position, the loop structure, and pay by level.
Real interview experiences
What candidates said about the loop, difficulty, and outcomes, straight from recent reports for these roles.
What separates offers from rejections
Patterns from candidates who got offers, and the mistakes that most often sink a loop.
Do this
- Make your answers anchored to what you have already written on your CV, and be ready for the interviewer to challenge your choices and push into deeper follow-ups.
- If your role is in the data or DevOps orbit, prepare to talk through Databricks administration and Spark development topics, and connect them to data processing or platform operations.
- For Azure DevOps and CI/CD, be ready to explain pipeline concepts and how you would approach tooling upgrades or build and release automation, not just definitions.
- Practice producing working solutions under time pressure, since at least one reported coding interview emphasized delivering working results within the allotted time.
Avoid this
- Do not give surface-level project or experience walkthroughs. Reports describe interviewers probing what you did and how you would think if requirements or approach changed.
- Do not rely only on high-level theory for the technical portion. The difficulty distribution includes a sizable hard share (20.5%) and the process includes deep technical evaluation and deeper concept follow-ups.
- Do not treat screening as merely administrative. Multiple reports describe tight filtering on fundamentals and CV alignment before moving to technical rounds.
- Do not assume immediate feedback or a short timeline. At least one candidate report mentions hearing back after about 20 days, and processes are described as spanning multiple stages.
Larsen & Toubro interview FAQ
Answered from real candidate and workplace dataHow hard is the interview process?
The aggregated difficulty distribution across candidate reports is 18.2% easy, 60.6% medium, 20.5% hard, and 0.8% very hard. Reports also describe deep follow-ups and technical evaluations that can feel demanding.
Do you get an offer after the final stage?
From the aggregated candidate reports, the offer rate is 0.0%. In the provided sample reports, candidates also note not receiving an offer.
What topics should I prioritize most?
Prioritize Azure DevOps (percentile 100) and the technical interview itself (percentile 100). Next in prominence are DevOps Engineering (percentile 95), Databricks Administration (percentile 91), and Spark development and Spark big data processing topics (percentiles 82 and 78), plus tooling currency and CI/CD concepts.
How long does it take, and when will I hear back?
Candidate reports describe end to end experiences that can be short, such as around two days in one case, and they also describe waiting for results, such as hearing back after about 20 days in another. The process includes multiple stages, including technical rounds and HR or client-facing discussions.
Is the interview more coding, more systems, or more HR?
The topic data is dominated by technical areas related to Azure DevOps, DevOps engineering, Databricks, and Spark, with CI/CD and infrastructure automation also recurring. Reports still include HR components, but the emphasis appears to stay on technical evaluation and fundamentals, often with CV-linked deep dives.
Should I reapply if I do not pass?
The supplied data does not say anything about re-application or how L&T handles candidates who apply again after rejection. If you want guidance tailored to your situation, share the role you are targeting and your strongest technical areas.
What people say about Larsen & Toubro
Verbatim snippets from employee and candidate reviews“Larsen & Toubro offers excellent opportunities for learning and development.”
“Office politics and discrimination against late joiners can be significant challenges.”
“The support from senior colleagues has been invaluable.”
“Long work hours and a toxic environment are significant drawbacks.”
“Timely salary and job security are definite positives.”
“The overall experience is a mix of good, bad, and ugly.”
Related company guides
Companies that hire for the same data roles
Ready for your Larsen & Toubro interview?
Practice the exact questions from this guide with AI feedback, and walk into your loop knowing what to expect.