We are building our financial crime platform in-house: transaction monitoring, screening, case management and the integrations around them. As an Engineer in Financial Crime, you will own one part of that platform and see it through from code to production. The tools you build will be used every day by the teams who investigate alerts and cases.
Responsibilities:
- Own one or more services and integrations behind our financial crime controls, such as alert generation, screening and case management tools.
- Write clean, tested code and take part in code reviews.
- Add the logging, metrics and service alarms that show when a service misbehaves, build Grafana dashboards for your services, and keep runbooks up to date.
- Work with Product Owners and operations teams to understand how alerts and cases are handled, and improve the tools they use.
- Use AI coding tools in your daily work, reviewing their output as you would a colleague's code.
Requirements:
- 3+ years of commercial backend development in Java.
- Experience building and running services in production: you have owned a service, not only delivered tickets.
- Hands‑on experience with financial crime systems, such as AML, transaction monitoring, sanctions or PEP screening, fraud detection or case management.
- Working knowledge of Apache Kafka or another message broker, and of running services on Kubernetes.
- Hands‑on experience with logging, metrics and alerting, ideally with Grafana or a similar tool.
- Solid testing habits: unit and integration tests are part of how you deliver.
- Clear written and spoken English.
Nice to have:
- Experience in online brokerage, trading platforms, payments or digital banking.
- Experience integrating third‑party vendors for screening or identity verification.
- PostgreSQL and SQL performance work.
- Experience with AI coding tools such as Claude Code, Cursor or GitHub Copilot.
Desired Candidate Profile
- 3+ years of commercial backend development in Java.
- Experience building and running services in production: you have owned a service, not only delivered tickets.
- Hands‑on experience with financial crime systems, such as AML, transaction monitoring, sanctions or PEP screening, fraud detection or case management.
- Working knowledge of Apache Kafka or another message broker, and of running services on Kubernetes.
- Hands‑on experience with logging, metrics and alerting, ideally with Grafana or a similar tool.
- Solid testing habits: unit and integration tests are part of how you deliver.
- Clear written and spoken English.