Software Engineer – Low‑Latency Trading Systems (Rust/C++)

About the role

We are looking for a high‑caliber Software Engineer with at least three years of experience to develop low‑latency, high‑throughput trading infrastructure. You will work hands‑on with Rust (or C/C++) on performance‑critical backend services, reporting directly to senior systems architects.

Key responsibilities

• Design, implement and maintain high‑performance backend services in Rust under senior guidance.
• Build components of distributed, fault‑tolerant systems that handle large transaction volumes.
• Write extensive unit, property‑based and simulation tests for correctness‑critical code.
• Profile, benchmark and optimise code for latency, throughput and memory efficiency.
• Participate in design discussions, rigorous code reviews and debug production issues on Linux.

Required profile

• B.Tech/M.Tech in Computer Science from an IIT or NIT (mandatory).
• 3+ years of professional software development experience in Rust, C++, Java or Go with systems‑level focus.
• Strong computer‑science fundamentals: data structures, algorithms, operating systems, networking and concurrency.
• Understanding of financial markets and trading concepts (order books, matching, spot & derivatives) is a strong plus.
• Experience with Linux, Git and modern development workflows.
• Competitive programming background or open‑source Rust projects are advantageous.

Required skills

• Rust, C++, Java, Go
• Linux development environment
• Git version control
• Performance profiling and benchmarking tools
• Distributed systems concepts (replication, consistency, message queues such as Kafka or NATS)
• Low‑latency techniques (lock‑free structures, zero‑allocation design, binary protocols like SBE, Protobuf, FlatBuffers)
• Consensus algorithms (e.g., Raft) and deterministic testing

What we offer

• Top‑of‑market compensation benchmarked against product companies.
• Direct mentorship from senior engineers with deep exchange‑infrastructure experience.
• Clear progression path to senior‑engineer ownership of subsystems within 18–24 months.