01
How do you test pagination, sorting and filtering through an API?
Show answer
Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.
Axis Bank Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Axis Bank hiring for Software Testing roles
Axis Bank is one of India's large private sector banks, offering retail banking, corporate banking, credit cards, loans and digital payment services. It acquired Citibank's India consumer business in 2023. It hires for branch banking, relationship management, operations, risk, analytics and technology roles, and also runs young professional and campus programmes.
For Software Testing roles, this Axis Bank practice set focuses most on Manual Testing Basics (5), Test Case Design (5), Bug Life Cycle and Jira (5), Performance and Security Basics (5). It has 8 easy, 29 medium, 3 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Banking & finance
- Headquarters
- Mumbai, India
- Main India offices
- Mumbai, Bengaluru
Axis Bank Software Testing interview process
- Online assessment (aptitude + banking awareness)
- Functional or technical interview
- Managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Axis BankStart 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
How do you test a mobile app when the device storage is almost full?
Show answer
Fill the device storage close to the limit, then install or update the app and confirm a clear message if it cannot proceed. Inside the app, try downloads, photo capture, caching and saving drafts. The app should show a helpful error, not crash or corrupt data. Also check what happens to the local database when a write fails, and whether the app recovers after space is freed.
03
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.
04
What is a test case and its components?
Show answer
A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.
05
What is use case testing?
Show answer
Designing tests from user flows described in use cases to verify complete real-world interactions.
06
What is the difference between a defect and a production incident?
Show answer
A defect is a flaw in the software that makes it behave differently from the requirement, whether found in testing or production. A production incident is an event that disrupts or degrades service for users, such as an outage or a failed payment flow. An incident may be caused by a defect, but also by infrastructure, configuration or third-party failures. Incidents are handled by an incident process first, then linked to defects for the fix.
07
How do you handle a product owner who keeps adding scope in the middle of a sprint?
Show answer
Model answer: Situation: our product owner added two small changes to a story mid-sprint, which pushed testing to the last day. Task: protect quality without being rigid. Action: I showed the extra test effort in stand-up and asked the Scrum Master to help decide what to swap out. Result: one change moved to the next sprint, and the team agreed new requests go through the backlog.
08
Your automated tests pass one by one but fail randomly when run in parallel. How do you fix the test data so tests are independent?
Show answer
Each test should create the data it needs, usually through an API or database helper, use unique values such as an email with a timestamp, and clean up afterwards. Avoid tests that depend on data made by another test or on a shared account other tests change. For fixed reference data, seed it before the suite runs. Independent data allows tests to run in parallel and in any order without random failures.
09
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
);
10
What is a test plan and what does it contain?
Show answer
A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.
11
What is a performance bottleneck and where do bottlenecks usually occur?
Show answer
A bottleneck is the component that limits the whole system's performance, so adding load beyond it increases response times or errors. Common places are slow database queries or missing indexes, too few database connections or threads, CPU or memory limits on servers, slow third-party APIs, large uncompressed files and chatty code that makes many small calls. Monitoring each layer during a test shows which resource saturates first.
12
What is the difference between a test strategy and a test plan?
Show answer
A test strategy is a high-level document, often at organisation or product level, that defines the general approach: test levels, types, tools, environments, automation approach and standards. It changes rarely. A test plan is project or release specific: scope, schedule, resources, entry and exit criteria, risks and deliverables. The plan follows the strategy and applies it to a particular release.
13
How do you test an application when requirements change frequently?
Show answer
Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.
14
What do testers look for during a requirement review?
Show answer
Check that each requirement is clear, complete, consistent and testable. Look for vague words like fast or user-friendly, missing error handling, undefined limits, conflicting rules and missing roles or states. For each requirement ask how you would test it and what the expected result is. Record questions in a review log and get answers from the business analyst before writing test cases, so ambiguity does not turn into defects later.
15
A client needs WCAG 2.2 AA compliance before launch in two weeks. How do you plan the testing?
Show answer
Agree on scope: key user journeys and page templates, not every page. Day one, run automated scans on all templates to fix easy issues fast. Then do manual checks of each journey with keyboard, NVDA, VoiceOver on mobile, zoom and contrast. Log issues with WCAG references and severity, and get blockers fixed first. Retest fixes and deliver a conformance summary with known issues. Be honest if full compliance is not realistic.
16
What is defect leakage?
Show answer
Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.
17
How would you test a feature that is enabled for only 10 percent of users through a feature flag?
Show answer
Test both states: flag on and flag off, so existing users are not affected. Verify the targeting rule assigns the right users and that a user stays consistently in the same group. Test switching the flag on and off in a live session and confirm data created with the flag on still works after it is turned off. Check analytics events for both groups and confirm the flag can be rolled back quickly.
18
What is a test scenario for the login functionality at a high level?
Show answer
Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.
19
What does POUR mean in accessibility?
Show answer
POUR is the four principles behind WCAG. Perceivable: users can see or hear the content, for example images have alt text and videos have captions. Operable: everything works with a keyboard and users have enough time. Understandable: text is clear and forms explain errors. Robust: content works with assistive technologies such as screen readers. Every WCAG success criterion sits under one of these four principles.
20
What is an assertion and what makes a good one?
Show answer
An assertion is the check in an automated test that compares the actual result with the expected result and fails the test if they differ, like the expected result column in a manual test case. A good assertion checks the outcome that matters to the user, such as the order confirmation number appearing, not just that a page loaded. It should be specific, give a clear failure message and avoid fragile details like exact timestamps.
21
What is scalability testing?
Show answer
Scalability testing checks how well the system handles growing load by adding resources, such as more servers or bigger machines, and whether performance improves in proportion. For example, if two servers handle 1,000 users, do four servers handle about 2,000 at the same response time? It finds limits that resources cannot fix, such as a single database bottleneck, and helps plan capacity for future growth.
22
What does quality mean to you as a tester?
Show answer
Model answer: To me quality means the product does what users need, reliably, and is easy to use, not just that test cases pass. In my final-year project I tested a library app; all features worked, but students struggled to find the search option. I reported it as a usability issue and the team moved search to the home screen. That taught me to test from the user's point of view as well.
23
A page loads slowly only for some users. How do you investigate as a manual tester?
Show answer
Collect details from affected users: location, device, browser, network and time. Try to reproduce with similar conditions using browser network throttling. Use the browser developer tools network tab to find slow requests, large files or failing calls, and compare with a fast user. Check whether those users have more data, like a long order history. Share the slow request, timing and conditions in the bug for the developers.
24
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.
25
Write test cases for a search box.
Show answer
Valid keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.
26
The test environment is down for two days just before release. What do you do?
Show answer
Escalate immediately with the impact on the schedule. While it is down, prepare test data, review and update test cases, and test what you can elsewhere: API tests against another environment, UI on a developer machine or a staging copy. Track the lost hours in the status report. When the environment returns, run smoke first, then the prioritised list, and ask whether the release date or scope needs to change.
27
What is SQL injection and how can a tester check for it at a basic level?
Show answer
SQL injection happens when user input is added directly into a database query, letting an attacker change the query to read or modify data. A tester can enter inputs like a single quote or ' OR '1'='1 in login, search and URL parameters and watch for database errors, unexpected results or a login bypass. Only test in approved environments. The real fix is parameterised queries, not input filtering alone.
28
An automated test keeps failing because an element's ID is generated differently on every build. What do you do?
Show answer
Stop using the dynamic ID. Look for a stable alternative: the element's role and visible name, its label, a stable attribute, or a relative locator based on a nearby fixed element. The best long-term fix is asking developers to add a data-testid attribute. Avoid partial matches on random strings, which can break again. Then update the locator in the page object so every test using it is fixed at once.
29
How do you link stories, test cases and bugs in Jira for traceability?
Show answer
Create test cases as linked issues or in a test management add-on and link each one to its story with a tests relationship. When a test fails, create the bug from the test execution or link it to both the test and the story with is blocked by or relates to. Use the same fix version for all. A story then shows its tests and open bugs, which makes sign-off and the traceability report easy.
30
Tell me about a time you found a usability problem that the requirements did not mention.
Show answer
Situation: while testing a leave application form, every test case passed. Task: I still felt the flow was confusing. Action: I noticed the date picker started on Sunday and the half-day option was hidden under 'More', so I asked two colleagues to apply for leave while I watched; both made mistakes. I logged a usability suggestion with notes. Result: product moved the option and support queries dropped.
31
How do you test session management in a web application?
Show answer
Check that a new session ID is created after login, and that the session expires after the defined idle time. Verify logout invalidates the session on the server, so pressing back or reusing the old cookie does not work. Check that cookies use Secure, HttpOnly and SameSite flags. Test concurrent logins if they are limited, and that changing the password ends other sessions. Session IDs must not appear in URLs.
32
SQL: how do you test a foreign key defined with ON DELETE CASCADE?
Show answer
-- Create a parent and child, delete the parent, child rows must disappear
INSERT INTO customers (id, name) VALUES (501, 'Cascade Test');
INSERT INTO orders (id, customer_id, total) VALUES (7001, 501, 250);
DELETE FROM customers WHERE id = 501;
SELECT COUNT(*) FROM orders WHERE customer_id = 501;
-- Expected: 0
-- Also test inserting an order for a non-existent customer: it must fail
33
The developer says "it's not a bug". What do you do?
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
34
A developer asks you to test a feature that has no acceptance criteria. How do you proceed?
Show answer
First ask the product owner or business analyst for the expected behaviour and write down the answers as draft acceptance criteria. Meanwhile, explore the feature, compare it with similar existing features and list assumptions. Share the assumptions in the story so everyone agrees before you sign off. Raise the missing criteria in the next refinement so future stories are not picked up without them.
35
What is defect removal efficiency?
Show answer
Defect removal efficiency shows how many defects the team found before release. DRE = defects found before release divided by (defects found before release plus defects found after release), multiplied by 100. If QA found 90 bugs and users reported 10, DRE is 90 percent. A falling DRE means testing is missing more defects, and the escaped bugs should be analysed to improve test coverage.
36
How do you set up and clean test data for database tests without affecting other testers?
Show answer
Create your own data with a clear prefix or tag, such as emails starting with qa_ravi_, or IDs in a reserved range. Insert data through the app or API where possible so it follows real rules, and keep SQL setup scripts in version control. After testing, delete only your tagged rows, or run inside a transaction and roll back. Never edit shared master data without telling the team.
37
Which test cases are good candidates for automation?
Show answer
Good candidates are stable, repeatable and high value: smoke tests, regression of core flows such as login and checkout, data-driven checks with many inputs, API tests and cross-browser runs of the same flow. Poor candidates are features still changing every sprint, one-time tests, tests needing human judgement like look and feel, and flows that are hard to make reliable, such as real OTP or CAPTCHA. Start with what runs most often.
38
What is JSON schema validation in API testing?
Show answer
JSON schema validation checks that a response has the expected structure: required fields are present, data types are correct, formats like email or date are valid and no unexpected fields appear. Instead of checking only one value, it protects against contract changes that break the app. In Postman you can validate a response against a schema in the test script, and run it on every request in a collection.
39
Tell me about a time you found an important bug that others missed.
Show answer
Model answer: Situation: before a release of an insurance app, all regression tests had passed. Task: I was doing a final exploratory round. Action: I renewed a policy on the last day of the month and saw that the premium was calculated for 31 days in a 30-day month. I logged it with exact data and the formula difference. Result: the date logic was fixed before release, and I added month-end cases to the suite.
40
What is compliance testing?
Show answer
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
Tips to crack the Axis Bank Software Testing interview
- Prepare banking awareness topics such as repo rate, CASA, NPAs, KYC and digital payment systems like UPI.
- For analytics and technology roles, revise SQL, Excel and data visualisation, and be ready with project examples.
- Practise clear communication and customer-handling answers, since many bank roles involve direct interaction with customers.
- 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; Axis Bank interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Axis Bank Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + banking awareness); Functional or 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 Axis Bank Software Testing interview?
This practice set leans on Manual Testing Basics (5), Test Case Design (5), Bug Life Cycle and Jira (5), Performance and Security Basics (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Axis Bank interviewers ask you to walk through real work.
Are these the exact questions asked at Axis Bank?
No. These are curated practice questions that match the skills and difficulty usually tested in banking & finance interviews like Axis Bank's. They are not a leaked or verified list of past questions.
Where does Axis Bank hire Software Testing professionals in India?
Axis Bank has large teams in Mumbai, Bengaluru. Openings and locations change often, so check the Axis Bank careers page and filter by city and experience.
Software Testing questions for similar companies
Banking & finance
Deutsche Bank
Software Testing interview questions
Pune, Bengaluru, Mumbai +1
View questionsBanking & finance
American Express
Software Testing interview questions
Gurugram, Bengaluru
View questionsBanking & finance
ICICI Bank
Software Testing interview questions
Mumbai, Hyderabad, Chennai +1
View questionsBanking & finance
HSBC
Software Testing interview questions
Hyderabad, Pune, Bengaluru
View questionsBanking & finance
Goldman Sachs
Software Testing interview questions
Bengaluru, Hyderabad, Mumbai
View questionsBanking & finance
Kotak Mahindra Bank
Software Testing interview questions
Mumbai, Bengaluru
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