How to prepare for the Revolut compliance live challenge

Revolut's hiring process is notoriously tough. For risk and compliance professionals, the 'Live Challenge' is where the interview loop actually gets real. Traditional behavioral interviews ask you to recount past experiences, but this challenge drops you straight into a simulated, high-pressure environment. You'll get a dense piece of regulatory text or a complex internal compliance scenario. Your job? Analyze it, map out the obligations, and make a definitive business decision. Oh, and you'll do all of this while the interviewer watches your screen, evaluating your thought process in real time.

This round tests exactly how you operate under conditions that mimic a hyper-growth fintech. Legacy banks might give their compliance teams six months to interpret a regulatory update and draft a policy. Revolut expects you to do it in a two-week sprint while working directly inside a product pod. Their compliance teams simply can't afford to act as bottlenecks; they have to be business enablers who deeply understand risk. Passing requires a lot more than basic regulatory knowledge. You'll need a highly structured approach to problem-solving, the ability to communicate clearly under pressure, and a firm grasp of frameworks that let you break down pure ambiguity into actionable engineering and operational steps.

Where the live challenge fits in the Revolut hiring loop

Before we break down the mechanics of the live challenge itself, you need to know where it sits within the broader interview process. The compliance manager and risk interview loops at Revolut typically follow a standardized path. That said, the exact ordering can occasionally vary based on your seniority and region. The live challenge acts as the ultimate filter before the final behavioral rounds.

The 60-minute live challenge structure and timing

You can expect the live challenge to be a 60-minute video call with one or two senior members of the compliance or risk team. They'll share a document with you, often via Google Docs or a similar collaborative tool, and ask you to share your screen while you work through it. Time management is absolutely your biggest enemy here. Candidates fail because they get bogged down in legal definitions and run out of time to provide business solutions. A successful candidate usually structures their hour like this:

1. Minutes 0-5: Introductions, context setting, and reading the prompt. Clarify any immediate logistical questions here.
2. Minutes 5-20 (Part 1 - The Breakdown): Silent or semi-vocal reading of the regulatory text/scenario. You should be actively typing a skeleton structure, taking notes, and mapping out the core obligations on the shared document.
3. Minutes 20-40 (Part 2 - The Solution): Evaluating the specific compliance decision, structuring your argument, and presenting your findings. This is where you outline the operational, technical, and policy changes required.
4. Minutes 40-55 (Part 3 - The Pushback): The interviewers will act as product managers or business leaders. They will challenge your restrictions, complain about lost revenue, and ask for workarounds. You must defend your decisions and negotiate a compliant path forward.
5. Minutes 55-60: Wrap up, final summary, and your opportunity to ask them questions.

Example Scenario: The Crypto Margin Lending Case

To understand how to tackle the challenge, let's look at a highly realistic mock scenario. Imagine you are handed a one-page document detailing a new product launch: Revolut wants to offer crypto margin lending to retail customers in a Tier-2 European market. The document includes a heavily redacted, newly drafted regulation from the local financial authority stating that 'all leveraged digital asset products must ensure retail participants do not risk more than 10% of their verified liquid net worth, and providers must maintain real-time liquidation protocols to prevent negative balances.'

The prompt asks: 'The Product team wants to launch this feature in three weeks. What are the compliance requirements, and what is your go/no-go decision?'

A weak candidate will immediately start talking about how risky crypto is and say the timeline is impossible. A strong candidate will stay calm, create four headings in the Google Doc, and begin categorizing the specific requirements needed to actually build the product legally.

How do I map regulatory obligations under time pressure?

In Part 1 of the challenge, you must distill heavy legal jargon into clear operational requirements. To succeed, you absolutely must use a MECE (Mutually Exclusive, Collectively Exhaustive) framework. Don't just list random thoughts as they pop into your head. Instead, categorize the regulatory text into distinct operational buckets. A highly effective framework for compliance mapping is the 'O-P-T-R' model. Here is how you would apply it to the crypto margin lending scenario right on your shared screen:

• Operations: What changes need to happen in the day-to-day processes? (e.g., Customer support agents need new scripts for handling margin call complaints. We need a manual review queue for users whose net worth verification fails automated checks).
• Policy: What internal documents need to be rewritten? (e.g., The Global Credit Risk Policy needs an addendum for digital assets. The Terms of Service must be updated to include negative balance liquidation clauses).
• Technology/Product: What engineering tickets need to be raised? (e.g., We need an API integration to verify liquid net worth during onboarding. We need a real-time liquidation engine that triggers the moment a user's margin health drops below the threshold).
• Reporting: What new data needs to be captured? (e.g., The MLRO needs a daily dashboard showing total leveraged exposure, and we need a monthly report for the local regulator detailing any negative balance incidents).

By structuring your notes into these four buckets, you immediately show the interviewer something important. You prove you understand exactly how compliance impacts the wider business. You are speaking the language of product managers (API integrations, engineering tickets) rather than just quoting the law back to a lawyer.

How do I evaluate a compliance decision during the live case?

Part 2 usually shifts gears from theory to practice. You might be asked to look at a documented decision made by a junior analyst. For example, the prompt might show that a 22-year-old FinCrime analyst approved the onboarding of a high-net-worth individual residing in the UAE, whose primary source of wealth is listed as 'crypto trading.' The analyst approved the account based on a single screenshot of a Binance wallet and a local utility bill. You are asked, 'Did they make the right call?'

This is where you should use an Issue Tree to structure your evaluation. Start with the core question—was this the right decision?—and break it down into logical branches.

• 1. Inherent Risk: Assess the baseline risk before controls. The geography (UAE) is often categorized as high-risk for money laundering. The product/source of wealth (Crypto) is inherently high-risk. Therefore, the inherent risk profile of this user is Severe.
• 2. Controls Applied: Evaluate what the analyst actually did. They accepted a screenshot of a wallet. This is a weak control. Screenshots can be trivially forged using browser developer tools. They did not request blockchain analytics to verify the source of funds, nor did they conduct adverse media screening.
• 3. Residual Risk: Subtract the controls from the inherent risk. Because the controls were entirely inadequate, the residual risk remains Severe, which sits far outside Revolut's standard risk appetite.

If you spot a mistake made by the analyst, don't just point it out and stop talking. A strong candidate immediately pivots to remediation. State exactly what you'd do next: 'First, I would restrict the account immediately to prevent any outbound fiat transfers. Second, I would file an internal Suspicious Activity Report (SAR) for the MLRO to review. Third, I would require the user to provide a cryptographic signature proving ownership of the wallet, alongside tax returns verifying the trading income. Finally, I would review the junior analyst's previous 20 cases to check if this is an isolated error or a systemic training gap.'

Navigating interviewer pushback and stress testing

Around the 40-minute mark, the interviewers will intentionally turn up the heat. They will roleplay as aggressive business stakeholders. If you tell them the crypto margin product cannot launch in three weeks because the API verification tools aren't built, they will push back. They might say, 'The CEO has already promised this to investors for Q3. We have spent $2M on marketing. If we delay, we lose our competitive advantage. Are you really telling me we have to scrap the launch?'

Do not fold, but do not be a brick wall. This is a test of your commercial awareness and negotiation skills. The correct approach is to find a compliant path to 'yes'. Instead of saying no, offer a risk-managed alternative.

You should respond with something like: 'I understand the commercial pressure, but launching fully without the net-worth verification API breaches the local regulation and risks our operating license. However, we don't have to scrap the launch. We can launch on time to a closed beta of 5,000 existing Revolut Metal customers who have been with us for over three years, where we already have verified income data on file. This allows marketing to announce the launch, lets product gather user feedback, and buys engineering the necessary three weeks to build the API for the wider public rollout.'

What if I don't know the specific local regulation?

Candidates often panic when handed a regulation from a jurisdiction they've never worked in. Revolut actually does this intentionally. They aren't testing your encyclopedic knowledge of the Monetary Authority of Singapore's (MAS) exact rulebook versus the UK's Financial Conduct Authority (FCA). Instead, they're testing your fundamental understanding of risk principles.

If you hit an unfamiliar term or a weird local nuance, just state your assumption clearly and keep moving. Use global standards like the Financial Action Task Force (FATF) guidelines as your safety net. For example, you could say: 'I'm not intimately familiar with this specific local clause regarding corporate shell structures, but based on standard FATF guidelines, I will assume this requires us to identify the Ultimate Beneficial Owner (UBO) down to a 25% threshold. Operating under that assumption, here is how I would design the onboarding flow.' Handling it this way demonstrates confidence, adaptability, and a solid grounding in global compliance standards.

Structuring your communication and thinking out loud

The live challenge tests your communication just as much as your technical compliance skills. Revolut heavily values brutal clarity and speed. When presenting your findings, avoid long, winding narratives at all costs. Never start your sentences with 'Well, it depends...' Instead, use the 'What, So What, Now What' framework to deliver your conclusions.

• What: State the core finding in one sentence. (e.g., 'The new regulation requires us to hold an additional 5% capital buffer for crypto assets.')
• So What: Explain the business impact immediately. (e.g., 'This means our current crypto lending product will become significantly less profitable, and we may breach our internal capital limits by Q3.')
• Now What: Give a concrete, actionable recommendation. (e.g., 'We need to pause new crypto lending immediately and convene a risk committee tomorrow morning to reassess the product's pricing model.')

Fatal mistakes that will instantly cost you the offer

Even highly experienced compliance officers fail this interview because they treat it like a traditional banking assessment. Here are the four most common traps that will result in an immediate rejection:

• Playing 'Dr. No': If your default answer to every new product idea is 'we can't do this because of risk,' you will fail. Fintechs require compliance to find solutions, not just identify roadblocks.
• Ignoring the Commercial Reality: If you suggest a control that would cost $5 million to build in order to mitigate a $10,000 risk, you show a lack of commercial awareness. Controls must be proportionate to the risk.
• Freezing in Silence: It is normal to need a minute to read, but if you spend 15 minutes staring at the screen in silence without typing or narrating your thought process, the interviewer has nothing to grade. Think out loud.
• Failing to Escalate: If the scenario involves a blatant breach of law or internal fraud, and your solution is to 'monitor the situation,' you will fail. You must know when a situation requires immediate escalation to the MLRO or legal counsel.

Key compliance competencies and values Revolut is grading

Throughout the entire 60 minutes, the interviewers are silently scoring you against Revolut's core values. 'Never Settle' means they want to see you push for the absolute highest standard of compliance rather than just scraping by with the bare minimum. If a regulation says you must review accounts annually, a 'Never Settle' candidate suggests building an automated trigger-based review system that flags high-risk activity in real-time.

'Get It Done' means they're looking for practical, implementable solutions, not just dry, academic legal analysis. They want to see that you can take a complex legal requirement and turn it into a step-by-step project plan that a team of software engineers can actually code.

Ultimately, the live challenge is about proving you can thrive in ambiguity. You won't have all the facts. You won't have weeks to deliberate. You will have to make hard decisions based on incomplete data, document your rationale clearly, and defend your stance against aggressive pushback. If you can master the O-P-T-R framework, structure your arguments with Issue Trees, and always maintain a commercial mindset, you will stand out from the vast majority of candidates.