Skip to content

Software Testing Interview Questions for Banking & finance Companies

40 questions weighted to the interview style of banking & finance companies — 8 easy, 30 medium, 2 hard.

How banking & finance companies interview for Software Testing

Banks and financial-services firms hire for technology, analytics and QA in their global capability centres. Interviews mix technical rounds with domain questions on banking products, regulation, data quality and risk, and they value process discipline.

This set focuses on Agile, SQL and API Testing (8), Test Case Design (5), Mobile Testing (5), Automation Basics for Manual Testers (4).

HR round Managerial round Technical round Hiring manager round Online assessment (aptitude + technical)
Solved — banking & finance companiesStart 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
01

How do you test pagination, sorting and filtering through an API?

Save to ▾
Show answer
Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.
02

What is an assertion and what makes a good one?

Save to ▾
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.
03

What is JQL?

Save to ▾
Show answer
JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.
04

An API returns 200 OK but the body contains an error message. Is that a bug?

Save to ▾
Show answer
Usually yes. Status codes should reflect the result so clients and monitoring can react correctly; an error with 200 can hide failures and break retries. A validation error should return 400 or 422, a missing resource 404 and a server failure 500. Check the API contract first: some legacy APIs document this pattern. If it is not documented, log it as a defect with the request and response attached.
05

What are severity and priority? Give examples.

Save to ▾
Show answer
Severity is impact on the system; priority is urgency of the fix. A crash in a rare report is high severity, low priority; a spelling mistake in the logo is low severity, high priority.
06

What is test automation and what problems does it solve?

Save to ▾
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.
07

Write test cases for a calculator app.

Save to ▾
Show answer
Basic operations, division by zero, decimals, large numbers, order of operations, clear and backspace, repeated operations and memory keys.
08

Write test cases for a file upload feature.

Save to ▾
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
09

What is heuristic evaluation and how is it different from a usability test with users?

Save to ▾
Show answer
Heuristic evaluation is an expert review where a few evaluators inspect the interface against known usability principles, such as Nielsen's ten heuristics, and list problems with severity. It is fast and cheap and needs no participants. A usability test watches real users perform tasks and shows where they actually struggle. Heuristic reviews find many obvious issues early, but they can miss problems that only real users with real goals reveal.
10

What is a test closure report?

Save to ▾
Show answer
A final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.
11

What is mobile app testing and what extra checks does it need?

Save to ▾
Show answer
Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.
12

An automated test passes on your laptop but fails in the CI pipeline. How do you troubleshoot?

Save to ▾
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.
13

Your test repository has many duplicate and outdated test cases. How do you clean it up?

Save to ▾
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.
14

What is decision table testing?

Save to ▾
Show answer
List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.
15

What is visual regression testing in automation?

Save to ▾
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.
16

SQL: find duplicate emails.

Save to ▾
Show answer
SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1;
17

SQL: find customers who placed more than three orders in the last 30 days.

Save to ▾
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;
18

What is a sprint planning meeting and what does QA contribute?

Save to ▾
Show answer
The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.
19

Verification vs validation?

Save to ▾
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).
20

What is cold start versus warm start, and why test app launch time?

Save to ▾
Show answer
A cold start launches the app from scratch when it is not in memory, loading the process and the first screen; it is the slowest. A warm start happens when the app process exists but the screen must be recreated, and a hot start just brings it to the foreground. Users abandon slow apps, so teams set targets, such as cold start under two seconds on a mid-range device, and measure each release for regressions.
21

What does the absence-of-errors fallacy mean?

Save to ▾
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.
22

What are the levels of testing?

Save to ▾
Show answer
Unit, integration, system and acceptance testing, moving from individual components to the complete product in front of users.
23

What sensitive data checks do you do in API responses and logs?

Save to ▾
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.
24

Write a Postman test script that checks the status is 201 and the response contains an id.

Save to ▾
Show answer
pm.test('Status is 201', function () { pm.response.to.have.status(201); }); pm.test('Response has id', function () { const body = pm.response.json(); pm.expect(body).to.have.property('id'); pm.expect(body.id).to.be.a('number'); });
25

A hotfix build arrives and you have only 15 minutes before deployment. How do you sanity check it?

Save to ▾
Show answer
Read the hotfix ticket to know exactly what changed. First verify the fix with the original reproduction steps and data. Then check the directly connected flows, for example if the fix is in coupon calculation, test applying, removing and paying with a coupon. Finish with a quick smoke of login and the main business flow. Report the result immediately, mentioning what was and was not covered.
26

A CAPTCHA on the signup page blocks screen reader users. What do you recommend?

Save to ▾
Show answer
Log it as a high-severity accessibility bug because it fully blocks a group of users from signing up. An image-only CAPTCHA fails WCAG unless an alternative is offered. Recommend options such as invisible or risk-based bot checks, an email or OTP verification step, an audio alternative plus another modality, and rate limiting on the server. Retest the full signup with NVDA and TalkBack after the change.
27

You notice full card numbers printed in the application logs. What do you do?

Save to ▾
Show answer
Treat it as a high-severity security defect, because storing full card numbers in logs breaks payment card security rules and creates a data leak risk. Do not copy the card numbers into the bug; use masked examples and the log location instead. Log the bug with restricted visibility and inform your lead and the security contact right away. After the fix, verify new logs are masked and confirm old logs are cleaned.
28

How do you test a web page using only the keyboard?

Save to ▾
Show answer
Put the mouse away. Press Tab and Shift+Tab to move through every link, button and field, and check that the order is logical and the focus outline is always visible. Use Enter and Space to activate buttons and links, arrow keys for menus, radio groups and sliders, and Escape to close dialogs. Check that nothing traps focus, hidden items do not receive focus and a skip to main content link works.
29

What is network condition testing for mobile apps?

Save to ▾
Show answer
It checks app behaviour on different networks: Wi-Fi, 4G, 5G, slow 2G or 3G, high latency, packet loss and no network. Also test switching between Wi-Fi and mobile data in the middle of an action, and airplane mode. The app should show loaders and clear offline messages, retry safely without duplicate actions and not freeze. Network throttling tools in developer options or proxy tools help simulate these conditions.
30

What should a tester verify about HTTPS on a website?

Save to ▾
Show answer
Check every page and API uses HTTPS, and plain HTTP redirects to HTTPS. Verify the certificate is valid, not expired, and matches the domain, with no browser warnings. Look for mixed content, where an HTTPS page loads scripts or images over HTTP. Check login and payment forms submit only over HTTPS and that cookies holding session data have the Secure flag.
31

What do you check when testing an API in Postman?

Save to ▾
Show answer
Status code, response body and schema, headers, response time, error messages for invalid input, authentication (401/403) and that data is saved in the database.
32

What is a test readiness review?

Save to ▾
Show answer
A test readiness review is a checkpoint before formal test execution starts, where the team confirms everything needed is in place. It checks that the build is deployed and smoke tested, the environment and test data are ready, test cases are reviewed and approved, access and tools work, and entry criteria are met. It prevents wasted days when execution starts and testers discover a missing service or empty database.
33

What is pairwise testing?

Save to ▾
Show answer
A technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most defects.
34

What is JSON schema validation in API testing?

Save to ▾
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.
35

How do you capture logs from an Android device for a bug report?

Save to ▾
Show answer
Enable developer options and USB debugging, connect the phone and confirm it is visible with adb devices. Clear old logs with adb logcat -c, reproduce the bug, then save logs with adb logcat -d > crash_log.txt, filtering by the app package or error level if needed. For a crash, search for FATAL EXCEPTION. Attach the log, device model, OS version, app version and a screen recording to the bug.
36

What is normalization and why should a tester understand it?

Save to ▾
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.
37

Why should we hire you as a manual tester over someone with more automation experience?

Save to ▾
Show answer
Answer with strengths and honesty. For example: I am strong at understanding requirements, designing test cases with techniques like boundary values and finding bugs through exploratory testing, which automation depends on to be useful. I also write SQL and test APIs in Postman. I am learning Playwright and have automated a few smoke tests, so I can grow into automation while adding value from the first week.
38

Why is orientation and screen size testing important?

Save to ▾
Show answer
Mobile users have many screen sizes, resolutions, notches and foldable screens, and they rotate their phones. Rotation can recreate the screen and lose entered data if not handled. Test portrait and landscape on key screens, small and large phones and tablets, and check text does not cut off, buttons stay reachable and the keyboard does not hide input fields. Check entered form data survives rotation.
39

What is accessibility testing?

Save to ▾
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.
40

What does Won't Fix mean and who decides it?

Save to ▾
Show answer
Won't Fix means the bug is acknowledged as real, but the team decides not to fix it, usually because the impact is very low, the feature is being retired or the cost of fixing is higher than the benefit. The decision is made by the product owner, often in triage with dev and QA leads. The tester should make sure the reason is recorded and, if user-facing, documented as a known issue.

Banking & finance companies (18)

Banking & finance

Goldman Sachs

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Hyderabad, Mumbai

View questions
Banking & finance

JP Morgan Chase

Software Testing interview questions

  • 40 questions
  • 5 rounds

Mumbai, Bengaluru, Hyderabad

View questions
Banking & finance

Morgan Stanley

Software Testing interview questions

  • 40 questions
  • 5 rounds

Mumbai, Bengaluru

View questions
Banking & finance

Barclays

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Chennai, Noida +1

View questions
Banking & finance

HSBC

Software Testing interview questions

  • 40 questions
  • 4 rounds

Hyderabad, Pune, Bengaluru

View questions
Banking & finance

American Express

Software Testing interview questions

  • 40 questions
  • 5 rounds

Gurugram, Bengaluru

View questions
Banking & finance

Wells Fargo

Software Testing interview questions

  • 40 questions
  • 4 rounds

Hyderabad, Bengaluru, Chennai

View questions
Banking & finance

Citi

Software Testing interview questions

  • 40 questions
  • 5 rounds

Pune, Chennai, Mumbai +2

View questions
Banking & finance

Deutsche Bank

Software Testing interview questions

  • 40 questions
  • 5 rounds

Pune, Bengaluru, Mumbai +1

View questions
Banking & finance

Standard Chartered

Software Testing interview questions

  • 40 questions
  • 4 rounds

Chennai, Bengaluru, Mumbai

View questions
Banking & finance

HDFC Bank

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Chennai, Bengaluru

View questions
Banking & finance

ICICI Bank

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Hyderabad, Chennai +1

View questions
Banking & finance

Kotak Mahindra Bank

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Bengaluru

View questions
Banking & finance

Axis Bank

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Bengaluru

View questions
Banking & finance

State Bank of India

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Navi Mumbai

View questions
Banking & finance

Fidelity Investments

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Chennai, Gurugram

View questions
Banking & finance

UBS

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Mumbai, Hyderabad

View questions
Banking & finance

BNY

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Chennai

View questions

Frequently asked questions

How are Software Testing interviews at banking & finance companies different?

Banks and financial-services firms hire for technology, analytics and QA in their global capability centres. Interviews mix technical rounds with domain questions on banking products, regulation, data quality and risk, and they value process discipline.

Which banking & finance companies are covered?

This page links to 18 banking & finance companies, including Goldman Sachs, JP Morgan Chase, Morgan Stanley, Barclays, HSBC, American Express, Wells Fargo, Citi. Each has its own page with rounds and a separate practice set.

What rounds should I expect?

Common rounds at these companies include: HR round; Managerial round; Technical round; Hiring manager round; Online assessment (aptitude + technical). The exact process varies by company and role.