Software Engineer - High Visibility Team - Middle Office Technology

About the Role

This role sits inside the technology group supporting cash, collateral, settlements, and liquidity operations for a global multi-strategy fund. The systems this team builds reconcile positions, move money, and confirm funding across the firm's trading strategies every single day. If a settlement break goes undetected or a cash position reconciles incorrectly, it is this team's tooling that catches it before it becomes a real problem.

What You'll Do

• Design, build, and maintain systems that support cash management, collateral, and settlement workflows across multiple trading strategies
• Partner directly with middle office operations teams to translate manual or error-prone processes into reliable software
• Build and maintain data pipelines and reconciliation tooling that operations and risk teams depend on daily
• Debug and resolve production issues in time-sensitive, operationally critical systems
• Contribute to architecture decisions as the team's tooling scales across new strategies and asset classes

Must-haves

• 3+ years of professional software engineering experience
• Strong SQL and proficiency in Python, Java, or C#
• Experience building software for financial operations, back-office, or middle office functions at a fund, bank, or financial services firm. This is non-negotiable for the role.
• Comfort working directly with non-engineering stakeholders to scope and ship solutions
• Experience working in environments where data accuracy and timeliness carry real operational consequences

Nice-to-haves

• Exposure to multi-strategy or multi-asset trading environments
• Experience with cloud infrastructure (AWS, Azure, or GCP)
• Familiarity with reconciliation, settlement, or payments systems
• Prior experience at a hedge fund, asset manager, or prime broker

Why This Role

This is a small, high-leverage engineering team working on systems that touch every strategy the fund runs. Compensation is top of market, and the team operates with real autonomy over how problems get solved. For an engineer who wants their code to directly prevent costly operational errors rather than sit several layers removed from the business, this is that.