Goldman Sachs Software Testing Interview Questions & Answers

Reproduce and assess impact, inform stakeholders, help developers fix and verify in staging, run regression and check monitoring after the hotfix, then do a post-mortem.

The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.

Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.

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.

The observation that a small number of modules contain most defects, so testing should focus on those areas.

Evaluating how easy and pleasant a product is to use by observing real users complete tasks and noting confusion.

Moves to the chosen floor, doors open and close, door sensor stops closing on obstruction, overload alarm, emergency button, behaviour in a power cut, max capacity and the floor display.

User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.

Valid keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.

200 OK, 201 Created, 204 No Content, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Internal Server Error.

A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.

Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.

JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.

Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.

The hardware, software, data and configuration where testing happens, set up to mirror production as closely as practical.

Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.

Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.

Smoke tests run on every build for quick feedback; full regression runs less often, such as nightly or before release.

A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.

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.

New → Assigned → Open → Fixed → Retest → Verified → Closed, with Reopened, Rejected, Deferred and Duplicate as side paths.

Shift left with early reviews, improve test design, automate regression, use better test data, add monitoring and learn from escaped defects.

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.

Check access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.

The extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

DELETE removes selected rows and can be rolled back; TRUNCATE quickly removes all rows and resets the table.

Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.

Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.

A clear title, steps to reproduce, expected vs actual result, environment/build, severity and priority, and evidence (screenshot, video, logs).

A grid mapping requirements to test cases and defects, proving every requirement is tested.

Test execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.

Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.

Smoke testing checks that the critical features of a new build work (broad and shallow). Sanity testing checks that a specific fix or area works after a change (narrow and deep).

A technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most defects.

Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.

Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.

Testing how a system moves between states based on events, for example an order going from placed to paid to shipped to delivered.

A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.

Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.

Valid card and PIN, wrong PIN, three failed attempts, amount above balance, amount above daily limit, invalid denomination, machine out of cash, network failure and receipt printing.

Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.

A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.

Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.

Static testing reviews documents and code without executing; dynamic testing executes the software to observe behaviour.

State the problem, location and condition briefly, for example 'Checkout button disabled after applying a coupon on the cart page'.

Peer review for clarity, coverage of requirements, correct expected results, test data and traceability, then update and baseline them.

Check SQL injection, brute-force lockout, password masking, session timeout, HTTPS, cookie flags, error messages not revealing users and password reset flow.

Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.

Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.

Success, failure and pending flows, timeouts, refunds, double-click payments, every method (UPI, cards, net banking), rounding, security (no card data stored) and reconciliation with bank reports.

A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.