Senior KDB Developer

Job Description

A global financial-services organization is seeking a Senior KDB Developer to join a technology organization supporting real-time Equities data and analytics.

\n

\n

This position will engineer high-performance platforms responsible for processing large volumes of real-time and historical financial data. The engineer will work closely with trading, quantitative, engineering, QA, and production teams while maintaining substantial hands-on ownership of KDB+/Q development.

\n

\n

The ideal candidate combines deep KDB/Q expertise with experience building real-time, low-latency financial data systems.

\n

\n

Responsibilities

\n

\n

\n
• Design and develop low-latency KDB+/Q platforms for real-time financial data.

\n

• Build and optimize streaming pipelines supporting market, ticker, order, and execution data.

\n

• Develop scalable tickerplant, RDB, and HDB architectures.

\n

• Design time-series models and high-performance query frameworks.

\n

• Optimize platform latency, throughput, reliability, and query performance.

\n

• Develop APIs and reusable components for trading and analytics applications.

\n

• Implement monitoring and automated data-quality controls.

\n

• Troubleshoot complex real-time data and production issues.

\n

\n

\n

Role Requirements

\n

\n

\n
• Extensive hands-on KDB+/Q engineering experience.

\n

• Strong experience developing real-time data-processing systems.

\n

• Experience working in low-latency environments.

\n

• Financial-services experience.

\n

• Experience with large-scale market, trading, transactional, or time-series datasets.

\n

• Strong Linux/Unix skills.

\n

• Working knowledge of Python or Java.

\n

• Strong understanding of time-series architecture and streaming data.

\n

• Ability to work directly with technical and front-office stakeholders.

\n

• Ability to work onsite in New York City three days per week.

\n

\n

\n

Nice to Have

\n

\n

\n
• Electronic or algorithmic trading experience.

\n

• Equities experience.

\n

• Market microstructure knowledge.

\n

• AWS exposure.

\n

• Authentication and entitlement experience.

\n

\n