核心开发(Trading Engine Core Dev)

We are one of the world's earliest and most mature digital asset platforms, serving tens of millions of users around the world. We are consistently ranked among the top exchanges in the world, providing comprehensive trading and wealth management products covering thousands of digital assets.

With thousands of employees in major financial centers around the world, we operate a remote-first, highly autonomous culture that attracts talented individuals who thrive in fast-paced, challenging environments.

We currently hope to rebuild the core matching engine and are looking for outstanding professionals to join us. We hope you are (one of them):

1. Those responsible for high-performance and high-concurrency systems in large factories
2. Traditional finance is responsible for high-frequency trading systems (HFT market makers, derivatives exchanges, clearing systems)
3. Crypto’s top exchange is responsible for the matching engine and high concurrency optimization
4. Low-latency infrastructure (exchange technical service providers, financial cloud infrastructure) is responsible for underlying optimization

Core responsibilities

Tackling high-performance component development: Responsible for the code implementation of matching logic, high-precision risk control or high-speed distribution routing, squeezing every bit of computing efficiency.

Full-link observability construction: treat documents and observability as "first-class citizens", discover potential performance degradation through precise indicator monitoring, and prevent system jitter caused by small disturbances.

Participate in system reconstruction and logic optimization: carry out directional blasting on the bottleneck points of the existing architecture, continuously optimize the memory layout, reduce the Context Switch, and improve the single-machine throughput limit.

Output high-quality code and clear design documents - making each implementation stand the test of code review and time

ideal candidate portrait

A "technical geek" who is deeply involved in underlying facilities: obsessed with low latency, and also understands trade-offs - knows when to use lock-free queues and when to use read locks, and is willing to tinker with assembly or adjust kernel parameters for a little bit of performance

Have strict requirements for technical documents: believe that clear code logic and detailed technical design solutions are the foundation of high-quality projects, and have a strong code aesthetic.

Self-driven and keen: Have natural sensitivity to data and system indicators, and can proactively predict technical risks instead of passively dealing with bugs.

Originally posted on Himalayas