Engineering market data for an exchange

Problem

CoinDCX was building its in-house cryptocurrency exchange. My work focused on the market data service, where I owned the design and implementation of multiple modules.

Other teams had market-data dependencies. The role therefore included coordinating their needs, not only delivering code within one service.

Constraints

The scope crossed module and team boundaries. Alongside hands-on engineering, I served as the single point of contact for the market data service and coordinated with teams depending on it.

In parallel, I developed core Order Management System (OMS) components. That was a separate contribution within the broader exchange effort; my service-level point-of-contact responsibility was for market data.

Architecture

Module design and implementation sat within the market data service. Coordination extended that responsibility to the teams depending on the service.

Decisions

At the module level, I owned planning, design, and implementation. At the service level, I coordinated market-data dependencies with other teams as their point of contact.

The role combined module-level engineering decisions with responsibility for understanding how other teams depended on the service.

Execution

• Planned, designed, and implemented multiple modules in the market data service.
• Served as the service’s single point of contact for other teams’ market-data dependencies.
• Developed core OMS components as part of the broader in-house exchange effort.

Impact

The contribution combined delivered market-data modules, core OMS components, and a defined point of contact for cross-team dependencies.