DevOps Engineer

Job Description

Site Reliability Engineer – Investment Fund

\n

Our client is a specialized investment firm in New York looking to hire a Site Reliability Engineer as the second engineer on its technology team.

\n

The firm is a lean, approximately 17-person investment platform focused on micro-cap PIPE and structured equity investments. Its technology stack has been built internally and includes AI applications used daily by the investment team, an internal knowledge system, scheduled data pipelines, and infrastructure supporting the firm's trading systems.

\n

This hire will work directly with the CTO and take ownership of production reliability across the platform. This is a broad, hands-on role with no layers between engineering and the investment team.

\n

What You'll Do

\n

\n
• Own day-to-day reliability of production applications, data pipelines, AI tools, and trading-related systems
\n
• Build and maintain monitoring, alerting, logging, and tracing across the technology environment
\n
• Monitor scheduled data pipelines and troubleshoot late or missing data, failed dependencies, retries, and reruns
\n
• Serve as the first line of technical support for the firm's trading systems
\n
• Diagnose and resolve production incidents across applications, infrastructure, data, and integrations
\n
• Read, debug, and patch production Python code when issues arise
\n
• Support Linux-based applications, shell scripts, cron jobs, and scheduled processes
\n
• Operate applications and data workflows across Azure and AWS
\n
• Support deployment, backups, database connections, performance issues, and other day-to-day cloud operations
\n
• Monitor and troubleshoot LLM-backed applications, including provider outages, rate limits, model changes, silent agent failures, and unexpected token usage
\n
• Automate recurring operational work and eliminate manual processes
\n
• Build runbooks and documentation for systems currently maintained by a small engineering team
\n
• Communicate directly with investment, trading, operations, and senior leadership when issues arise
\n

\n

What We're Looking For

\n

\n
• 4–8 years of experience in Site Reliability Engineering, Production Support, Application Support, Infrastructure Engineering, Platform Engineering, or a similar hands-on production role
\n
• Strong Linux, shell scripting, and cron experience
\n
• Strong working knowledge of Python , including the ability to read, debug, and patch an existing production codebase
\n
• Experience building monitoring, alerting, logging, or tracing capabilities , rather than only operating within an established environment
\n
• Hands-on responsibility for scheduled data pipelines and their day-to-day reliability
\n
• Experience troubleshooting dependencies, retries, missing or late data, failed jobs, and pipeline reruns
\n
• Experience operating applications and data workflows in a cloud environment such as Azure, AWS, or GCP
\n
• Experience running an LLM-backed application in production and troubleshooting the operational issues unique to LLM-based systems
\n
• Meaningful on-call or incident-response experience with the ability to independently own an issue from detection through resolution and postmortem
\n
• Comfortable operating independently within a small technology team
\n

\n

Nice to Have

\n

\n
• Experience at a fintech or AI product company, proprietary trading firm, broker-dealer, hedge fund, or other financial-services organization
\n
• Familiarity with Microsoft Graph API, Entra app registrations, Teams bots, SharePoint permissions, or the broader Microsoft 365 ecosystem
\n
• Understanding of trading systems, market data, OMS/EMS workflows, end-of-day processes, settlement, or Bloomberg/vendor data
\n
• FIX familiarity
\n
• C++ exposure
\n

\n

Who This Role Is For

\n

This is a strong opportunity for an engineer who enjoys owning production systems rather than working on one narrow piece of a large infrastructure organization .

\n

The ideal candidate has been the person on call, has diagnosed real production incidents, has kept scheduled pipelines running, and is comfortable figuring out whether an issue sits in the application, infrastructure, data, or upstream dependency.