Java Backend Engineer, Global Travel Rule (GTR)

Responsibilities

Design, build, and maintain backend services and RESTful APIs powering compliance and analytics products

Own features end to end, from technical design through deployment and monitoring

Build data pipelines that ingest, normalise, and index on-chain activity across multiple blockchains

Contribute to the architecture of new compliance capabilities — you'll be in the room where the approach gets decided, not handed the outcome

Model data and optimise queries against relational and NoSQL stores at scale

Work directly with compliance and product specialists to translate regulatory requirements into technical design

Improve reliability, observability, and performance of services already in production

Use AI-assisted development tooling as part of your normal workflow to raise output quality and speed

Requirements:

• 3+ years building production backend systems in Java

• Strong command of Spring Boot, JVM fundamentals, concurrency, and memory behaviour

• Solid SQL and data modelling; practical experience diagnosing slow queries

• Experience designing and operating web-facing services at scale — request handling, caching, rate limiting, idempotency

• Working proficiency in both Chinese and English, spoken and written

• Fluent, daily use of AI coding agents such as Claude Code or Codex, with a clear view of where they help and where they need supervision

• Comfortable owning code you did not write, and reading unfamiliar codebases quickly

• Genuine interest in the problem space — compliance products reward engineers who care why a rule exists, not only what it says

Preferred:

A self-starting, exploratory mindset — you investigate problems before being asked to, and you go looking for the answer rather than waiting for a ticket

A willingness to contribute to how the industry develops, and to speak up with constructive proposals when you see a better way — we want engineers who challenge the design, not only implement it

AWS in production: ECS/EKS, RDS, S3, SQS, IAM, CloudWatch

Blockchain or crypto exposure — node RPC integration, on-chain data indexing, wallet or transaction infrastructure

Kafka or similar streaming platforms

Prior work in a regulated environment: financial services, payments, AML/KYC, or RegTech

Familiarity with FATF Travel Rule, sanctions screening, or transaction monitoring concepts

 

Why this role

Web3 compliance is one of the few areas where the engineering problem and the regulatory problem are genuinely unsolved together. The products you build here are used by exchanges, VASPs, and regulators, and the design choices you make have reach well beyond a single codebase. If you want work where the technical difficulty and the significance are both real, this is that.