Binance
via Lever
Java Backend Engineer, Global Travel Rule (GTR)
Posted 548 days ago, which is unusual. The employer's own board was still carrying it when we last read it, 3 hours ago.
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 12h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 548d ago
The date the source published, not the day we noticed it (2025-03-15). Last seen at its source 3h ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
Asia
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay A$2,062–3,050/mo
Middle 50% of 11 listings that do state pay — Engineering · all levels · Asia · AUD/month. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
lever employer's own board first seen 17h ago · last seen 3h ago
The listing
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:
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.