BFSI and fintech tech
Banking GCCs
Global capability centres of banks: controls, regulation, and resilient automation.
These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.
What they tend to probe
- Payments and ledger testing
- Regulatory and audit evidence
- Test data privacy
- API and batch testing
- Production support
Question 1 · Payments · Hard
A customer says money left their account but the beneficiary has not received it. What do you test and what do you check in production?
Answer guide
Transaction states, reversal and retry rules, reconciliation between ledger and network, timeouts, idempotency, notification, and an audit trail to explain each state.
Question 2 · Ledger · Hard
How do you prove that debits equal credits after a complex batch?
Answer guide
Independent reconciliation query or report, control totals, rerun safety, rounding rules, and checks on every account touched, not a sample only.
Question 3 · Compliance · Medium
What evidence does an auditor expect from your testing?
Answer guide
Traceability from requirement to test to result, approvals, environment and build identifiers, defect history, and retained logs. Evidence is created while testing, not afterwards.
Question 4 · Data · Medium
You need production-like data for a test. What are the rules?
Answer guide
No real customer data in lower environments unless masked under policy, referential integrity kept after masking, synthetic data for edge cases, and access logged.
Question 5 · API testing · Medium
How do you test an open-banking style consent API?
Answer guide
Consent scope, expiry and revoke, token and permission checks, rate limits, error codes, and that revoked consent stops data access immediately.
Question 6 · Resilience · Hard
A downstream core-banking system is slow. What should the customer-facing journey do and how do you test it?
Answer guide
Timeouts, circuit breaker, clear user messaging, no duplicate submission, safe retry, and tests that inject latency and failure.