Interview Preparation
How to prepare for a Senior Business Analyst, Product Owner or payments SME interview at a large bank. This module is built around how interviews in payments actually work, not generic advice.
How payments interviews actually work
Interviewers at large banks do not ask you to recite definitions. They give you a situation and ask what you would do. A payment failed, a system went down, a stakeholder wants something impossible, a release is about to go wrong. They are testing whether you have done the work, whether you understand how money actually moves, and whether you can think clearly under pressure. Every answer should show the steps you take, the messages and systems involved, and the outcome you drive.
The four question types you will face
1. Situational technical questions. A payment is stuck, a response never arrives, an amount does not match. The interviewer wants your investigation steps, in order, naming the messages (pacs.008, pacs.002, pacs.004, camt.053, camt.056) and the systems (payment hub, core banking, clearing house, nostro). The Interview Ready Questions bank has 200 of these, with model answers.
2. System design questions. Design a payment integration, connect a channel to a hub, move a batch core to real time. Start from the business need, draw the flow, name the components, call out the failure modes and the controls. State your assumptions out loud before you design.
3. Behavioural questions. Tell me about a time you found a defect, handled a difficult stakeholder, or delivered under pressure. Use a simple structure: what happened, what you did, what the result was. Keep it to two minutes. Use real examples from your own work, never invented ones.
4. Bank operations questions. How a large bank organises payments, how treasury funds nostro accounts, how operations, engineering and the business work together. These test whether you understand the operating model, not just the messages.
A four week preparation plan
Week 1: Foundations. Work through the Essential Foundations questions and the core chapters on payments, settlement, clearing and ISO 20022. Be able to explain, in plain words, how a payment moves from instruction to beneficiary credit.
Week 2: End to end flows. Trace one domestic payment and one cross border payment hop by hop. Know every message, every system, and every status change. Practise explaining each flow out loud without notes.
Week 3: Exceptions and design. Work through the Exception Handling and System Design questions. For each scenario, write your answer, then compare it with the model answer. Practise the design questions by drawing the flow on paper first.
Week 4: Mock interviews. Answer 10 questions a day out loud, timed. Record yourself. Cut filler, tighten the structure, and make sure every answer names the message, the system, and the next step. Do a full mock with a peer if you can.
How to answer well
Start with the answer, then the reasoning. Give your conclusion in one sentence, then walk through the steps. Interviewers score structure as much as content.
Name the message and the system. Saying "I would check the pacs.002 for the RJCT reason code, then look at the hub logs" is far stronger than "I would investigate the failure". Specificity proves experience.
Always state the customer and operational impact. A good BA answer covers what the customer sees, what operations must do, and what the fix is, in that order.
End with prevention. After you fix the immediate problem, say what you would change so it does not happen again: a validation rule, a regression test, an alert, a process change.
What interviewers at large banks look for
They look for four things. First, domain depth: you understand payments end to end, not just one system. Second, structured thinking: you break a problem into steps and work them in order. Third, stakeholder sense: you know who owns what, and you communicate clearly with operations, engineering, treasury and the business. Fourth, ownership: you follow a problem through to the fix and the prevention, you do not hand it over and walk away.
Common mistakes to avoid
Do not recite textbook definitions when the question is situational. Do not say "it depends" without then giving a concrete answer. Do not blame another team. Do not invent experience you do not have; interviewers will probe it and it will collapse. Do not skip the prevention step; fixing the incident is only half the answer.
Where to practise
Interview Ready Questions (240 questions with model answers) · Test Series · Placement Test · Scenarios · Simulators