Why the role exists

Onboarding a client currently takes weeks. Most of that is manual work that exists because our criteria aren't written down anywhere an analyst or a script can use them.The job is to write them down, work the queue yourself while you learn where it breaks, and automate as much of it as possible from there. Within a year we'd expect most low-risk cases to clear without anyone touching them.

Responsibilities

• Productise the process, run it, then automate it. We want someone hands-on, not someone who writes requirements and waits two quarters for engineering capacity.Productise. Turn the AML policy and the business-wide risk assessment into onboarding criteria, screening thresholds, monitoring rules and escalation triggers that give the same answer whoever applies them. Same for the monitoring volume thresholds, exception policy, offboarding process and override justification rules.
• Run it yourself. KYB collection, refresh and remediation outreach to a published SLA. Triage screening and transaction monitoring, false-positive clearing against the rulebook you wrote. Evidence packs the MLRO can decide on first time. Banking questionnaires, counterparty information packs, MI, audit evidence and the quarterly board pack.
• Automate responses, process, screening and anything that is time-consuming.
• Build what you can yourself. Scripts, low-code, AI tooling, we don't mind how, as long as it's documented and holds up under audit.
• Stay aligned with the Group MLRO. Everything you write gets signed off, dated and auditable, and gets revisited as policy, appetite and jurisdictions change.

• KPIsKYB submission to trading-ready, under 24 hours for low and medium risk. Currently weeks.
• Percentage of alerts cleared by rule rather than by hand.
• Percentage of cases the MLRO can decide on without asking for more information.

• Who you areWe don't expect a perfect candidate, and this mix is unusual to ask for.A systems thinker. You look at a slow process and see the decisions, handoffs and missing rules that make it slow, then rebuild it rather than adding another checklist on top.
• Operations experience somewhere small enough that you built the process rather than inherited it.
• AI native. You reach for AI before you reach for headcount or a ticket, and you've built working things with it. Side projects and scrappy internal tools count.
• Able to push back when commercial pressure says move faster, but also articulate to the rest of the Compliance team why we don't need an extra process or policy.

How we work

We have five values, and we use them in check-ins, reviews, and hiring. You'll be asked about them at interview, so here is what they mean for this role.Truth over comfort. Say the process is broken while people are still defending it. That applies to your own work once it's live.Act with agency. Nobody will hand you a prioritized backlog. Find the slowest step and fix it.Ship great things. A working automation beats a documented plan.One team, one system. Create workflows in collaboration with MLROs across the group and with Product and Client Growth.Focus on the future. The point of this role is to let the business double its client count without doubling the compliance queue.

Speed is the thread through it all, which we call #LudicrousSpeed internally. Hours instead of weeks, without a single approval landing outside the risk appetite.

• Nice to haveCompliance exposure in OTC, payments, banking or another regulated setting. Useful, not mandatory.
• Interest in Bitcoin.

• Benefits & PerksFlexible working hours with hybrid WFH
• Comprehensive compensation packages
• A brand-new modern office near Dubai Marina
• Monthly team lunches, and a very healthy team events budget

Requirements added by the job poster

• 2+ years of work experience with Automation

• 2+ years of work experience with Artificial Intelligence (AI)

Why the role exists

Onboarding a client currently takes weeks. Most of that is manual work that exists because our criteria aren't written down anywhere an analyst or a script can use them.The job is to write them down, work the queue yourself while you learn where it breaks, and automate as much of it as possible from there. Within a year we'd expect most low-risk cases to clear without anyone touching them.

Responsibilities

• Productise the process, run it, then automate it. We want someone hands-on, not someone who writes requirements and waits two quarters for engineering capacity.Productise. Turn the AML policy and the business-wide risk assessment into onboarding criteria, screening thresholds, monitoring rules and escalation triggers that give the same answer whoever applies them. Same for the monitoring volume thresholds, exception policy, offboarding process and override justification rules.
• Run it yourself. KYB collection, refresh and remediation outreach to a published SLA. Triage screening and transaction monitoring, false-positive clearing against the rulebook you wrote. Evidence packs the MLRO can decide on first time. Banking questionnaires, counterparty information packs, MI, audit evidence and the quarterly board pack.
• Automate responses, process, screening and anything that is time-consuming.
• Build what you can yourself. Scripts, low-code, AI tooling, we don't mind how, as long as it's documented and holds up under audit.
• Stay aligned with the Group MLRO. Everything you write gets signed off, dated and auditable, and gets revisited as policy, appetite and jurisdictions change.

• KPIsKYB submission to trading-ready, under 24 hours for low and medium risk. Currently weeks.
• Percentage of alerts cleared by rule rather than by hand.
• Percentage of cases the MLRO can decide on without asking for more information.

• Who you areWe don't expect a perfect candidate, and this mix is unusual to ask for.A systems thinker. You look at a slow process and see the decisions, handoffs and missing rules that make it slow, then rebuild it rather than adding another checklist on top.
• Operations experience somewhere small enough that you built the process rather than inherited it.
• AI native. You reach for AI before you reach for headcount or a ticket, and you've built working things with it. Side projects and scrappy internal tools count.
• Able to push back when commercial pressure says move faster, but also articulate to the rest of the Compliance team why we don't need an extra process or policy.

How we work

We have five values, and we use them in check-ins, reviews, and hiring. You'll be asked about them at interview, so here is what they mean for this role.Truth over comfort. Say the process is broken while people are still defending it. That applies to your own work once it's live.Act with agency. Nobody will hand you a prioritized backlog. Find the slowest step and fix it.Ship great things. A working automation beats a documented plan.One team, one system. Create workflows in collaboration with MLROs across the group and with Product and Client Growth.Focus on the future. The point of this role is to let the business double its client count without doubling the compliance queue.

Speed is the thread through it all, which we call #LudicrousSpeed internally. Hours instead of weeks, without a single approval landing outside the risk appetite.

• Nice to haveCompliance exposure in OTC, payments, banking or another regulated setting. Useful, not mandatory.
• Interest in Bitcoin.

• Benefits & PerksFlexible working hours with hybrid WFH
• Comprehensive compensation packages
• A brand-new modern office near Dubai Marina
• Monthly team lunches, and a very healthy team events budget

Requirements added by the job poster

• 2+ years of work experience with Automation

• 2+ years of work experience with Artificial Intelligence (AI)