Companies / Banking GCCs
Banking GCCs practice pack
BFSI and fintech tech. 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.
Skills this role is usually tested on
- Payments and ledger testing
- Regulatory and audit evidence
- Test data privacy
- API and batch testing
- Production support
Business areas used for scenarios
- retail banking
- payments
- capital markets
- risk and compliance
6 questions
Answer out loud first, then open the guide. Most people read the guide too early.
- 1
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?
hardPaymentsA strong answer covers
Transaction states, reversal and retry rules, reconciliation between ledger and network, timeouts, idempotency, notification, and an audit trail to explain each state.
- 2
How do you prove that debits equal credits after a complex batch?
hardLedgerA strong answer covers
Independent reconciliation query or report, control totals, rerun safety, rounding rules, and checks on every account touched, not a sample only.
- 3
What evidence does an auditor expect from your testing?
mediumComplianceA strong answer covers
Traceability from requirement to test to result, approvals, environment and build identifiers, defect history, and retained logs. Evidence is created while testing, not afterwards.
- 4
You need production-like data for a test. What are the rules?
mediumDataA strong answer covers
No real customer data in lower environments unless masked under policy, referential integrity kept after masking, synthetic data for edge cases, and access logged.
- 5
How do you test an open-banking style consent API?
mediumAPI testingA strong answer covers
Consent scope, expiry and revoke, token and permission checks, rate limits, error codes, and that revoked consent stops data access immediately.
- 6
A downstream core-banking system is slow. What should the customer-facing journey do and how do you test it?
hardResilienceA strong answer covers
Timeouts, circuit breaker, clear user messaging, no duplicate submission, safe retry, and tests that inject latency and failure.
Now say it to an interviewer
Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.