D. E. Shaw Software Testing Interview Questions & Answers

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

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

Verifying the application works across different hardware, software and settings combinations.

SDLC is the full software development life cycle; STLC is the testing life cycle: requirement analysis, test planning, test design, environment setup, execution and closure.

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

A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.

Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.

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.

By business criticality, usage frequency, defect history, risk and dependencies, running high-priority cases first.

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.

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

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

Alpha is done in-house by internal teams before release; beta is done by a limited group of real users in their own environment.

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

Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.

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

Prioritising tests by the likelihood and impact of failure, so critical areas get the most coverage when time is limited.

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

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.

The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.

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

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

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.

Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.

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

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

Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.

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

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

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.

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

INNER returns matching rows, LEFT keeps all left rows, RIGHT keeps all right rows and FULL keeps all rows from both tables.

A human error causes a defect in the code, and when that defect is executed it produces a failure visible to users.

A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.

Re-testing existing features after a change. Automate stable, repetitive, high-value flows that run every release.

Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.

Break the work into modules and test cases, use past velocity or three-point estimation (optimistic, likely, pessimistic), add time for test data, environment issues, retesting and regression, and keep a risk buffer.

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

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.

Code is built and tested automatically on each change; tests are quality gates that stop faulty builds from moving forward.

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.

Scope (in and out), objectives, approach, environments, schedule, roles, entry/exit criteria, risks and mitigation, deliverables and tools.

A bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.

Test 17, 18, 19, 59, 60 and 61.

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

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

For a field accepting 1–100: valid class 1–100 (test 50), invalid below 1 (test −5), invalid above 100 (test 150). One value represents each class.

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