Business analyst interview questions in UK financial services, and how to answer them
The shape of a good interview answer
- Situation, in one sentence
- What you personally did
- What changed as a result
- Evidence you could show
Interviewers in banks, insurers and payments firms rarely want a textbook definition. They want to hear what you did on a real piece of work and how you know it worked. A good answer names a situation, a decision, a result and a piece of evidence you could show them.
This article covers the questions that come up most, what each is testing, and how to build an answer. The firm in the examples, Northgate Bank, is fictional.
Last reviewed: October 2026.
The shape of a good answer
For experience questions, use a short structure: the situation in one sentence, what you personally did, and what changed as a result. Then add evidence: a document, a number, a date, a name of a role. If you cannot show evidence, say so and describe how you would have known.
Keep answers to about two minutes. Stop, and let them ask.
Questions and what they test
| Question | What the interviewer is checking | What to include |
|---|---|---|
| "Tell me about a requirement that changed late." | If you control change or are carried by it | The change, who asked, how you recorded it and what you told the team |
| "How do you handle two stakeholders who disagree?" | Judgement and nerve | How you found the facts, who had authority to decide, and what you wrote down |
| "Walk me through how you would start on a new assignment." | If you have a method | Stakeholders, documents, a decisions log, questions to ask in week one |
| "How do you know a requirement is testable?" | If you think past the document | An acceptance criterion with a value, a state or a message in it |
| "Describe a time you found an error in a source document." | Attention to detail and honesty | How you spotted it, who you told, what happened to the document |
| "What would you do if the sponsor wants it faster?" | How you deal with pressure | What you would cut or defer, and what you would put in writing |
| "How do you work with developers and testers?" | Collaboration | A specific example, such as walking the tester through criteria before build |
| "What do you know about payments / KYC / regulatory reporting?" | Domain honesty | What you know, what you have worked on, how you learn the rest |
| "How do you use AI in your work?" | If you are safe and accountable | Firm's rules first, nothing confidential pasted, every claim checked against a source |
Starter, £30 (41 files, discovery to a tested set of requirements) · Complete, £80 (59 files, adds governance and assurance). Prices include UK VAT: Starter £25 + VAT, Complete £66.67 + VAT. Payhip may show the price before VAT. One payment, no subscription.
Sold by Quantum Sphere Consulting Limited; your statutory rights apply.A worked answer
Question: "Tell me about a time you found a contradiction in the requirements."
A weak answer: "There were conflicting documents so I got everyone together and we resolved it."
It says nothing you can check. A stronger version, from the invented Northgate case:
"On a settlements project, three documents gave three different cut-off times: 15:00 in the operations procedure, 15:30 in the scheme document and 16:00 in an old email. I listed all three in a source register with the date and owner of each. I took the list to the head of operations and the compliance manager, because they were the two people who could decide. They confirmed 15:30 and agreed the email was out of date. I logged the decision with their names and the date, updated the requirement, and asked for the old procedure to be corrected. The test team then wrote their cases from the confirmed time."
Notice what it contains: three dated sources, two named roles, a recorded decision and a downstream effect. It does not claim that everything went perfectly, and it does not use a number it cannot support.
Questions about the domain
You will not be expected to know everything. You are expected to be honest about it and to show how you learn.
Typical questions: What happens between a payment being initiated and it settling? What is KYC and why does the business care? What does a regulatory change programme need that an ordinary change does not?
A good approach is to state what you have direct experience of, then describe the process in plain language, then name what you would check. For example: "I have worked on onboarding rather than payments, so I would want to confirm the settlement cycle with the operations team before I wrote anything down. In outline, the instruction is validated, sanctions-screened, sent to the scheme and confirmed back. I would map each step and ask who owns each one."
Do not bluff. An interviewer who knows the area will find the edge of your knowledge within two questions, and a confident wrong answer costs more than an honest gap.
Assessment-centre exercises
Many firms set a timed case: you receive a few documents and thirty minutes to produce requirements, questions or a process map. What they are looking for is mostly the same as in the interview:
- Did you notice where the documents disagree?
- Did you separate what is stated from what you are assuming?
- Did you ask good questions rather than invent answers?
- Could someone else pick up your output and use it?
Spend the first five minutes reading and listing questions before you write anything. Mark assumptions as assumptions.
Questions to ask them
Prepare three or four real questions. Examples that show you have thought about the work:
- Who signs off requirements here, and how long does that usually take?
- How do business and delivery teams work together on acceptance criteria?
- What was the last change that went wrong, and what did you learn from it?
- What would a good first month look like for this role?
Before the day
- Choose four pieces of work you can talk about in detail, and write down the evidence for each.
- Rehearse out loud once, with a timer.
- Read the job description and mark the three things they care about most.
- Check what the firm does and who it serves.
- Prepare one example where something went wrong and what you changed.
If you are a career changer, use work from outside BA where the skills match, and say clearly that it is from another setting. Do not invent project experience.
What to do next
Write out your answer to "Tell me about a requirement that changed late" using the structure above and time it. If it runs over two minutes, cut the background.
The Starting Out or Returning to BA pack includes a 40-question bank with answer frameworks, an evidence and STAR story planner and four timed case exercises.