Execution / Trading Systems Engineer (Live Trading)

Execution / Trading Systems Engineer (Live Bots, DAS Trader)

About the role
We run automated US small-cap trading strategies through DAS Trader on a fleet of Windows PCs. The bots are in C++ (the DAS API client and strategy code), with Python tooling around them for logs and reporting. They trade live money every US session, premarket included. We need an engineer who owns the health of this system day to day: watching the bots, reading the logs, finding why something went wrong, and shipping a safe fix.

Working hours
1:00 pm to 9:00 pm local time, Monday to Friday. This covers the US premarket and the open, so it's not a standard daytime schedule. You must be comfortable with this on a permanent basis.

What you'll do

• Monitor the live bots through the US premarket, open and close. Catch disconnects, stopped bots, rejected orders, missed entries, and stop-loss or cover-order failures as they happen.
• Read raw DAS and bot logs to explain exactly why a trade did or didn't happen. For each incident, write a short root-cause note that shows the log lines behind it.
• Own the short-locate and borrow logic. That covers double locates, wrong located-share counts, the wait before trying another locate route, and reconnect replays that inflate the count.
• Design, test and ship fixes to the bot code. Replay real logs against the patched build before it goes live, and roll out one account at a time.
• Keep the daily execution reports and trade-log uploads accurate, and fix them when they break.
• Maintain the bots across PCs: builds, configs, restarts and the mapping from account to bot.
• Work with the strategy and research side. They own the strategies, and you own how those strategies execute.

You are the right person if you

• Write production C++ (C++17 or later) and have debugged multithreaded, event-driven code with real-time message streams.
• Have worked on trading execution systems, such as order routing, a broker or exchange API, or an OMS or EMS. DAS Trader experience is a strong plus. US equities and small-cap borrow and locate mechanics are a strong plus.
• Debug from evidence. You read logs first, form a hypothesis, prove it with timestamps, and say plainly when you don't know yet.
• Stay calm when something breaks while the market is open, and are careful about changing code that touches live orders.
• Are comfortable on Windows servers, remote access and SSH, PowerShell or batch scripting, and Python for log analysis.
• Write clearly. Your incident notes should be short enough that a trader can read them in one minute.

Strong signs

• You have been on call for a trading system and can tell us about an incident you diagnosed and fixed.
• You've built log replay or simulation tools to test a fix before shipping it.
• You push back with data when you disagree.

Not a fit if

• You want to design strategies or backtest ideas; that is a different team.
• You aren't comfortable working an evening schedule.
• You prefer to ship fixes without a test or replay first.

How we'll hire

1. A short written exercise. We give you real, anonymised bot log excerpts from a missed entry and ask for the root cause and a proposed fix.
2. A code review conversation on a small C++ patch.
3. A final call with the team.