Options + Futures Trading System (IBKR)

We run a live, working 0DTE options trading system on Interactive Brokers — connector, broker authentication, database, and web dashboard are all already built and running. We are not paying to rebuild any of that. This job is to adapt that existing system to run a new strategy: a 30-day iron condor (short call + short put, long protective wings) with a futures hedge overlay, backtested across 8 symbols. The strategy logic and rules are fully defined — this is an implementation job, not a research job. We don't need new infrastructure, Reuse what already works. Simple and complete beats clever and complicated — and it keeps this within budget. What already exists (do not rebuild) IBKR connector (order placement, fills, account/margin snapshots) for both options and futures Broker authentication and connection handling Database layer used as the integration point between components Web dashboard for monitoring and control Your job is to add the new strategy logic on top of this, following the same pattern already in place (a strategy "controller" that only reads/writes the database Scope of work Strategy implementation — 30DTE iron condor entry, following the exact entry/strike/pricing rules from our backtest Futures hedge overlay — the deferred-entry hedging logic from the backtest (front month + back month expirations) Margin tracking section — a daily view (dashboard section or report) showing, per open position: premium collected, futures P&L (realized + unrealized), current option leg value if closed today, and total margin used vs. available. This must be reliable enough that we can trust it for real capital decisions. Early settlement closing. If at risk for early settlement (ex Divident, then close early. Paper trading validation — run live on paper first, confirm it matches backtest behavior on a handful of real trades, before touching live capital. Who we're looking for: Strong Python, comfortable with the Interactive Brokers API (TWS/Gateway) Experience with options and futures — you should understand what an iron condor and a futures hedge actually are, not just the code shape Comfortable working from detailed written specs and asking sharp questions rather than guessing We expect you to use AI coding tools as part of your workflow — we do too, and use it well. This isn't a red flag for us, it's a plus — we just want visibility into how you're using it, not code you can't explain. A short video call before we start. We want to actually see and talk to who we're working with — not just exchange messages. This matters to us for building a working relationship we can trust over time, especially since we're hoping this leads to ongoing work, not a one-off.