Enhance Python Trading Bots Infrastructure
Budget / Salary£20–250
TypeFreelance project
LocationRemote
Posted2 hours ago
Python Dev — Harden Live OANDA/Schwab Trading Bot Infrastructure (No Strategy Work)
Description:
We run two Python trading bots: one on OANDA (FX/CFD), one on Schwab (options). We need infrastructure fixes, NOT a new trading strategy — we already tested and rejected a breakout strategy against real historical data, so please don’t pitch indicators or “high win rate” ideas.
Scope:
1. Asset lock (OANDA): Restrict the bot to a short instrument allow-list (e.g. NAS100_USD, SPX500_USD, EUR_USD), enforced at the order-request level, not just config.
2. Permanent trade log: Append-only CSV/SQLite logger recording every order decision (timestamp, instrument, reasoning, size, SL/TP, result) — must survive outside system journald, which currently loses history after ~32 hours.
3. Schwab options sizing fix: Refactor contract sizing to enforce a $500 minimum trade size (via ceiling math), $300 max per-contract ask, 5-contract cap, with up to $600 total overrun allowed. Include unit tests.
4. Defensive coding: Proper exception handling on all API calls, no silent failures, safe fallback states.
Not in scope: Any change to entry/exit signal logic or new strategies. Any future strategy work will be scoped separately after independent backtesting.
Requirements: Proven experience with OANDA v20 REST API and/or Schwab API. Clean, tested, defensive code. Must explain how they’d catch an overfit strategy before going live (out-of-sample testing, real transaction costs) — this is a screening question, reject vague or evasive answers.
Deliverable: Working code, unit tests, brief documentation — reviewed before deploying to our live server.
Description:
We run two Python trading bots: one on OANDA (FX/CFD), one on Schwab (options). We need infrastructure fixes, NOT a new trading strategy — we already tested and rejected a breakout strategy against real historical data, so please don’t pitch indicators or “high win rate” ideas.
Scope:
1. Asset lock (OANDA): Restrict the bot to a short instrument allow-list (e.g. NAS100_USD, SPX500_USD, EUR_USD), enforced at the order-request level, not just config.
2. Permanent trade log: Append-only CSV/SQLite logger recording every order decision (timestamp, instrument, reasoning, size, SL/TP, result) — must survive outside system journald, which currently loses history after ~32 hours.
3. Schwab options sizing fix: Refactor contract sizing to enforce a $500 minimum trade size (via ceiling math), $300 max per-contract ask, 5-contract cap, with up to $600 total overrun allowed. Include unit tests.
4. Defensive coding: Proper exception handling on all API calls, no silent failures, safe fallback states.
Not in scope: Any change to entry/exit signal logic or new strategies. Any future strategy work will be scoped separately after independent backtesting.
Requirements: Proven experience with OANDA v20 REST API and/or Schwab API. Clean, tested, defensive code. Must explain how they’d catch an overfit strategy before going live (out-of-sample testing, real transaction costs) — this is a screening question, reject vague or evasive answers.
Deliverable: Working code, unit tests, brief documentation — reviewed before deploying to our live server.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.