Skip to content

Tower Research Capital Software Testing Interview Questions & Answers

Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.

About Tower Research Capital hiring for Software Testing roles

Tower Research Capital is a quantitative trading firm that develops automated, high-frequency trading strategies across global markets. Its Gurugram office works on trading systems, low-latency software, infrastructure and quantitative research. It hires in India for software engineers, quantitative researchers and traders, with interviews that focus heavily on problem solving, probability and systems.

For Software Testing roles, this Tower Research Capital practice set focuses most on Agile, SQL and API Testing (10), Test Case Design (6), Mobile Testing (5), Bug Life Cycle and Jira (5). It has 1 easy, 35 medium, 4 hard questions, so you can start easy and work up to the harder ones.

Company type
Fintech
Headquarters
New York, USA
Main India offices
Gurugram

Tower Research Capital Software Testing interview process

  1. Online assessment (coding + quant)
  2. Technical round 1 (DSA)
  3. Technical round 2 (C++ or systems)
  4. Quant or probability round
  5. HR round

Typical pattern based on public candidate experiences. Rounds vary by role, team and year.

Solved for Tower Research CapitalStart 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 a mobile app when the device storage is almost full?

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

How do you write test cases when only wireframes are available and the UI is not ready?

Save to ▾
Show answer
Use the wireframes and the user story as the test basis. Write test scenarios and high-level cases for the flows, field validations, navigation and error states shown in the design. Note open questions, such as missing empty states or error messages, and clarify them with the designer. Keep exact UI text and steps light so they are easy to update. Once the build arrives, refine the cases and add any missing details.
03

How do you test an API using Postman?

Save to ▾
Show answer
Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.
04

Write test cases for an online money transfer.

Save to ▾
Show answer
Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.
05

SQL: find orders whose total does not match the sum of their order items.

Save to ▾
Show answer
SELECT o.order_id, o.total_amount, SUM(i.quantity * i.unit_price) AS items_total FROM orders o JOIN order_items i ON i.order_id = o.order_id GROUP BY o.order_id, o.total_amount HAVING o.total_amount <> SUM(i.quantity * i.unit_price);
06

How do you test a REST API with authentication?

Save to ▾
Show answer
Check access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.
07

SQL: verify that soft-deleted users do not appear in the active users list.

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

What are ACID properties and how can a tester check them?

Save to ▾
Show answer
ACID means Atomicity, Consistency, Isolation and Durability. Atomicity: a transfer that debits one account must also credit the other, or neither happens; test by forcing a failure midway. Consistency: constraints still hold after the transaction. Isolation: two users updating together do not see each other's half-done work; test with two sessions. Durability: committed data survives a restart; test by committing, restarting the service and querying again.
09

What is shift-left testing and why is it cheaper?

Save to ▾
Show answer
Shift-left means starting testing activities earlier in the life cycle: reviewing requirements, joining design discussions and writing tests before code is complete. A defect found in requirements may cost a short conversation to fix, while the same defect found in production may need a hotfix, data correction and customer support. Testers shift left by asking questions in grooming, defining acceptance criteria and reviewing designs.
10

How do you plan testing for a two-week sprint?

Save to ▾
Show answer
In sprint planning, review each story's acceptance criteria and estimate test effort, including test data and regression. Write test cases in the first days while development starts. Ask for early builds so testing is spread across the sprint, not crowded at the end. Keep time for regression and bug retesting in the last two or three days. Track progress on the board and raise risks in stand-up.
11

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.
12

What are the characteristics of a good test case?

Save to ▾
Show answer
Clear, concise, independent, repeatable, traceable to a requirement, with precise expected results and tested data.
13

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.
14

What is a bug triage meeting?

Save to ▾
Show answer
A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.
15

What is API testing and why is it important?

Save to ▾
Show answer
Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.
16

Search works fine in QA but is very slow in production. Could a missing database index be the reason, and how do you check?

Save to ▾
Show answer
Yes, very likely. An index lets the database find rows quickly, like the index of a book. With a small QA table, a full table scan is still fast, but with millions of production rows it becomes slow. Compare indexes on the searched columns in both environments and ask a developer to check the query plan. Test key queries on production-size data in staging, and include data volume in future performance checks.
17

Tell me about a time you found an important bug that others missed.

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

Write SQL to verify an order was saved correctly.

Save to ▾
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123'; -- compare with the UI, then check the matching rows in order_items
19

Why are stable locators like data-testid or roles preferred over position-based XPath?

Save to ▾
Show answer
A position-based XPath such as /html/body/div[3]/div[2]/button breaks whenever a developer adds a wrapper div or reorders the layout, even though the feature still works. That creates false failures and maintenance work. Locators based on a dedicated data-testid attribute or the accessible role and name, like a button named Submit, stay valid through design changes and describe intent clearly. Testers should ask developers to add test IDs.
20

How do you test battery and memory usage of a mobile app?

Save to ▾
Show answer
Run typical user sessions on a real device and measure battery drain, CPU and memory with platform profiling tools or the device's battery statistics. Compare with the previous version. Look for background work continuing after the app is closed, GPS left on, frequent network polling and memory that keeps growing, which signals a leak. Test on low-RAM devices too, where the OS kills heavy apps quickly.
21

How would you test a feature that is enabled for only 10 percent of users through a feature flag?

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

What goes into a test plan?

Save to ▾
Show answer
Scope (in and out), objectives, approach, environments, schedule, roles, entry/exit criteria, risks and mitigation, deliverables and tools.
23

When should you reopen a bug and when should you log a new one?

Save to ▾
Show answer
Reopen the bug when the same issue, with the same steps and expected result, still fails after the fix. Log a new bug when the fix works but a different problem appears, even in the same screen, or when the original bug has already been closed in a past release. Link the new bug to the old one. Mixing different problems in one reopened ticket confuses tracking and metrics.
25

SQL: check that no user has more than one active subscription.

Save to ▾
Show answer
-- Business rule: at most one ACTIVE subscription per user SELECT user_id, COUNT(*) AS active_count FROM subscriptions WHERE status = 'ACTIVE' GROUP BY user_id HAVING COUNT(*) > 1; -- Expected result: no rows
26

How do you write a good bug title?

Save to ▾
Show answer
State the problem, location and condition briefly, for example 'Checkout button disabled after applying a coupon on the cart page'.
27

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.
28

How do you test a database trigger?

Save to ▾
Show answer
First read what the trigger should do and when it fires, such as AFTER UPDATE on the salary column writing a row to an audit table. Then perform the event that should fire it and query the target table to confirm the expected row and values. Also perform events that should not fire it and confirm nothing happens. Check multi-row updates, NULL values and rollback: if the main statement fails, the trigger's changes must not remain.
29

How do you chain requests in Postman by passing a token from login to the next call?

Save to ▾
Show answer
// Tests tab of the Login request const body = pm.response.json(); pm.environment.set('authToken', body.token); // Next request header: // Authorization: Bearer {{authToken}} // Postman replaces {{authToken}} with the saved value
30

What is the difference between a defect and a production incident?

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

What are latent defects and masked defects?

Save to ▾
Show answer
A latent defect exists in the software but has not caused a failure yet because the needed conditions have not occurred, such as a leap-year bug that appears only on 29 February. A masked defect is hidden by another defect, for example a broken discount calculation you cannot reach because the cart page crashes first. After the first bug is fixed, the masked one appears, which is one reason regression and retesting matter.
32

What metrics do QA teams track?

Save to ▾
Show answer
Test execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.
33

Notifications arrive late, and some screens look broken, only on certain Android phone brands. Why can this happen and what do you test?

Save to ▾
Show answer
Android phone makers ship their own skins and settings on top of Android, so the same app can behave differently. Common problems are aggressive battery savers that kill background tasks and delay notifications, different permission screens, custom fonts and display scaling, camera differences and modified WebViews. Pick devices from the brands most used by your audience and test background work, notifications, camera and layout on each.
34

How do you test zoom, text resizing and reflow?

Save to ▾
Show answer
Set browser zoom to 200 percent and check that all text is readable and no content or buttons are cut off. Then zoom to 400 percent, or use a 1280 pixel wide window, which gives a 320 CSS pixel viewport; content should reflow into one column without horizontal scrolling, except for things like data tables and maps. Also increase text spacing and the operating system font size to check that labels do not overlap.
35

What is a duplicate bug and how do you avoid logging one?

Save to ▾
Show answer
A duplicate bug is a new report for a problem that is already logged. Before raising a bug, search the tracker by key words, module, error message and recent open bugs, and ask teammates working on the same area. If a similar bug exists, add your extra information, such as another browser or data set, as a comment instead of a new ticket. This keeps the backlog clean and saves triage time.
36

Write test cases for live order tracking in a food delivery app.

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

A training portal is adding recorded video lessons and podcasts. What accessibility checks do you run?

Save to ▾
Show answer
Check that prerecorded videos have accurate, synchronised captions, not just auto-generated ones with errors, and that audio-only content like podcasts has a transcript. Important visual information that is not spoken should have audio description or be covered in the transcript. Media should not autoplay with sound, and player controls must work by keyboard and be announced by screen readers. Also check that nothing flashes more than three times per second.
38

What is a Three Amigos session?

Save to ▾
Show answer
Three Amigos is a short meeting where a business person or product owner, a developer and a tester discuss a story before development. The business explains the need, the developer considers how to build it and the tester asks what could go wrong and how it will be verified. The output is clear acceptance criteria and example scenarios. It prevents misunderstandings and reduces bugs found late.
39

Write test cases for a shopping cart.

Save to ▾
Show answer
Add, remove, update quantity, price and tax calculation, coupon codes, stock limits, cart persistence after login and checkout navigation.
40

A bug fix was made in the payment module. How do you decide the regression scope?

Save to ▾
Show answer
Ask the developer which code, services and database tables changed. Map them to impacted flows: all payment methods, refunds, partial payments, failed payment retries, invoices and order status updates. Add high-risk areas from past defects and anything that calls the same service. Run full payment regression because the business risk is high, plus a smoke test of the rest of the application before release.

Tips to crack the Tower Research Capital Software Testing interview

  • Practise probability puzzles, expected value and brain teasers, which are common in quant trading interviews.
  • For developer roles, revise C++ deeply, including memory management, templates and low-latency coding practices.
  • Learn the basics of order books, market making and latency so you can discuss how trading systems work.
  • 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; Tower Research Capital interviewers usually ask follow-ups on your first answer.

Frequently asked questions

How many rounds are there in the Tower Research Capital Software Testing interview?

Candidates usually go through 5 stages: Online assessment (coding + quant); Technical round 1 (DSA); Technical round 2 (C++ or systems); Quant or probability 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 Tower Research Capital Software Testing interview?

This practice set leans on Agile, SQL and API Testing (10), Test Case Design (6), Mobile Testing (5), Bug Life Cycle and Jira (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Tower Research Capital interviewers ask you to walk through real work.

Are these the exact questions asked at Tower Research Capital?

No. These are curated practice questions that match the skills and difficulty usually tested in fintech interviews like Tower Research Capital's. They are not a leaked or verified list of past questions.

Where does Tower Research Capital hire Software Testing professionals in India?

Tower Research Capital has large teams in Gurugram. Openings and locations change often, so check the Tower Research Capital careers page and filter by city and experience.

Software Testing questions for similar companies