Senior Software Engineer-Trading

About the role

The role shapes a high-performance Order Management System for trading, bridging investment intent and market execution with precision and low latency. The position drives architectural vision and elevates engineering standards as a strategic technical leader in the Trading domain.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Architect scalable, resilient Java or Quarkus microservices to define the technical direction for trading systems.

Design trade order lifecycle logic to ensure reliable broker connectivity and accurate allocations for precise execution.

Build event-driven systems and data solutions on AWS using Kafka to enable robust messaging at scale.

Scale FIX, REST, and file-based integrations to support high-performance data exchange across interfaces.

Shape engineering culture by mentoring teams and elevating Agile SDLC standards to improve delivery quality.

Requirements

Earn a B.S. or M.S. in Computer Science or a similar technical field, or possess equivalent practical experience.

Bring 8+ years of experience architecting and building complex backend distributed systems at scale.

Demonstrate expert proficiency in Java, Spring Boot, JVM tuning, and concurrency, with Quarkus as a plus.

Apply advanced expertise in AWS cloud-native architectures and messaging platforms like Kafka.

Show experience with databases, SQL, NoSQL, and data architectures.

Champion developer productivity, automation, and adoption of AI-assisted development tools.

Act as a technical leader with strong ownership to drive cross-team initiatives.

Communicate complex technical concepts clearly to non-technical stakeholders and foster a collaborative, experimental culture.

Prior experience in Trading or Financial Services is preferred.

Practical knowledge of the FIX protocol is preferred.

Familiarity with frontend technologies such as React is preferred to support UI-related backend requirements.

Practical notes

Work requires Eastern working hours. Employment eligibility requires authorization to work in the United States without visa sponsorship, and the ability to start on the first day.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Core tools include Java, Spring Boot or Quarkus, AWS, and Kafka for event-driven architectures.

The position operates within a global data platform used by thousands of firms managing trillions in assets.

Engineers contribute to an open platform that integrates with hundreds of data and consulting partners.

The role emphasizes Agile delivery, technical ownership, and continuous learning in a fast-moving financial environment.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.