Transaction monitoring analyst: interview questions that reveal real experience

Victor Birjukov · 4 Nov 2026 · 7 min read

Ask for a real alert, start to finish: what they saw, what they checked and what was decided.
A good analyst writes a case file the compliance officer can act on; the compliance officer decides on reporting.
Test with a short anonymised case study and check references with someone who reviewed their work.

Hiring a transaction monitoring analyst for an EMI, payment institution or PSP? Most lists of transaction monitoring analyst interview questions test definitions, and any well-read candidate can recite those. This guide gives you questions that show whether someone has really worked alerts, and what good answers sound like.

What does a transaction monitoring analyst actually do?

The analyst reviews alerts from the monitoring system, investigates unusual activity and prepares a case for the compliance officer. The compliance officer decides whether to report to the financial intelligence unit. So the analyst's real output is a clear, documented case file. Our guide to hiring for AML compliance at an EMI or PSP shows where the role sits in the team and when you need it.

The EBA's Guidelines on ML/TF risk factors describe monitoring as checking that transactions are in line with the customer's risk profile. Firms set the frequency and intensity of monitoring on a risk-sensitive basis. They also decide which transactions to monitor in real time and which after the event, and whether monitoring is manual or automated. A good analyst knows where their alerts come from, not only how to close them.

Why do generic interview questions fail?

Many published question lists ask "What is transaction monitoring?" or "What is a red flag?". A candidate who has read a course book answers these well. A candidate who has cleared hundreds of alerts answers them no better.

Ask about things the candidate did, in order, with details. Strong candidates name the trigger, the data they pulled, the activity they expected from the customer and who signed off. Weak candidates stay general.

Which questions reveal real experience?

"Walk me through the last alert you escalated. What triggered it, what did you check and what did you write?" Listen for: the rule or scenario that fired, the customer's profile and history, any documents requested, and a clear conclusion. "It just looked suspicious" is a warning.
"Tell me about an alert you closed as a false positive. How did you justify closing it?" Listen for: a written reason another reviewer could follow. "The customer is known to us" is not a reason.
"How do you compare a transaction with what you expected from the customer?" Listen for: use of onboarding data, the stated purpose of the account and expected activity, and when they ask for that information to be updated.
"Several new beneficiaries receive round-amount transfers from one account within a few days. What do you do?" Listen for: looking at the wider pattern, linked accounts and source of funds before deciding. A quick block or a quick close without checks is a weak answer.
"Which monitoring tool have you used? Did you only work alerts or also help tune rules?" Listen for: a named tool, an example of a rule that created noise and what changed, and how the change was tested.
"How did you keep up when alert volumes rose?" Listen for: prioritising by risk, raising the backlog early and keeping the quality of case notes. Shorter notes to hit a target is a red flag.
"A customer asks why their payment is on hold while you investigate. What do you say?" Listen for: following the firm's procedure and the compliance officer's guidance, and care not to discuss the investigation with the customer.
"A reviewer challenges your case notes. How do you respond?" Listen for: openness to quality checks, the ability to defend a decision with evidence, and willingness to change it when the evidence says so.

Many of the same habits apply to KYC work. Our checklist for hiring an AML / KYC analyst for an EMI covers the CV and reference checks.

How do you test a candidate in practice?

A short case study tells you more than another interview round. Give the candidate an anonymised customer profile, a few months of transactions and one alert. Ask for a case note within a set time.

Mark it on three things. What did they check? Does the conclusion follow from the evidence? Could a compliance officer act on the note without asking follow-up questions? Never use real customer data in a test.

What are the red flags in a candidate?

They talk only about tools, never about customers or patterns.
They cannot explain why they closed an alert.
They treat every alert as a report, or every alert as noise.
Their work has never been reviewed or quality-checked.
They share customer details from a previous employer. That alone is a reason to stop.

Is the role changing under the new EU AML rules?

The EU's new Anti-Money Laundering Regulation (AMLR) sets rules on ongoing monitoring. In June 2026 the Anti-Money Laundering Authority (AMLA) opened a consultation on draft guidelines on the ongoing monitoring of business relationships under Article 26(5) AMLR. According to a summary by the law firm CMS, the draft allows manual, automated or semi-automated monitoring, as long as it is explainable, regularly tested and properly documented. CMS expected the final guidelines in Q4 2026.

For hiring, that points to analysts who can explain and document their decisions, not only clear queues. This describes draft guidance and is not legal advice. Check the final text with your compliance officer.

What to check

The candidate can walk through one escalated alert and one closed alert in detail.
Their case note from the practical test supports its own conclusion.
They can name the tool they used and say what, if anything, they changed in it.
They understand that the analyst prepares the case and the compliance officer decides on reporting.
A reference who reviewed their work, not only a colleague, confirms the quality of their files.
They answered the customer question without discussing the investigation.

How AfterWorc can help

You tell us the role and we send three matching profiles. You meet each candidate in a video interview before you decide. Pricing is a formula: the specialist's salary plus employer taxes plus a 10% AfterWorc margin. Fixed-price tasks carry a 5–8% fee, with funds held until you accept the work. Responsibility for your AML framework stays with your firm. Start a hiring request and tell us your alert volumes and tools.

FAQ

Is a transaction monitoring analyst the same as a KYC analyst? Not quite. KYC checks who the customer is at onboarding and in later reviews, while monitoring looks at what the customer does over time. In a small team one person often covers both, and the roles split as volumes grow.

Who decides whether to report a suspicious transaction? In the team structure we describe for EMIs and PSPs, the compliance officer decides, based on the analyst's case. The analyst's job is to make that case clear and complete. Your own procedures set the exact roles.

How many interview rounds do we need? One structured interview plus a short practical case study usually tells you more than several unstructured rounds. Add a reference call with someone who reviewed the candidate's work.

Should the analyst know how to tune monitoring rules? It is not essential for a junior analyst. But ask whether they have given feedback on noisy rules. It shows they think about why alerts fire, not only how to close them.

Sources

Hiring a transaction monitoring analyst? Tell us the role and get three matching profiles. Start hiring on AfterWorc. The first 10 business clients get €190 off their first hire and a free technical assessment.