01
Verification vs validation?
Show answer
Verification: are we building the product right? (reviews, walkthroughs — no code run). Validation: are we building the right product? (actual testing against user needs).
KPIT Technologies Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About KPIT Technologies hiring for Software Testing roles
KPIT Technologies is a Pune-based software integration partner for the automotive and mobility industry. It works with vehicle makers and suppliers on embedded software, autonomous driving, electric powertrains, connected vehicles and AUTOSAR-based development. In India it hires software, embedded, testing and validation engineers, and many roles suit candidates from electronics, electrical, mechanical and computer science backgrounds with an interest in vehicles.
For Software Testing roles, this KPIT Technologies practice set focuses most on Agile, SQL and API Testing (7), Manual Testing Basics (6), Performance and Security Basics (5), Testing Types (5). It has 15 easy, 23 medium, 2 hard questions, so you can start easy and work up to the harder ones.
- Company type
- IT services
- Headquarters
- Pune, India
- Main India offices
- Pune, Bengaluru
KPIT Technologies Software Testing interview process
- Online assessment (aptitude + programming)
- Technical interview
- Managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for KPIT TechnologiesStart 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
What is colour contrast ratio and what values does WCAG require?
Show answer
Contrast ratio compares the brightness of text and its background, from 1:1 to 21:1. WCAG AA requires at least 4.5:1 for normal text and 3:1 for large text, which is about 18 point or 14 point bold. User interface parts such as input borders and icons need 3:1. AAA raises text to 7:1. Testers check this with a contrast checker or browser developer tools, including placeholder, disabled and hover states.
03
What does the absence-of-errors fallacy mean?
Show answer
It means that finding and fixing many defects does not guarantee success if the system itself does not meet user needs. A bug-free product built on wrong or misunderstood requirements is still a failure. For example, a perfectly working report that shows the wrong business metric is useless to the client. This is why testers validate against real user expectations, not just the written specification.
04
What are response time, throughput and latency?
Show answer
Response time is the total time from sending a request to receiving the complete response, as the user experiences it. Latency is the delay before the first byte of the response arrives, mostly network and waiting time. Throughput is how many requests or transactions the system handles per unit of time, such as 500 requests per second. Good performance usually means low response time at the required throughput.
05
How do you test API error handling for invalid input?
Show answer
Send requests with missing required fields, wrong data types, values beyond limits, invalid formats such as a bad email, unknown fields and an empty or malformed JSON body. The API should return a 4xx code such as 400 or 422, a clear error message that names the field, and no stack trace or database details. Also check that nothing was partly saved in the database after the failed request.
06
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.
07
What is CSRF and how is it prevented?
Show answer
Cross-site request forgery tricks a logged-in user's browser into sending an unwanted request to a site, such as changing their email, because the browser automatically includes cookies. Prevention includes anti-CSRF tokens in forms, SameSite cookie settings and re-authentication for sensitive actions. Testers check that state-changing requests fail when the token is missing or reused, and that such actions are not done through GET requests.
08
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.
09
What is regression testing, and when do you automate it?
Show answer
Re-testing existing features after a change. Automate stable, repetitive, high-value flows that run every release.
10
SQL: verify that row counts and totals match between a source table and a target table after a data load.
Show answer
-- Compare counts and sums side by side; both columns must match
SELECT
(SELECT COUNT(*) FROM staging_orders) AS src_count,
(SELECT COUNT(*) FROM dw_orders) AS tgt_count,
(SELECT SUM(amount) FROM staging_orders) AS src_amount,
(SELECT SUM(amount) FROM dw_orders) AS tgt_amount;
11
What is end-to-end testing?
Show answer
End-to-end testing checks a complete business flow from the user's first action to the final result, across all connected parts: UI, APIs, database, third-party services and notifications. For example, in online shopping: search a product, add to cart, pay, receive the confirmation email and see the order in the account. It finds integration issues that module-level testing misses, but it is slower and needs stable environments.
12
What is the Page Object Model?
Show answer
The Page Object Model is a design pattern where each page or major component gets a class that holds its locators and actions, such as LoginPage with a login method. Tests call these methods instead of using locators directly. When the login button changes, you update one place instead of fifty tests. Tests become readable, like steps a manual tester would write, and duplication drops. Keep assertions mostly in tests, not page objects.
13
How can you do basic performance checks with browser developer tools?
Show answer
Open developer tools and use the network tab with cache disabled to see each request's size and time, and the total load time. Look for very large images or scripts, slow API calls and requests that fail or repeat. Use throttling to simulate slow 3G or 4G. Run the built-in performance audit tool to get scores for load speed and suggestions. Record the numbers so you can compare with later builds.
14
What is recovery testing?
Show answer
Recovery testing checks how well the system recovers from crashes, hardware failures, network loss or other failures. For example, kill the server during a file upload, or disconnect the network during payment, and verify the system restores a consistent state, does not lose or duplicate data and resumes or shows a clear message. It also measures recovery time against agreed targets, which matters for banking and healthcare systems.
15
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;
16
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.
17
What is Agile testing?
Show answer
Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.
18
SQL: find rows where mandatory columns are NULL or empty in a customers table.
Show answer
-- Mandatory fields: name, email, phone
SELECT id, name, email, phone
FROM customers
WHERE name IS NULL OR TRIM(name) = ''
OR email IS NULL OR TRIM(email) = ''
OR phone IS NULL OR TRIM(phone) = '';
-- Expected result: no rows
19
Write SQL to verify an order was saved correctly.
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123';
-- compare with the UI, then check the matching rows in order_items
20
What is shift-left testing and why is it cheaper?
Show answer
Shift-left means starting testing activities earlier in the life cycle: reviewing requirements, joining design discussions and writing tests before code is complete. A defect found in requirements may cost a short conversation to fix, while the same defect found in production may need a hotfix, data correction and customer support. Testers shift left by asking questions in grooming, defining acceptance criteria and reviewing designs.
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 is normalization and why should a tester understand it?
Show answer
Normalization organises tables to reduce duplicate data, for example storing the customer address once in a customers table instead of repeating it in every order. Testers should understand it because it explains where data lives and which joins are needed to verify a screen. It also shows risk: in a denormalized report table, the same value is copied in many places, so updates must be tested to confirm every copy changes.
23
What is a database view and what do you verify when testing it?
Show answer
A view is a saved query that behaves like a virtual table, often used for reports or to hide sensitive columns. When testing it, compare its output with the same query run on the base tables, check filters and joins return the right rows, confirm hidden columns such as salary are really absent, check behaviour when base data changes and verify that users without permission on the base tables can still read the view if intended.
24
Write test cases for an online money transfer.
Show answer
Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.
25
What are entry and exit criteria?
Show answer
Entry criteria are conditions that must be met to start testing (build ready, environment set); exit criteria define when testing can stop (pass rate, no critical defects).
26
What is UAT?
Show answer
User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.
27
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.
28
Explain the bug life cycle.
Show answer
New → Assigned → Open → Fixed → Retest → Verified → Closed, with Reopened, Rejected, Deferred and Duplicate as side paths.
29
What are the characteristics of a good test case?
Show answer
Clear, concise, independent, repeatable, traceable to a requirement, with precise expected results and tested data.
30
What does INVEST mean for user stories?
Show answer
INVEST is a checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable. For testers, testable is the most important: a story must have clear acceptance criteria so you can say pass or fail. Small stories are easier to test within a sprint. If a story fails INVEST, raise it in refinement rather than discovering the gaps during testing.
31
An automated test passes on your laptop but fails in the CI pipeline. How do you troubleshoot?
Show answer
Check the CI logs, screenshots, video or trace to see exactly where it failed. Then compare the environments: headless versus headed browser, screen size, browser version, time zone, environment URLs and secrets, test data and network speed. Run the test locally in headless mode with the CI settings. Common causes are timing, missing data in the CI environment and tests depending on run order. Fix the cause, not with a sleep.
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
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.
34
How does QA use Jira filters and dashboards?
Show answer
Save filters for common views such as my open bugs, bugs ready for retest, blockers in the current sprint and bugs by fix version. Add them to a dashboard with gadgets like pie charts by priority, created versus resolved trend and a sprint bug list. Share the dashboard with the team so status is visible without manual reports. Testers start their day from the ready-for-retest filter.
35
What is data mapping testing?
Show answer
Data mapping testing checks that each field on a screen, file or API goes to the correct table and column with the correct format. For example, the Date of Birth field on the signup form must land in users.dob as a date, and the State dropdown must store the state code, not the label. Testers use a mapping document, enter known values in the UI or API and query the database to compare field by field.
36
What is a test harness?
Show answer
A test harness is the setup of drivers, stubs, test data, scripts and tools needed to run tests on a component and collect results, especially when the full system is not available. For example, to test a pricing module, a harness can feed it input files, stub the tax service and compare outputs with expected values. In automation, the framework, runner and reporting together are often called the harness.
37
What is compatibility testing?
Show answer
Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.
38
What is the difference between a walkthrough and an inspection?
Show answer
Both are static review techniques. A walkthrough is informal and led by the author, who explains the document or code to peers to share knowledge and gather feedback. An inspection is the most formal review: it has defined roles such as moderator, reader and scribe, uses checklists, needs preparation and records defects and metrics. Inspections find more defects but take more effort.
39
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.
40
What is the difference between GET and POST?
Show answer
GET retrieves data and has parameters in the URL; POST sends data in the body to create or process something.
Tips to crack the KPIT Technologies Software Testing interview
- Revise C programming, pointers, embedded systems basics and microcontroller concepts, which are central to many KPIT engineering roles.
- Learn the basics of automotive software such as AUTOSAR, CAN communication and electric vehicle components to stand out in discussions.
- Prepare to explain any vehicle, robotics or embedded project in detail, including hardware used and how you tested it.
- 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; KPIT Technologies interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the KPIT Technologies Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + programming); 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 KPIT Technologies Software Testing interview?
This practice set leans on Agile, SQL and API Testing (7), Manual Testing Basics (6), Performance and Security Basics (5), Testing Types (5). Revise those first, then practise explaining one or two of your own projects end to end, because most KPIT Technologies interviewers ask you to walk through real work.
Are these the exact questions asked at KPIT Technologies?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like KPIT Technologies's. They are not a leaked or verified list of past questions.
Where does KPIT Technologies hire Software Testing professionals in India?
KPIT Technologies has large teams in Pune, Bengaluru. Openings and locations change often, so check the KPIT Technologies careers page and filter by city and experience.
Software Testing questions for similar companies
IT services
Infosys
Software Testing interview questions
Bengaluru, Mysuru, Pune +2
View questionsIT services
Tata Elxsi
Software Testing interview questions
Bengaluru, Thiruvananthapuram, Chennai +1
View questionsIT services
Capgemini
Software Testing interview questions
Mumbai, Bengaluru, Pune +2
View questionsIT services
Nagarro
Software Testing interview questions
Gurugram, Jaipur
View questionsIT services
HCLTech
Software Testing interview questions
Noida, Chennai, Bengaluru +2
View questionsIT services
Wipro
Software Testing interview questions
Bengaluru, Hyderabad, Pune +2
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