01
What is SQL and why do testers use it?
Show answer
A language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.
State Bank of India Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About State Bank of India hiring for Software Testing roles
State Bank of India is India's largest public sector bank, with a huge network of branches and digital services such as the YONO app. It offers retail and corporate banking, loans, deposits and government banking services. It typically recruits through public examinations for roles like probationary officer and clerk, and through specialist officer notifications for IT, risk and data roles.
For Software Testing roles, this State Bank of India practice set focuses most on Agile, SQL and API Testing (6), Test Case Design (5), Bug Life Cycle and Jira (5), Automation Basics for Manual Testers (5). It has 4 easy, 32 medium, 4 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, Navi Mumbai
State Bank of India Software Testing interview process
- Preliminary online exam (for PO or clerk roles)
- Main online exam
- Psychometric test, group exercise or interview
- Document verification and final selection
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for State Bank of IndiaStart 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 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.
03
Your test repository has many duplicate and outdated test cases. How do you clean it up?
Show answer
Export the cases and group them by module and requirement. Mark duplicates, merge them into one well-written case, and retire cases for removed features. Check which cases have not been executed or failed in months and confirm whether they are still valid. Link the remaining cases to requirements so gaps are visible. Do it module by module with peer review, and set a rule that every story update also updates its test cases.
04
What is boundary value analysis?
Show answer
Testing at the edges of input ranges, such as 17, 18 and 19 for an age limit of 18, since errors cluster at boundaries.
05
What is mobile app testing and what extra checks does it need?
Show answer
Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.
06
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.
07
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.
08
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.
09
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.
10
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.
11
How do you write a good accessibility bug report?
Show answer
Give a clear title, such as 'Checkout: Place Order button not reachable by keyboard'. Include the page URL, browser, operating system and assistive technology with versions. Write exact steps, what was announced or happened, and what was expected. Add the WCAG success criterion, such as 2.1.1 Keyboard, and the user impact. Attach a screenshot or audio recording, and suggest a fix when obvious. Severity should reflect whether users are fully blocked.
12
What is the V-model?
Show answer
A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.
13
You join a project in the middle of a release. How do you plan your testing?
Show answer
Spend the first day learning the scope: read the release notes, user stories and test plan, and ask the lead what is at risk. Get access to the environment, tracker and test repository. Pick up a clearly defined module, run its existing test cases to learn the application and note gaps. Ask questions early in stand-up. Within a few days, take ownership of retesting and regression for that module.
14
Tell me about a time you found a bug by checking the database directly.
Show answer
Situation: a wallet refund screen showed success for every test. Task: I wanted to confirm the balance logic. Action: I queried the wallet_transactions table and saw two refund rows when I double-clicked the submit button, though the UI showed one. I logged it with both query outputs and the steps. Result: developers added an idempotency key, and the team added a database check to our regression checklist.
15
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.
16
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.
17
Write test cases for a file upload feature.
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
18
What is the definition of done?
Show answer
A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.
19
What is cause-effect graphing?
Show answer
Cause-effect graphing is a black box technique that models input conditions (causes) and output actions (effects) with logical relations like AND, OR and NOT. The graph is converted into a decision table, and each column becomes a test case. It is useful when outputs depend on combinations of inputs, such as loan approval based on income, age and credit score. It helps find missing or contradictory rules in the requirement.
20
Write a simple Playwright test in TypeScript that logs in and checks the dashboard heading.
Show answer
import { test, expect } from '@playwright/test';
test('valid user can log in', async ({ page }) => {
await page.goto('https://qa.example.com/login');
await page.getByLabel('Email').fill('qa.user@test.com');
await page.getByLabel('Password').fill('Secret@123');
await page.getByRole('button', { name: 'Login' }).click();
await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible();
});
21
Describe a time an automated test caught a regression that manual testing would have missed.
Show answer
Situation: a small tax rounding change was made late on a Friday. Task: no manual regression was planned for pricing. Action: our nightly API suite failed one data-driven case where a 3-item cart was off by one rupee; I checked the trace, reproduced it manually and logged it with the failing input. Result: it was fixed before release, and the team agreed to keep pricing tests in the pull request suite.
22
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.
23
What is deep link testing?
Show answer
A deep link opens a specific screen inside the app from a URL, email, SMS, QR code or notification. Test that each link opens the correct screen with the right data when the app is installed, closed or running in background. If the app is not installed, it should open the store page or a web fallback. Test links that need login, expired or invalid links, and that parameters cannot be tampered with to access other users' data.
24
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
25
How do you test push notifications?
Show answer
Verify notifications arrive when the app is in foreground, background and closed. Check title, text, icon and that tapping opens the right screen with the correct data. Test with notifications disabled at OS level and inside app settings. Check behaviour after logout, reinstall and on multiple devices with the same account. Test grouping of many notifications, time-sensitive ones, and that no notification shows private data on the lock screen.
26
Write test cases for live order tracking in a food delivery app.
Show answer
Verify each status change appears in order: placed, accepted, preparing, picked up and delivered. Check the rider's location updates on the map at the expected interval. Test the estimated time updates when there is a delay. Verify notifications for each status. Check behaviour when the network drops and recovers, when the app is reopened, and when the order is cancelled midway. Confirm tracking stops after delivery and the rating screen appears.
27
What is a user story and what are acceptance criteria?
Show answer
A user story describes a feature from the user's view, usually as: As a role, I want a goal, so that a benefit. Acceptance criteria are the specific conditions the story must meet to be accepted, often written as Given, When, Then. For example, given a registered user, when they enter a wrong password three times, then the account is locked for 15 minutes. Testers use acceptance criteria as the base for test cases.
28
How do you decide which automated tests run on every pull request and which run nightly?
Show answer
Pull request checks must be fast, usually under ten to fifteen minutes, and highly reliable, so they include unit tests, API tests for changed services and a small UI smoke set of critical flows. The full UI regression, cross-browser runs, long data-driven suites and performance checks run nightly or before release. Tag tests by suite, measure run times and flakiness, and move tests between suites based on value and speed.
29
What is a flaky test and what usually causes it?
Show answer
A flaky test passes and fails on the same code without any change. Common causes are timing problems such as fixed sleeps or missing waits, tests depending on each other or on shared data, unstable locators, animations, third-party services, test order in parallel runs and environment issues like slow servers. Flaky tests destroy trust in the suite, so teams quarantine them, find the root cause and fix it rather than adding retries forever.
30
What do you check in mobile accessibility testing?
Show answer
Turn on the screen reader, TalkBack on Android or VoiceOver on iOS, and check every button, image and field has a meaningful label and the reading order is logical. Check text scales with system font size, colour contrast is sufficient and touch targets are large enough, about 48 by 48 density-independent pixels. Make sure information is not shown by colour alone and that the app works without complex gestures.
31
What is data-driven testing?
Show answer
Data-driven testing runs the same test steps many times with different input and expected values taken from a table, CSV, JSON or spreadsheet. For example, one login test can run with valid users, locked users, wrong passwords and blank fields. It reuses the logic, makes adding cases easy and maps well to equivalence partitioning and boundary values from manual design. Tools support it through parameterised tests, such as pytest.mark.parametrize.
32
Tell me about a time exploratory testing helped you find a critical bug.
Show answer
Model answer: Situation: a new leave management module had passed all scripted cases. Task: I had a one-hour exploratory session. Action: I applied leave, then changed my manager in the profile while the request was pending. Result: the request disappeared for both managers and could never be approved. It was fixed before release, and the team added role-change scenarios to the regression suite.
33
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.
34
What is test monitoring and control?
Show answer
Test monitoring compares actual testing progress with the plan, using metrics like test cases executed, pass rate, open defects and effort spent. Test control is the action taken when monitoring shows a gap, such as re-prioritising tests, adding testers, changing the schedule or tightening entry criteria. For example, if half the time has passed but only a quarter of cases are executed, the lead must act and inform stakeholders.
35
SQL: find customers who placed more than three orders in the last 30 days.
Show answer
SELECT c.id, c.name, COUNT(o.id) AS order_count
FROM customers c
JOIN orders o ON o.customer_id = c.id
WHERE o.order_date >= CURRENT_DATE - INTERVAL '30' DAY
GROUP BY c.id, c.name
HAVING COUNT(o.id) > 3
ORDER BY order_count DESC;
36
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.
37
How do you test an application with no documentation?
Show answer
Talk to developers and users, explore the product, review similar systems, create notes and mind maps, confirm assumptions and write test cases as you learn.
38
What is a hotfix?
Show answer
An urgent patch released outside the normal schedule to fix a critical production defect, followed by regression testing and merge back to the main branch.
39
What is a bug bash and how do you run one?
Show answer
A bug bash is a short, time-boxed session where people from across the team, including developers, product and support, test the product together to find as many issues as possible before a release. To run one, share a build, scope and test accounts, assign focus areas, give a simple bug template and a shared board, then triage findings at the end. It brings fresh eyes and finds usability issues formal tests miss.
40
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.
Tips to crack the State Bank of India Software Testing interview
- Follow official SBI recruitment notifications closely, as eligibility, exam pattern and stages change between recruitment cycles.
- Prepare quantitative aptitude, reasoning, English and banking awareness thoroughly, practising full-length mock tests under exam timing.
- For specialist IT officer roles, revise networking, databases, security and programming topics listed in the official syllabus.
- 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; State Bank of India interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the State Bank of India Software Testing interview?
Candidates usually go through 4 stages: Preliminary online exam (for PO or clerk roles); Main online exam; Psychometric test, group exercise or interview; Document verification and final selection. 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 State Bank of India Software Testing interview?
This practice set leans on Agile, SQL and API Testing (6), Test Case Design (5), Bug Life Cycle and Jira (5), Automation Basics for Manual Testers (5). Revise those first, then practise explaining one or two of your own projects end to end, because most State Bank of India interviewers ask you to walk through real work.
Are these the exact questions asked at State Bank of India?
No. These are curated practice questions that match the skills and difficulty usually tested in banking & finance interviews like State Bank of India's. They are not a leaked or verified list of past questions.
Where does State Bank of India hire Software Testing professionals in India?
State Bank of India has large teams in Mumbai, Navi Mumbai. Openings and locations change often, so check the State Bank of India careers page and filter by city and experience.
Software Testing questions for similar companies
Banking & finance
Morgan Stanley
Software Testing interview questions
Mumbai, Bengaluru
View questionsBanking & finance
Citi
Software Testing interview questions
Pune, Chennai, Mumbai +2
View questionsBanking & finance
American Express
Software Testing interview questions
Gurugram, Bengaluru
View questionsBanking & finance
UBS
Software Testing interview questions
Pune, Mumbai, Hyderabad
View questionsBanking & finance
BNY
Software Testing interview questions
Pune, Chennai
View questionsBanking & finance
HDFC Bank
Software Testing interview questions
Mumbai, Chennai, 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