01
Severity vs priority — with an example.
Show answer
Severity = impact on the system. Priority = urgency to fix.
Logo misspelt on the homepage → low severity, high priority.
Crash in a rarely used report → high severity, low priority.
L&T Technology Services Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About L&T Technology Services hiring for Software Testing roles
L&T Technology Services is an engineering research and development services company and part of the Larsen & Toubro group. It works with clients in transportation, industrial products, telecom, medical devices and plant engineering on product design, embedded systems and digital engineering. In India it hires engineers for software, embedded, testing and data roles across its engineering and delivery centres.
For Software Testing roles, this L&T Technology Services practice set focuses most on Agile, SQL and API Testing (8), Bug Life Cycle and Jira (6), Testing Types (4), Performance and Security Basics (4). It has 16 easy, 23 medium, 1 hard questions, so you can start easy and work up to the harder ones.
- Company type
- IT services
- Headquarters
- Vadodara, India
- Main India offices
- Vadodara, Bengaluru, Chennai, Mysuru, Pune
L&T Technology Services Software Testing interview process
- Online assessment (aptitude + technical MCQs)
- Technical interview
- Managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for L&T Technology ServicesStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
02
Functional vs non-functional testing?
Show answer
Functional testing checks what the system does (login, checkout). Non-functional testing checks how well it does it (performance, security, usability, compatibility).
03
What are Postman environments and the Collection Runner?
Show answer
An environment in Postman is a set of variables, such as base_url and token, that you switch to run the same requests against QA, staging or production-like setups without editing each request. The Collection Runner executes all requests in a collection in order, runs their test scripts and can repeat them with data from a CSV or JSON file. Together they give manual testers a first step into repeatable API automation.
04
What is a regression bug and how do you track it in Jira?
Show answer
A regression bug is a feature that worked before but broke after a new change, such as login failing after a profile page update. It is usually treated with higher priority because it affects existing users. In Jira, add a label such as regression, set the affected version and link it to the story or change that caused it. Tracking these labels over time shows where regression coverage is weak.
05
What is a screen reader and which ones are commonly used for testing?
Show answer
A screen reader is software that reads screen content aloud or sends it to a braille display, used mainly by blind and low-vision people. Common ones are NVDA, a free Windows reader, JAWS, a paid Windows reader common in enterprises, VoiceOver, built into macOS and iOS, and TalkBack, built into Android. Testers usually cover NVDA with a desktop browser plus VoiceOver or TalkBack on mobile.
06
SQL: find the second highest salary from an employees table.
Show answer
SELECT MAX(salary) AS second_highest
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);
-- alternative using DENSE_RANK
SELECT DISTINCT salary FROM (
SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk
FROM employees
) t WHERE rnk = 2;
07
What are the typical JIRA workflows for bugs?
Show answer
Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.
08
What is the OWASP Top 10 and why should testers know it?
Show answer
The OWASP Top 10 is a widely used list of the most critical web application security risks, published by an open community project. It includes broken access control, cryptographic failures, injection, insecure design, security misconfiguration, vulnerable components and authentication failures. Testers use it as a checklist to include basic security checks in their testing and to speak the same language as security teams.
09
A user updates their phone number in the app, but the old number still appears in reports. What do you check?
Show answer
First query the main users table to see whether the update was saved. If it was, check where the report reads from: a view, a reporting copy, a cache or a nightly ETL table. The report may simply be stale until the next refresh, which may be by design. If the main table still has the old value, check the API request, the update query and any errors in logs, then log a bug with both query results.
10
What is a REST API?
Show answer
An API style using HTTP methods on resources identified by URLs, usually exchanging JSON and staying stateless.
11
What sensitive data checks do you do in API responses and logs?
Show answer
Check that responses return only needed fields, with no passwords, password hashes, full card numbers, full ID numbers or internal keys. Verify personal data is masked where required, for example only the last four digits of a phone number. Look at application and browser console logs for tokens or personal data. Check error responses do not expose stack traces, SQL or server versions. Raise any leak as a high-severity bug.
12
What is localisation and internationalisation testing?
Show answer
Internationalisation tests that the product can support many languages and formats; localisation tests that a specific locale is correct for text, currency, date and layout.
13
What is the difference between an emulator, a simulator and a real device?
Show answer
An emulator imitates both the hardware and software of a device, as with the Android emulator, so it behaves close to a real phone. A simulator imitates only the software environment, as with the iOS simulator, and does not reproduce the hardware. Both are free and fast for early testing. Real devices are needed for camera, battery, sensors, actual performance, network behaviour and final sign-off.
14
Why are hard-coded sleeps bad in automated tests?
Show answer
A fixed sleep, such as waiting five seconds, is either too long, which makes the suite slow when the page loads in one second, or too short, which makes the test fail when the server is slow. Both waste time and cause flaky results. Instead, wait for a real condition: an element to appear, a network response to finish or a loading spinner to disappear. Modern tools do much of this automatically.
15
What is test automation and what problems does it solve?
Show answer
Test automation means using scripts and tools to run tests, compare results and report them without a person doing each step. It solves slow and repetitive regression, gives fast feedback on every code change in CI, runs the same checks exactly the same way every time and covers many data combinations. It does not replace thinking: exploratory testing, usability judgement and new feature testing still need manual testers.
16
How do you write steps to reproduce for a bug that needs specific test data?
Show answer
Start with preconditions: environment, build number, user role and the exact data state, such as an account with two pending orders and zero wallet balance. Mention how to create the data or give the test account ID. Then list numbered steps with exact inputs and finish with expected and actual results. If the data is hard to set up, attach the SQL used or a database screenshot so the developer can recreate it quickly.
17
Scrum ceremonies and the tester's role?
Show answer
Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.
18
How do you make test cases reusable and easy to maintain?
Show answer
Write one clear objective per case, keep steps short and avoid hard-coding data that changes. Put shared steps such as login into a common precondition instead of repeating them. Use consistent naming, link each case to a requirement and group them by module. Keep expected results specific but not tied to exact pixel layouts. Review and update cases whenever a story changes, so the suite stays trustworthy for regression.
19
What is usability testing?
Show answer
Evaluating how easy and pleasant a product is to use by observing real users complete tasks and noting confusion.
20
The UI shows the correct order total, but the database has a different value. What do you check?
Show answer
Note the order ID and compare the UI value, the API response and the database value to find where they differ. Check if the UI calculates the total on the screen instead of using the saved value, whether taxes, discounts or rounding are applied at different layers and whether a later update job changed the record. Log the bug with all three values, because invoices and reports will use the database figure.
21
What is cross-site scripting (XSS)?
Show answer
XSS is a vulnerability where an attacker's script is injected into a page and runs in other users' browsers, which can steal session data or change the page. It occurs when user input is shown without proper encoding. Testers enter a harmless script tag or an image tag with an onerror alert in comments, profile names and search boxes, then check if it executes when the page is displayed. Output encoding prevents it.
22
What are ACID properties and how can a tester check them?
Show answer
ACID means Atomicity, Consistency, Isolation and Durability. Atomicity: a transfer that debits one account must also credit the other, or neither happens; test by forcing a failure midway. Consistency: constraints still hold after the transaction. Isolation: two users updating together do not see each other's half-done work; test with two sessions. Durability: committed data survives a restart; test by committing, restarting the service and querying again.
23
What are stubs and drivers?
Show answer
Both are temporary pieces of code used in integration testing when some modules are not ready. A stub replaces a called lower-level module and returns fixed responses, used in top-down testing; for example, a stub payment service that always returns success. A driver replaces a calling higher-level module and sends inputs to the module under test, used in bottom-up testing. In API testing, mock servers play the role of stubs.
24
Write test cases for a forgot password feature.
Show answer
Verify reset with a registered email sends a link. Verify an unregistered email shows a generic message without revealing whether the account exists. Check the link opens the reset page and expires after the defined time. Check the link works only once. Validate new password rules and that confirm password must match. Verify login works with the new password and fails with the old one. Check resend limits and that other sessions are logged out.
25
How is back-end database testing different from front-end UI testing?
Show answer
UI testing checks what the user sees and does: screens, buttons, messages and flows. Database testing checks what happens underneath: whether the right rows are inserted, updated or deleted, whether constraints hold and whether data stays consistent across tables. A screen can show a success message while the database saved a wrong amount or nothing at all. So testers combine both, using SQL to confirm that every important UI action leaves the database in the expected state.
26
How do you handle a bug found late in a release cycle?
Show answer
Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.
27
What do you do in the test execution phase when a test fails?
Show answer
Re-run the test once to confirm the failure and rule out wrong data or environment issues. Capture evidence such as screenshots, logs and the build number. Check for an existing bug, then log a new one with clear steps and link it to the test case. Mark the test as failed, and mark dependent tests as blocked if they cannot run. After the fix, retest and run related regression.
28
What is API testing and why is it important?
Show answer
Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.
29
What is a Three Amigos session?
Show answer
Three Amigos is a short meeting where a business person or product owner, a developer and a tester discuss a story before development. The business explains the need, the developer considers how to build it and the tester asks what could go wrong and how it will be verified. The output is clear acceptance criteria and example scenarios. It prevents misunderstandings and reduces bugs found late.
30
What is JMeter and what does a basic test plan in it contain?
Show answer
Apache JMeter is an open-source load testing tool, mainly for HTTP APIs and web pages. A basic test plan has a Thread Group that sets the number of virtual users, ramp-up time and loop count; samplers such as HTTP Requests; config elements like headers and CSV data; timers for think time; assertions on responses; and listeners or reports showing response times, throughput and errors. Run real load in non-GUI mode.
31
What is visual regression testing in automation?
Show answer
Visual regression testing takes screenshots of pages or components and compares them with approved baseline images to detect unexpected layout, font, colour or spacing changes that functional assertions miss. When a difference crosses a threshold, a person reviews it and either accepts the new baseline or logs a bug. Dynamic content like dates and ads must be masked, and the same browser and screen size must be used to avoid noise.
32
What is a locator and what types of locators exist?
Show answer
A locator tells the automation tool how to find an element on the page so it can click, type or check it. Common types are ID, name, CSS selector, XPath, link text, and in modern tools role-based locators such as a button with name Login, plus label, placeholder and test ID locators. A good locator is unique, readable and unlikely to change when the page design changes.
33
What are positive and negative test cases?
Show answer
Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.
34
What are the seven principles of testing?
Show answer
Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.
35
What is data masking and why is it used in test databases?
Show answer
Data masking replaces real sensitive values with realistic but fake ones, for example changing real phone numbers to valid-looking dummy numbers and real names to generated names. It lets teams test with production-like data volume and patterns without exposing customer information. It also supports compliance with India's Digital Personal Data Protection Act. Testers should check that masked data still passes validation rules and keeps relationships between tables intact.
36
Difference between black box, white box and grey box testing?
Show answer
Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.
37
How do you use JIRA in testing?
Show answer
Log and track bugs, link them to stories, build dashboards and filters with JQL, manage sprints and generate reports.
38
What is error guessing?
Show answer
Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.
39
What is the difference between a test case and a test scenario?
Show answer
A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.
40
SQL: verify that soft-deleted users do not appear in the active users list.
Show answer
-- the active list query used by the app should return 0 rows here
SELECT u.user_id, u.email
FROM users u
WHERE u.is_deleted = 1
AND u.user_id IN (
SELECT user_id FROM active_users_view
);
Tips to crack the L&T Technology Services Software Testing interview
- Revise core engineering subjects from your branch along with C, basic data structures and one scripting language before the technical round.
- Be ready to explain an academic or internship project end to end, including design choices, tools used and testing approach.
- Read about LTTS segments like mobility, medical devices and plant engineering so you can connect your skills to a domain.
- Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
- Practise the hard questions on this page aloud; L&T Technology Services interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the L&T Technology Services Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + technical MCQs); Technical interview; Managerial round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the L&T Technology Services Software Testing interview?
This practice set leans on Agile, SQL and API Testing (8), Bug Life Cycle and Jira (6), Testing Types (4), Performance and Security Basics (4). Revise those first, then practise explaining one or two of your own projects end to end, because most L&T Technology Services interviewers ask you to walk through real work.
Are these the exact questions asked at L&T Technology Services?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like L&T Technology Services's. They are not a leaked or verified list of past questions.
Where does L&T Technology Services hire Software Testing professionals in India?
L&T Technology Services has large teams in Vadodara, Bengaluru, Chennai, Mysuru, Pune. Openings and locations change often, so check the L&T Technology Services careers page and filter by city and experience.
Software Testing questions for similar companies
IT services
Wipro
Software Testing interview questions
Bengaluru, Hyderabad, Pune +2
View questionsIT services
Quest Global
Software Testing interview questions
Bengaluru, Thiruvananthapuram, Belagavi +1
View questionsIT services
Infosys
Software Testing interview questions
Bengaluru, Mysuru, Pune +2
View questionsIT services
HCLTech
Software Testing interview questions
Noida, Chennai, Bengaluru +2
View questionsIT services
Tech Mahindra
Software Testing interview questions
Pune, Hyderabad, Bengaluru +2
View questionsIT services
Birlasoft
Software Testing interview questions
Pune, Noida, Bengaluru +1
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets