Principal Software Engineer – Low-Latency Backends

Nasdaq, Inc.; New York, Northern (NY, KY); Hybrid; USD 191,000 - 318,000; Full time

Benefits offered by this job

401(k) match

Equity plan

Hybrid work schedule

Comprehensive benefits

Job summary

Nasdaq, Inc. is seeking a Principal Software Engineer in New York, NY. You will act as a senior technical authority, shaping technology strategy and delivering high-impact back-end solutions for Nasdaq's global equities trading systems.

The role requires a Master’s degree and 12+ years in high-performance software, with deep Java, Linux, and TCP stack expertise. Expect collaboration across architecture, QA, and network design, with a hybrid schedule and in-office presence at least three days per

Qualifications

• Master's degree in Computer Science, Engineering, or related field (or equivalent).
• 12+ years of software engineering in low latency, high throughput environments.
• Ability to lead cross-functional teams and influence decisions at a strategic level.
• Deep expertise in software architecture, systems integration, and enterprise-scale design.

Responsibilities

• Provide strategic technical guidance to engineering teams and initiatives.
• Lead analysis of complex client and business requirements to define solutions.
• Drive innovation and develop competitive, high-performance software solutions.
• Collaborate with Architecture, QA, Network Design, and Enterprise Planning to solve multidisciplinary problems.

Skills

Technical leadership

Low latency

Core Java

Linux

TCP stack

Education

Master's degree

Tools

ITCH

OUCH

FIX

Job description

Nasdaq, Inc. is seeking a Principal Software Engineer in New York, NY. You will act as a senior technical authority, shaping technology strategy and delivering high-impact back-end solutions for Nasdaq's global equities trading systems.

The role requires a Master’s degree and 12+ years in high-performance software, with deep Java, Linux, and TCP stack expertise. Expect collaboration across architecture, QA, and network design, with a hybrid schedule and in-office presence at least three days per